Just wondering if it would be possible to enable the instance on LemmyFederate since then we could more easily distribute communities from here to elsewhere since as it is it’s kind of hard to grow communities or even just have them be discoverable on other instances.
Uh for those who don’t know LemmyFederate is a service that allows communities to be distributed to other instances via a bot that subscribes to them, then unsubscribes once a real user joins. It’s helpful because communities don’t become visible on remote servers until someone from that server searches and subscribes to it. Due to a limitation of how the Activitypub system works.
I’ve consciously not subscribed to this as it messes up the organic /all tab of the instance and as other said it would explode our storage and bandwidth.
Will you reconsider your decision once this gets implemented? https://github.com/LemmyNet/lemmy/issues/5016
It should save lots of storage space that would otherwise be used to store all the old votes from all the communities
I’m not really into the idea of archiving posts and not being able to reply to older posts anymore. Was one of the more annoying things on Reddit, and I’m glad they did away with it, or at least made it optional. Sometimes you just need to add something new to something old ya know.
This issue is mainly just about votes, since these take up lots of storage space. The total amount of upvotes/downvotes would still be saved, but the individual votes of each user would get purged from the DB. Even though it mentions disabling comments once a post gets archived, I think this will be a separate option, that can be disabled by instance admins. If you still oppose this, you should comment on the GitHub issue, that’s where the devs are, not here.
I thought I had posted it but I forgot to hit send, silly me. I posted it now.
I see, that makes sense. It does kind of suck though since it means that it’s harder to get communities here seeded elsewhere so they can be discovered and gain users. Getting communities here isn’t as big a deal , it’s getting your communities pushed out there that’s the issue.
Maybe someone could talk to the maintainers about including a mode that doesn’t push external communities to our instance but still allows for other instances to subscribe to communities on our instance.
Just a note from a small/personal instance owner to potential others, this will explode your bandwidth and storage usage.
That’s a good point, would recommend if doing it to keep the auto-add option off since that can help reduce the burden somewhat. If it’s automatically fetching and adding instances that can make the issue that much worse.
Can you set which communities?
You have to manually input each Community into the tool to get it to start doing its magic.
On instances where auto-add is enabled, it will fetch communities automatically and subscribe to them.
We’re looking into it ✌️
