I still have many different accounts on matrix, lemmy, mastodon, etc. and although you may communicate somehow, it doesn’t work properly.
Why would I trust a random Lemmy server admin with authentication for anything other than Lemmy?
You can use federated SSO. The remote site never sees your credentials but only a token that you’ve been authenticated against your home instance.
That being said, that’s probably the problem, in order to do federation a small degree of trust is required between the two instances. I guess that is already done with activityPub since you’re getting content from remote instances.
a token that you’ve been authenticated against your home instance.
I assume you are talking about OpenId Connect (or OAuth 2.0 but that is basically what OpenId Connect is based on) here. The crucial bit that didn’t really work out with this is the part where users just specify their OpenId Connect provider at login time. All uses I have seen in at least 10 years have a fixed list of providers to choose from because of these trust issues.
Federated ID was a thing for a while. Mozilla ran their Personas service for this exact purpose. OpenID, which is still used for single sign on, was once part of a federated standard. You could use any federated identity provider to sign into any federated website, or you could set up your own.
Almost nobody used the federated part, so all but the most prevalent auth providers (“log in with Facebook”) stayed around.
In theory, you could use the same account for a whole bunch of systems. Mastodon and Matrix both support OAuth2 I believe, so an operator of multiple services (like the Jerryverse) could use SSO to group services and provide accounts under a single login.
There are a few challenges to be solved, though. First of all, if you have a single account, you may expect messages and posts to appear on every single service. That’s just not how ActivityPub is designed to work (it can be, with a smart proxy and some shenanigans, but it’s not going to work reliably). Second, you’ll need support from all services. Kbin and Lemmy have had open feature requests about this for a while, but it’s not high on the priority list. Third, Matrix isn’t interoperable with the ActivityPub platform, so that’s going to need a completely different server setup on the side.
In theory, everyone could implement OpenID and let you log into Mastodon with your Ubuntu One account, but in practice the general public doesn’t really understand how it works.
As for communication, almost every ActivityPub service but Lemmy and Kbin interoperate just fine. That you can’t follow Mastodon accounts on Lemmy is more of a Lemmy shortcoming than a failure of the wider Fediverse.
Matrix just isn’t interoperable with ActivityPub, though I’m sure someone could write a bridge that’ll allow cross service communication. It’s a different protocol built on top of different concepts.
Federated ID seems interesting but impractical. Take your home instance ID and use it to auth to another server, nice to have if the home base is down but if the home is down then how does the remote host validate the user in a realtime sense? Storing tokens or creating a local version of the account would be possible but if the user was banned from the home base then you have to trust replication to clear it from the remotes or have a short enough token expiration to know they need to revalidate against the home base after X time.
A ways out of my expertise, I work more on the lower layers of connectivity so maybe I’m overthinking it. What could be helpful would some sort of local app setup that would create an instance with an easy executable. Creating spontaneous servers has playing with fire potential and doesn’t address domain creation or port allocations, but with the certbot/acme systems out there it seems like it wouldn’t be too far out of the realm of reality. Musings of a mad scientist…
Typo in title. It should be: “solve the problem”
The pixelfed dev even wrote his own chat system instead of integrating matrix or xmpp
Titles are editable on lemmy
Appearantly not on thunder
Hmmm… this is why I have like 15 lemmy apps on my phone. Every app is a random selection of features, and no app seems to do everything
I did that as well. Last week I uninstalled infinity after thunder solved the profile loading lag. Appearantly it was too soon.
Is Sync not good for you? I stopped app-hopping after Sync came out.
Unfortunately, at the moment, I’m running an iPhone. Have been for a few generations after my pixel 2 started giving me unfixable GPS issues while I was trying to do Uber/delivery work.
Thunder can’t edit posts at all yet.
We have XMPP accounts integrated with our Lemmy instance already. Lemmy doesn’t make that easy out of the box, but you can just hook up an XMPP server directly to the Lemmy database.
I can see that this should work great but I also hate it.
Really wish Lemmy would get SSO support, but I don’t really understand the Lemmy backend API design enough to make the necessary modifications myself without messing something up. The lack of official support also makes it so that you can’t expect any kind of third party application to authenticate if you use your own SSO fork.
There are two active issues on this:
https://github.com/LemmyNet/lemmy/issues/2930
https://github.com/LemmyNet/lemmy/issues/1368
Maybe someone will get around implementing this eventually.
Post titles can be edited after posting, at least on Lemmy
Integrating something like Matrix is not an easy feat, there is a lot of heavy lifting being done in the background to make things easier for us users, like key generation, message signing, verifying logins etc. that another dev may not have the time or resources to implement. Lemmy partially solves this with a dedicated message button if you have a Matrix account linked
Damn that behavior is new and a good step :)
Re: matrix, there’s a lightweight Matrix client that you can embed by basically adding an HTML div and adding a script file to the page. You probably don’t need a full Element embed for basic messaging. In theory Lemmy could add a chat box relatively easily, but then instance admins would probably have to deal with configuring the right security headers and such to make this possible.
It should be public key accounts like Scuttlebutt, you know it should.