I added Lemmy to the list of my self-hosted fediverse services, here’s what I think about it and how I made it more useful in a single-user instance configuration.
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to !firstname.lastname@example.org.
Thanks for the script! Gonna try that out today, great test for a lazy Saturday morning.
Communities will be stored forever, unless you manually go into the database and delete them. Even the delete buttons on the frontend only hide them.
Oh that’s good news, thanks!
The search idea is neat, but I think Lemmy should fix this upstream. Add some way for remote instances to discover communities on the network more easily.
This would quickly get complex, as it would require configuration options for instances to fetch from, fetch interval, number of communities to fetch each time, etc. At least for now i think its better to have an external tool. But it could be linked in the docs so other admins can easily find it.
Yeah agreed that’s a workaround but this issue is common for services relying on the fediverse and more globally for decentralized services.
I mean you can’t expect to know each and every e-mail address of every domains when you sign up with a mail provider. You would need some kind of agreement between two providers to share user lists.
I’m not well versed into activitypub but I don’t think such a feature exists. I guess because of privacy concerns amongst other things.
Yeah for sure. Discoverability ain’t a trivial topic in a decentralized/federated context, but it needs to be tackled.