(https://venera.social/profile/fediversenews)
(https://venera.social/profile/fediversenews)
One of the interesting things I've seen on the fediverse:
blahaj.zone run both a #calckey and #lemmy instance under the same domain/community. (I learnt this by running into @ada@lemmy.blahaj.zone on lemmy, who is also @ada@blahaj.zone on calckey)
See:
https://lemmy.blahaj.zone/
https://blahaj.zone/
I don't know how effective it is in practice, but it sure seems like a great way to foster more diversity and richness in the fediverse experience, especially if some integrations can be built, like mutual ids.
@maegul@hachyderm.io @fediversenews@venera.social @ada@lemmy.blahaj.zone It's worth nothing that the lemmy instance was not spun up to be effective, it was spun up because I wanted to try it out :)
And now it's a part of my daily routine and has a small but growing user base :)
@ada@blahaj.zone @fediversenews @ada@lemmy.blahaj.zone @maegul Are they completely separate or do they share a user database? I’m pretty sure Mastodon will let you use an existing external LDAP service as the authentication backend, but I know nothing much about Lemmy. That would be a cool way to solve some people’s gripes about multiple Fediverse IDs. Have a cluster of Pixelfed, Mastodon, Lemmy, Bookwyrm all sharing a user list. One account, lots of features.
@MetalSamurai@mas.to @fediversenews@venera.social @ada@lemmy.blahaj.zone @maegul@hachyderm.io They're separate. It's an interesting idea to tie them together to a central identity, but as a user rather than an admin, I'm not sure I'd be happy to use a feature like that unless identities were truly mobile.
@MetalSamurai
How would this work. I am assuming a single handle that will be used on multiple platforms. That men's the associated WebFinger doc should contain all the associated HTTP URIs of these services. If they are all present in a single doc, how would the peering server will select from the multiple URIs?
@ada@blahaj.zone @fediversenews @ada@lemmy.blahaj.zone @maegul