The more normal transfer path is to offer to take over a specific community or communities by:

1. Reaching out to the existing mod and asking to be added to the mod team.
2. Documenting their lack of response after a few days or a week.
3. Documenting the failure to abide by Lemmy world moderation guidelines: https://lemmy.world/post/424735 by linking spam or off-topic posts and to communities that lack rules/useful-sidebar-content, etc.
4. Posting this info in [email protected] and offering to takeover moderation.

This is better than mass deletion because it keeps whatever small list of existing subscribers and post content intact across the transition. For moderation, Lemmy world admins will get notified of reports and can address anything that violates instance rules.

The Beehaw admins made this choice, and documented their rationale here: https://beehaw.org/post/567170

This, but desktop linux users are on the step for 193rd place while excitedly screaming and holding a third-place sign. Steamdeck users are on the 3rd-place step while calmly playing their deck.

Tests go in [email protected]

I thought that was the first rule of rendering web content? Or was it protocol parsers?

I remember, it was first rule of video game character creation screens:

Folks should not use lemmony to bootstrap their subscription count. It's not that hard to hit lemmyverse.net and just manually sub a bunch of stuff you're actually interested in, or to visit a big instance and browse their all feed unauthenticated.

But if you really want to automate community bootstrapping, lemmony is the worst of the scripts that doit because it defaults to subscribing to EVERYTHING, including all the porn, piracy, and hate communities on the most absent-admin'ed under-modded instances in the lemmyverse. Then your instance will mirror all those questionably legal communities and re-serve them to the public unauthenticated internet, creating hosting liability for you. Not to mention being a bad fediverse citizen and creating massive amounts of federation load on the instances forwarding you posts and comments from 20k communities that you don't read.

These two subscription bootstrapping scripts limit you to top subs by default... So you're more likely to be in well-modded territory and just the number of subs is smaller you you can review them and back out of anything sketchy. Subscriber-bot's docs do a good job of explaining the risks and problems of mass-subscription so you know what you're getting into.

• https://github.com/lflare/lemmy-subscriber-bot
• https://github.com/Fmstrat/lcs

I blame unfederated subscriber counts. If you look up any community from an account on lemmy.world and there is a local version and a remote version... the local version LOOKS bigger when it's about half the size because the remote version only shows subscribers from lemmy.world whereas the local version shows subs fediverse-wide.

If sub counts were apples to apples for remote and local communities, people would much more frequently sub to the bigger remote comminity. But lemmy.world is so big, that when people are subbing locally because they're confused about which is bigger... the lemmy.world community actually becomes bigger very quickly. So it's winning the community scaling races consistently on pure confusion. The resulting community centralization is not all that healthy and they often overtake better run and more established communities for no meaningful reason.

Sadly the formatting in this post gave me terminal cancer. As my final act, I've fixed the formatting. OP, please, only you can save the others. Fix the post formatting.

1. Max VERSTAPPEN - Red Bull Racing 1:26.720
2. Lando NORRIS - McLaren +0.241
3. Oscar PIASTRI - McLaren +0.372
4. Charles LECLERC - Ferrari +0.416
5. Carlos SAINZ - Ferrari +0.428
6. George RUSSELL - Mercedes +0.435
7. Lewis HAMILTON - Mercedes +0.491
8. Alexander ALBON - Williams +0.810
9. Fernando ALONSO - Aston Martin +0.939
10. Pierre GASLY - Alpine +0.969
11. Nico HULKENBERG - Haas F1 Team 1:28.896
12. Lance STROLL - Aston Martin 1:28.935
13. Esteban OCON - Alpine 1:28.956
14. Logan SARGEANT - Williams 1:29.031
15. ~~Valtteri BOTTAS - Alfa Romeo no time~~ DQ'ed for failing to provide a sufficient fuel sample. See https://www.formula1.com/en/latest/article.bottas-disqualified-from-silverstone-qualifying-with-finn-set-to-start.5smsKl0raawLdfivHEeQgq.html
16. Sergio PEREZ - Red Bull Racing 1:29.968
17. Yuki TSUNODA - AlphaTauri 1:30.025
18. Guanyu ZHOU - Alfa Romeo 1:30.123
19. Nyck DE VRIES - AlphaTauri 1:30.513
20. Kevin MAGNUSSEN - Haas F1 Team 1:32.378

This is a terrible idea, and borderline irresponsible. One of the key reasons that Lemmy doesn't subscribe by default is to avoid forcing servers with many communities to waste time/CPU delivering messages to servers where no one will read those messages. By subscribing to everything, you're telling all those overloaded servers to waste time sending content to your server that you'll never even see.

• It also will massively inflate your db by multiple GB/day.
• It will maximize the chances of you downloading and hosting copyright infringing content and content that may be illegal in your jurisdiction but not in the jurisdiction where it's hosted (loli, etc).

It is much MUCH better to just hit lemmyverse.net and subscribe to 10-100 communities you care about. If script accepted a list of community-urls and automated subscribing to those, that would be super nice. Subscribing to the entire lemmyverse is terrible for your server, for your hosting liability, and for the lemmyverse's performance.

You can't, but there's a github issue to enable this functionality: https://github.com/LemmyNet/lemmy/issues/1985

The terms-of-use on every lemmy server I've seen would be considered underdeveloped by any lawyer I've ever met. Pragmatically:

• In the absence of a TOU that requires licensing content to participate, content posted directly to a lemmy server would probably get whatever the default treatment is either in the jurisdiction where the post was made or where the server is hosted (or maybe even that depends on the jurisdiction of each in complex ways). In the US that would mean all content is all-rights-reserved by default.
• But the poster/commenter isn't going to try to enforce their rights against lemmy. If they didn't want the content there, they wouldn't have put it there. And if they changed their mind they can delete it. And if they refuse to delete it themselves but contact an admin/mod... probably the admin/mod will just delete it for them.
• If the jurisdiction where the instance is hosted has a safe-harbor framework of some kind (like the US does), that would provide some protection from copyright claims on user-generated content provided the admins followed the requirements to be eligible (which I think most admins do even if they don't know it).
• Images and media hosted elsewhere but hotlinked from Lemmy may have their own TOU's (like imgur or whatever).

Overall, I'd say most of the lemmyverse has underbaked policy frameworks. The de-facto results function ok pragmatically anyway for what lemmy does on its own. Any scraping/reuse of content from Lemmy would have to navigate a very complex, confusing, and ambiguous licensing landscape. Probably 10y from now, if the Lemmyverse continues to grow, TOU's will be more common and more clear about open-licensing content or leaving it all-rights-reserved but giving lemmy a perpetual irrevocable non-exclusive right to distribute whatever you post here (the latter of which is more or less what's implicitly happening today).

Have you considered modifying this to be a pull-request for lemmy-ui? It's cool to have an extension, but Lemmy being open-source makes it possible to merge the improvement upstream and make it better for everyone.