this post was submitted on 17 Jul 2023
60 points (98.4% liked)
sh.itjust.works Main Community
7716 readers
2 users here now
Home of the sh.itjust.works instance.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The potential liability for instance owners due to this is massive. Images should be stored in the instances of the community they're posted to.
It's fundamental to the design of Lemmy's implementation of federation via ActivityPub that all content from an account be hosted on the account's instance.
If it's an ActivityPub feature, this is somewhat of a poor design if you ask me (or at least not being able to change this). He's right, this feature could put instance owners in legal problems, because the data in question is actually stored on their server, not the server that you posted the image on.
Indeed, this is a huge design flaw. You would basically have to police everything that users post on other instances as well. Do you even have moderation tools for this?
Yeah, you're right... but I think the problem is, the login info... but, than again, how could it store copies of my post, but not images.
In any case, I do agree that this is something that should be looked into and discussed in length.
I don't see why the login info is an issue, and storing a copy of a post wirh just a link to an image makes sense.
I really have no idea how other instances actually confirm that you're posting from another instance, not just emulating that you're a user on another instance. That might be a part of ActivityPub, but I haven't looked at code, wouldn't know.
This is part of the ActivityPub protocol, but I haven't looked into it enough to know how it's defined.