@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 @[email protected] on lemmy, who is also @ada 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.

Blåhaj Lemmy - Choose Your Interface

@maegul @[email protected] @[email protected] 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 @fediversenews @[email protected] @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
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 @fediversenews @[email protected] @maegul
@aswath @ada @fediversenews @[email protected] @maegul No, they’d be separate but linked. So @[email protected] @[email protected] and @[email protected] would all be created at the same time and refer to the same user in a shared LDAP user database. Maybe the alsoKnownAs field would be useful? Some people would love this, others will hate it.

@MetalSamurai @aswath @ada @fediversenews @[email protected]

I’ve seen someone implement a simple solution, I think, where effectively one platform stands as the single point of authentication and am the others defer to it. I forget how it was drive, but recall once you worked out the details it was utter straightforward to get mastodon to be the single point.

@maegul
Did the scheme you saw use diff handle for diff services, but use a single auth scheme? If not, when a federating server wants to post an article, how would it know the specific end point? If yes, then I suppose OAuth could be used to do auth.
@MetalSamurai @ada @fediversenews @[email protected]