I think that’s a kbin thing, where any time you reply to a comment, your comment includes an @ to that comment’s author. I think the only one they intended to “ping” was butterface
Oh, interesting! Thanks for pointing that out. Side note: entries… I hope kbin adopts better language for what to call Reddit-like posts (articles), Twitter-like microblog posts (posts), and comments (entries?). I never would have guessed entries == comments. Maybe this is ActivityPub-specific naming? It reminds me of a past job where we surfaced internal technical names as the names of products and features… it just confused customers.
Yes, there needs to be a glossary somewhere to get people up to speed, or some kind of on-boarding process. It's also plausible that some of the naming conventions are from translation weirdness, and, as you say, backend Activitypub naming conventions that frontend users don't normally see.
I made a magazine (aka a community, aka a sub[reddit]) specifically so I could play around with kbin to figure things out. Right now, trial and error is all we have, as I imagine all the devs are more busy with more technical issues than naming conventions.
But it is an open source project and the developers views are strongly in favor of privacy, so yeah you can self host it or check the source code. But I think it’s safe to assume they didn’t program it like that.
Note that people who host an instance theoretically change it, but still I wouldn’t worry it’ll actually happen.
Isn’t this comment deleted for you too? (I replied twice by mistake)
Anyway, yeah I completely agree. But as I replayed to a user at my other reply:
I don’t believe that, assuming an average person host an instance, the host will want some random people metadata from photos. It’s not big corps that process every bit of data they get.
But it is an open source project and the developers views are strongly in favor of privacy, so yeah you can self host it or check the source code. But I think it’s safe to assume they didn’t program it like that.
Note that people who host an instance can theoretically change it, but still I wouldn’t worry it’ll actually happen.
Instance admins are pulling the code down and implementing it in their server. They could easily slip in some malicious backend code and there would be no way to verify it.
Of course, I said that too. And unless you self host yourself you have to trust the instance you’re using. But the question itself was more about lemmy in general, and most people just deploy the docker image or something.
Also, I don’t believe that, assuming an average person host an instance, the host will want some random people metadata from photos. It’s not big corps that process every bit of data they get.
Rule #1 in internet privacy: don’t assume best intentions of anyone. Just because it is open source does not mean whoever hosts the instance didn’t modify the source.
It’s a good idea for the sake of your privacy to remove the metadata from the picture. While for a picture of a pet it is less important, it’s still a good idea to get in the habit of nixing the metadata. Don’t make it easier for you to be tracked and profiled.
Why would it be less important for pet pics though? I think it would be more important because you probably take those pics at home and your home location might get leaked.
On windows, if you check the properties of the file, there’s a button to remove metadata.
On iPhone, if you go into your photos and drag a photo up, you can click “adjust” and remove or edit the location and time/date (it will still have camera data).
I did a test upload of an image I knew had location data and it appeared to be stripped when I viewed the post. That being said I’d like a definitive answer and I do agree with everyone saying, the only way to know for sure is to do it yourself.
Add comment