They have completely different client API's so no it's not compatible. Quite a different UX as well, I don't think it would fit in well.
I'd love to be able to use 1 login for all of the Fediverse though, just switching clients based on the UX I want at that time.
I’d love to be able to use 1 login for all of the Fediverse though, just switching clients based on the UX I want at that time.
Amen that.
1 login for all of the Fediverse
At least for Mastodon <-> Lemmy that can be done. From the screenshots, I see you can get inbox from Lemmy users in your Tokodon.
Guess I'll use Lemmy in my browser for now.
Technically if ActivityPub instances served as an actual SSO, you'd be able to connect to a Lemmy instance via a Mastodon client, but that's not how this works.
ActivityPub is all about activity, i.e status updates, messages, etc. It's up to each instance to verify and maintain the user experience.
If someone were to make a client that supported logging into any instance without the need for the Mastodon API, then you'd still not have a SSO, because then you'd just be connecting to a different instance using a client.
True SSO means being able to create new accounts on a platforms using the identity of another platform, a'la Google, Apple, GitHub, etc. That would require implementation on both backends.
Then there are platforms with nomadic accounts, if they still exist.
Point is there is really no standardised SSO for the fediverse, at least not yet.
You can yes, but you have to decide to either be stuck with Mastodon UX or Lemmy UX. They're both different and I like to switch UX whenever I please, and currently I need 2 accounts to do so.
KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.