• 1 Post
  • 1 Comment
Joined 2Y ago
cake
Cake day: Jul 04, 2023

help-circle
rss

Exactly this is what I am worried about, you can get into trouble quickly. Good luck explaining to lawyers/judges that it’s not your content actually but just federation. Even if you could, in most jurisdictions you wouldn’t be off-the-hook anyway.


Self-hosted lemmy without serving arbitrary federated content?
I want to self-host lemmy and participate in federation. However, I wonder whether it's possible to have a setup where only I, and trusted users, are allowed to browse federated-content. Basically, guests should not be allowed to use my instance to browse other federated content. So requests to "mydomain.tld/c/[email protected]" should not be possible. Only users, logged-in on my instance, should be able to do that. Despite that, guests should be allowed to see posts of communities posted on my instance, and users of other instances should be allowed to comment. I know I can choose with which other instances mine should link with, but this would make the experience inconvenient to me. Because then I would need to adjust the config if I want to subscribe to a community on an instance I have not yet linked with. Is such setup possible? Could not find the answer in the docs unfortunately The only thing I can think of is something like blocking UI requests, and allow them only from localhost (so I would create a "ssh -L" tunnel on the server). Federation API endpoints would not be blocked. But this seems shaky, does Lemmy support a cleaner, built-in solution?
fedilink