I use Lemmy Community Seeder. Every four hours it checks the top posts on instances you specifies and automatically subscribes you to communities that appear there but you aren't already subscribed to. You can tweak it to ignore specific communities or instances.
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
That's amazing! I'm gonna set it up on my instance
Keep in mind that you're going to be retrieving and storing a huge amount of data running these scripts, and you should expect to need more than a $5 1gb of RAM vps to do it without it being a shitty broken experience for you.
We're talking dozens of gigabytes of storage for the database, plus effectively a need for an infinite amount of storage for the image caching, plus enough RAM and CPU resources to effectively process the whole Threadiverse.
Keep in mind that you’re going to be retrieving and storing a huge amount of data running these scripts
And you are adding to the overload of lemmy.world, beehaw, lemmy.ml, etc who have all the popular content communities. Federation has a lot of overhead, as does having to distribute a community one vote at a time to 500 subscribed servers.
True dat. I've been running it about seven weeks and am pulling about 700 communities. Most have near zero traffic but the high volume ones do add up.
42G /mnt/sp4dot1-data/appdata/mylemmy.win/
12G /mnt/sp4dot1-data/appdata/mylemmy.win/postgres
30G /mnt/sp4dot1-data/appdata/mylemmy.win/pictrs
I subscribe to !newcommunities@lemmy.world which helps. Other than that I look for mentions of other communities in comments, similar to how I used to on reddit.
This is really great, it's basically the same effect as what OP is doing when browsing c/All on a large instance, except you can do it on a small instance and without using an insane amount of system resources on your server
pend my time on Lemmy scrolling “All”, which I think is a pretty common thing.
There was a lot of advice handed out back in June that the answer to scaling Lemmy was to go create instances. The reason it works is because "All" is empty on a virgin system ;) With no data in the database, the logic Lemmy hands to PostgreSQL works real fast ;)