this post was submitted on 03 Jan 2023
19 points (100.0% liked)
Lemmy
12538 readers
4 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I was hoping that groups from instances that my instance knows about would show up in group search, but that doesn't seem to work either. They only show up in search if someone from my instance has subscribed to them.
I had someone from a science based instance reply to me somewhere, and so that instance now appears in the instances list for my lemmy instance, but the groups there don't show up from a plain old search. I have to go to that site, find the group, get the URL and then search for it on my site, which is a pain.
And of course, lemmy is still in development, so I can work with that, but I was wondering if there was a future vision as to how it might work?
Federated communities do show up both on the search page, and the communities page.
https://lemmy.ml/communities/listing_type/All/page/1
But looking from Ada's instance: https://lemmy.blahaj.zone/communities/listing_type/All/page/1
You don't see all lemmy.ml communities. Unless this is a case of "federation takes some time" (might be, I'm not very familiar with the inner workings) it seems that the only communities known to lemmy.blahaj.zone are those that have been searched for.
Yep that's correct, instances don't automatically connect to all communities. Someone from that instance has to subscribe to it first, for that instance to start getting updates.
Right, but that's the very problem I'm trying to solve! On a tiny instance, most of the communities I'm interested in on other instances won't have anyone subscribed from my instance. It will be me being the first to subscribe. So I'm trying to find a way of finding them when no one else follows them yet :)
NRSK uses an admin-run "Fetcher" account to subscribe to various extenal communities and pull interesting content to our home "All" timeline. It's a combination between browsing through communities on known and/or federated instances, and using join-lemmy.org to find new and unconnected instances. It's all manually, which is a bummer but better than basically only local content for fresh users.
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.
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.
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.
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.
That's an interesting idea! Not so relevant for my particular circumstances, but it's a good idea if we ever do start to get more users in!
Yeah you're right about groups/communities not showing up in search or the communities view. That's unfortunate that they don't all federate upon discovery of the instance. I kinda assumed discovery of the instance was discovery of all communities.