I’m running on a personal lemmy instance, and I’ve been able to simply re-subscribe to the communities that I was subscribed to on my previous lemmy.ml account.
But what if I didn’t have that? How would I discover those communities?
On the micro blogging fediverse, I can use relays, follow other peoples boosts, or join gup.pe groups etc for content discovery and to give me federated content in general on which to do content discovery.
What does that look like in the lemmyverse niche of the fediverse? How does a small single person instance find new content? How do they get richer content search options etc? Right now, I’m just using search on lemmy.ml for that, but that’s a work around, not a solution
It would be pretty easy to write a bot which does this automatically. Problem is that you could easily end up with a lot of spam or other unwanted content.
Pulling all communities would definitively lead to unwanted content.
Since it’s basically a work-around for the local only (incl. already pulled communities) search, more ideal solutions could be:
Having some way to discover unfetched content (even if only from already federated instances) would be a significant addition to Lemmy!
@dessalines@lemmy.ml @ada@lemmy.blahaj.zone
Are you talking pulling in posts from all of the groups on remote servers or just a list of groups? My thought was I just want group names to appear in my list when I search for them. I don’t care so much if the content doesn’t come through right away, as long as I can find the right group.
Just the overview, similar to local search. Titles, usernames, perhaps thumbnails and text excerpts of posts.
Honestly, my ideal solution would just be some sort of implementation that makes my lemmy instance aware of the groups on other lemmy instances that I federate with, so those groups turn up in searches. It will grow organically that way even without active seeding
How would you feel about bundling this type of automatic discovery into lemmy, as an optional server setting (default off)?
It’d be one of the periodic maintenance jobs we already have in there.
Not so good, because this would require a lot of customization options to fetch communities according to different criteria. I think this makes much more sense as an external tool, then it can have a config file or be forked for different behaviour.
I’d love to see it. All it needs to do is explore the list of groups available on the servers we federate with. It doesn’t need to be universal search, it can grow organically.
What about a public API-endpoint listing an instance’s communities, e.g. with the data already provided in the community sidebar?
That already exists, there’s a dedicated getcommunities endpoint… and a search that can search for communities.