Part of the problem is the smaller instances don’t even see those communities when you post, I was unaware of 75% of the communities you just listed. I have a micro instance, and if I don’t subscribe I don’t see it.
It’s probably not much of an issue, given that most people are on a couple mega instances…
I know community discoverability can be an issue. When I launched [email protected] and [email protected], I used my alts on the top 10 instances to subscribe to them so that they would show in the All feed of those instances.
There was a tool that could help address that (I don’t have the name right now), but last time I tried it, it wasn’t working, so I’m not sure it’s that useful.
Good to be seen! Smart of you to preseed The larger instances good strategy
I think the clients are going to have to solve this, maybe look at the all feed on multiple servers, and then only show you what’s different compared to your own server.
Discoverability is the key weakness of Lemmy, just like mastodon
Are you familiar with Lemmy Federate? Participating instances get a bot that follows submitted communities to get them in feeds and then unsubscribes once a real user from the instance subs.
Ah, that’s the cool I was looking for! Are we sure this tool is completely functional? The large number of “in progress” instances always gives me doubt
It used to be Lemmy Community Boost and I think it still works despite the status. I do keep meaning to track the developer down and give them a nudge.
The tool relies on community local subscriber count to unsubscribe and that value was not available from 0.19.0 to 0.19.3. I fixed the problem about 8 months ago but due to unfortunate timing, it didn’t reach prod from then.
In the end, the tool is working. The only problem is, it doesn’t know if it should unsubscribe on 0.19.0 to 0.19.3. So it stays in in progress state but still federates the community.
Once all instances upgrades to 0.19.4, it will work correctly both functionally and visually.
Also @[email protected]; the auto add feature is for adding new local communities to the tool automatically. With it, users don’t need to add their communities manually to the tool because it will do it automatically.
But the federation is not relies on that tick. If the instance is enabled, it will subscribe to all communities no matter if auto add is enabled or not.
I guess I need to improve the explanations cuz at this state it is so confusing :) Maybe a FAQ page could be useful.
Also @[email protected]; the auto add feature is for adding new local communities to the tool automatically. With it, users don’t need to add their communities manually to the tool because it will do it automatically.
I see, I thought it meant the manually added communities were put into a queue of some sort and each instance admin would manually choose when they get added. I’m glad that’s not the case. Thank you for clarifying and for the wonderful tool.
The second scenario is viable, if Lemmy was a lot more vibrant, and had enough population that the niche communities could keep you busy. Right now I wake up and check Lemmy and I’ve gotten through all the new posts in 20 minutes. So it’s getting kind of quiet
That’s a really good feature! I hope it gets implemented
For Voyager, I already suggested that they highlight communities for subscribe to when they are displayed, and that would make it easier to subscribe to new communities, so you don’t have to check to see if you’ve already subscribed
Part of the problem is the smaller instances don’t even see those communities when you post, I was unaware of 75% of the communities you just listed. I have a micro instance, and if I don’t subscribe I don’t see it.
It’s probably not much of an issue, given that most people are on a couple mega instances…
Hey, nice to see you here!
I know community discoverability can be an issue. When I launched [email protected] and [email protected], I used my alts on the top 10 instances to subscribe to them so that they would show in the All feed of those instances.
For small instances, I tried to post too to [email protected] and [email protected], but beyond that there isn’t really much I can do.
There was a tool that could help address that (I don’t have the name right now), but last time I tried it, it wasn’t working, so I’m not sure it’s that useful.
Good to be seen! Smart of you to preseed The larger instances good strategy
I think the clients are going to have to solve this, maybe look at the all feed on multiple servers, and then only show you what’s different compared to your own server.
Discoverability is the key weakness of Lemmy, just like mastodon
Not sure clients might be the solution here, I think at the end people will have to choose
Are you familiar with Lemmy Federate? Participating instances get a bot that follows submitted communities to get them in feeds and then unsubscribes once a real user from the instance subs.
Ah, that’s the cool I was looking for! Are we sure this tool is completely functional? The large number of “in progress” instances always gives me doubt
It used to be Lemmy Community Boost and I think it still works despite the status. I do keep meaning to track the developer down and give them a nudge.
I do see now that many instances have auto-add turned off, that could be what were seeing.
I’m not sure tbh. Pretty sure it’s run by the lemy.lol admin?
The tool relies on community local subscriber count to unsubscribe and that value was not available from 0.19.0 to 0.19.3. I fixed the problem about 8 months ago but due to unfortunate timing, it didn’t reach prod from then.
In the end, the tool is working. The only problem is, it doesn’t know if it should unsubscribe on 0.19.0 to 0.19.3. So it stays in in progress state but still federates the community.
Once all instances upgrades to 0.19.4, it will work correctly both functionally and visually.
@[email protected] @[email protected]
Also @[email protected]; the auto add feature is for adding new local communities to the tool automatically. With it, users don’t need to add their communities manually to the tool because it will do it automatically.
But the federation is not relies on that tick. If the instance is enabled, it will subscribe to all communities no matter if auto add is enabled or not.
I guess I need to improve the explanations cuz at this state it is so confusing :) Maybe a FAQ page could be useful.
Thanks for the information - very useful. And yes, an FAQ would be handy, although if you wait long enough it’ll be less necessary.
Thank you for the update! Maybe you should make a dedicated thread with that info here, in [email protected] ?
It’s a nice tool BTW, thanks !
I see, I thought it meant the manually added communities were put into a queue of some sort and each instance admin would manually choose when they get added. I’m glad that’s not the case. Thank you for clarifying and for the wonderful tool.
deleted by creator
The second scenario is viable, if Lemmy was a lot more vibrant, and had enough population that the niche communities could keep you busy. Right now I wake up and check Lemmy and I’ve gotten through all the new posts in 20 minutes. So it’s getting kind of quiet
It is indeed quiet.
I wanted to try something and blocked all news/memes/tech/politics communities last week, my All feed is definitely much more quieter.
Which I don’t mind, but there is definitely stuff to do to get it the communities “beyond memes-tech-news” active
Yeah you pretty much have to use https://lemmyverse.net/communities
There’s a feature request here that would help https://github.com/LemmyNet/lemmy/issues/2951
I remember this one, doesn’t seem to get much traction unfortunately 😔
That’s a really good feature! I hope it gets implemented
For Voyager, I already suggested that they highlight communities for subscribe to when they are displayed, and that would make it easier to subscribe to new communities, so you don’t have to check to see if you’ve already subscribed
Checking [email protected] can be useful sometimes
Consider participating in lemmy-federate.com/ ? That should help.