this post was submitted on 20 Jun 2023
86 points (97.8% liked)
Meta (lemmy.one)
993 readers
1 users here now
A place to discuss or ask anything about lemmy.one's instance or moderation.
For discussion about Lemmy (the software) itself, visit [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Is this actually working for anyone on lemmy.one right now? I have been unable to subscribe to any community/magazine/etc... that's not already federated to lemmy.one for almost a week now.
I've tried searching by URL. I've tried searching by !name@server.
Nothing works, it just sits there. I've hit search multiple times. I've tried to be patient and just come back later and try again. I get there's growing pains, and I'm guessing this server is getting overloaded. If that's the case, the admin posting in Meta "hey we're aware of the problems" would be nice.
I'm not aware of the problems, so I can't make such a post. Looking at this now and searching by URL for magazines on kbin and communities on lemmy instances both seem to work as expected, so I can't reproduce what you're seeing.
I am aware of issues with lemmy.ml, searching for communities that are hosted on that server will often fail the first few times, and subscribing to communities that are hosted on that server often shows that subscriptions are "pending," so if that's where you are searching for communities I can see why it'd be an issue. Federation is a two-way street, so if lemmy.one can't fetch remote data then it won't work, but I've seen many other reports of people subscribing to remote communities just fine, so I don't think there's any issues we're seeing on our end.
I had the same issue though only on jerboa. The website search works fine.
I am on lemmy.one. Are you using jerboa? I posted a similar experience using jerboa and someone suggested logging in to the lemmy website instead and using the web search function to add communities not already connected. That totally works!
I have the same problem on both. Seems like the !name@server nor the full url ever populate. What I am finding is that after some time, if I come back and just type in a partial name (to search federated communities) it'll show up.