… viewing posts by All gives a very limited view of what’s out there, and uncomparable to viewing All posts on R*ddit. The tool mentioned, while definitely could use some adjusting, alleviates that issue a lot more.

I understand the goal of the tool, the defaults are a really bad approach at achieving it and the docs are really bad at identifying the pitfalls. A tool that subscribes to a list of communities provided in a text file would be great. Subscribing to the entire lemmyverse is a solution that creates problems that are worse than the discovery problem.

Definitely amusing to see you gauge piracy on the same level as hate-speech or porn/loli. Not that I have any opinions about the matter, but amusing regardless.

All of this content seems fairly clearly to me to fall into the category “content that can cause legal liability for the hoster depending on their jurisdiction”. Is that a controversial point of debate?

I run my own tool, written by myself, subs to about ~800 communities of a certain defined activity threshold, of which have about more than 50 users/month, my metrics have indicated a disk space usage of about 2GiB/day, 20% of a single CPU core, and about 8~10GiB/traffic a day. Is this workable for a tiny instance on a Pi? Probably not, but it is what it is, and while I think my fediverse activity is not agreeable, I try to take steps to alleviate that by manually unsubscribing from the communities that I absolutely have no interest in.

This all sounds eminently reasonable. 800 subs is a lot, but it’s much more reasonable than the 7k subs this tool leaves you with in it’s default config, and if you further curate it manually and that’s what it takes for your feed to feel lively… then go for it.

Maybe consider releasing it? I totally agree that community discovery is rough all over, and moreso on tiny instances. A tool to help folks bootstrap 50-200 communities and that did a good job documenting the tradeoffs of oversubscription and helped folks identify/avoid legal risk would be a huge step up from the “subscribe all” approach.

I definitely agree with the part about jurisdiction, but content serving is still done from the original instance…

Content is NOT served from the original instance. https://lemmy.world/post/1191149 shows a post that was made to a community on lemmy.ml. Because there are subscribers on lemmy.world, that post is replicated there. Any unauthenticated user on the internet can view that post, the content was pulled out of the db on lemmy.world and sent out from lemmy.world’s ip and over its internet connection. By every legal definition I’ve encountered lemmy.world is serving that post and subject to any legal complications that entails. The only exception I’m aware of are full-size images, which don’t replicate. Thumbnails do though, so that provides no protection. You host the image content, just at reduced quality.

… and while I’m not a lawyer, I think the most severe legal threat might be just a takedown.

This is also not true. In the US, you have to register a copyright agent to receive the kinds of protection typically associated with commercial hosts. If you fail to do so, I believe that you run the risk of just getting sued out of the gate for copyright issues. There are also almost certainly jurisdictions where hosting gay porn or certain political speech is a “straight to jail” kind of maneuver.

Of course, I have no evidence that OP is in a particularly dangerous jurisdiction. But my broader point is that new users of single-user instance often don’t consider that they may be signing up to host legally risky content that they themselves didn’t create, view, or want. If one curates their list of subs, they can gauge for themselves what communities they consider to be risky. If they “subscribe all”, they WILL be serving to the unauthenticated public internet the worst of the lemmyverse without realizing it… which is an entirely avoidable situation.