@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

Which is part of the story I think. lemmy.ml has a somewhat notoriously slow sign up process. They have reasons for it but it hampers their growth.

Nothing is stopping people from starting their own instances (just like with mastodon etc!) and federating and customising their admin to their needs (and then federating with lemmy.ml).

Yours is, I'd say, an interesting experiment for the fediverse that could be quite informative and even inspiring.

@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]
@MetalSamurai @[email protected] @[email protected] @maegul 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.

@ada @MetalSamurai @fediversenews @[email protected]

What exactly do you mean by mobile here? Like, following any one of your accounts results in following all of your accounts? Something else?

@maegul @MetalSamurai @[email protected] @[email protected] I mean, independent of a particular instance. So you own it and can take it with you elsewhere, rather than it being tied to the instance/community you happen to be using.
@maegul @ada @MetalSamurai @fediversenews @[email protected] I think "mobile" here means changing servers without losing content. Currently you can't clone an account, only take your followers elsewhere and start from scratch. Calkey and Hubzilla, on the other hand, have fully nomadic identity.
@Probably Paul 🌍 @maegul @Kevin Davidson @Ada #CalcKey has full #NomadicIdentity?

As in, you can have identical clones of your account/channel simultaneously on multiple instances? They're kept in-sync with each other in real-time? All clones display the same Webfinger ID which uses the domain of the primary instance? And you can make any clone your new primary instance?

Because this is what nomadic identity actually means.

The only projects known to me that support it are #Hubzilla, #Streams and the now-defunct #Zotlabs projects #Redmatrix, #Osada, #Zap, #Misty a.k.a. #Mistpark2020 and #Roadhouse, basically everything created by Mike Macgirvin after #Friendica.

In fact, I've got my doubts that full nomadic identity can be pulled off without having multiple channels per account/login. And this is another feature which the projects mentioned above have and the ActivityPub-based microblogging/macroblogging/"social network" projects don't.

Or are you referring to how easy it is to move your entire account with everything on it from one instance to another? That isn't what nomadic identity means.
Netzgemeinde/Hubzilla

@jupiter_rowland Thanks for clarifying. I was referring to easily being able to migrate all content to another instance, but I do use Hubzilla for my blogs because I can clone and mirror them and make it nigh-on impossible for anyone to delete them.

Clearly, I was conflating the two.

@ada @fediversenews @[email protected] @maegul It would probably make more sense for an organisation to do it for members. But I’d quite like the simplicity of a one stop shop. I’ve set up several accounts on different platforms to try them out. They’re all obviously me, but not linked, which is a pain.