Does any form of multi-fediverse account type of thing exist?
I mean by this, is there any website that with one sign up would allow you to have a matrix account, lemmy account, mastodon account, etc. If it couldn't be done with just one url it could be made a thing where it would be service.website.tld (so an example would be lemmy.myreallycool.website). Is there anything that already exists like this? I think it would be really cool to just have one home server for everything that you need, and to also have the same identity on all platforms. Another actual practical application of this I can think of is if you want to message someone you know from lemmy but on matrix you could just change the domain (ex: @username@lemmy.myreallycool.website to @username@matrix.myreallycool.website) or something like that. I know that one of the big appeals of the fediverse is that the accounts are interoperable but I still end up using a different account for my mastodon and lemmy accounts for example. I'm genuinely interested in something like this as I think this would be a really cool idea.
You just described (my service, paid hosting) Communick.
Sign up at the main "portal", choose your plan and your username will be the same on all services that you activate. You get your mastodon account as @your.username@communick.com, your Matrix id is @yourusername:communick.com, and your Lemmy account is @your.username@communick.news. Authentication is unified - except for Lemmy, which does not provide an easy way for SSO.
Awesome idea! Signed up immediately but am curious about the payment options, I'm seeing options to sign up for an instance of mastodon, or 10 accounts, or one account with the single account being $9 yearly?
My question is, will I have to pay every single month for every account that I own?
For example, if I have an account on mastodon, lemmy.world, lemmy.ml, lemmy.nsfw, beehaw etc. Would I have to pay for all of them individually?
I'm probably missing something! It's just that while $9 a year for a single mastodon account is cheap @ less than $1 a month, I'd like to have every possible instance available for this one account which under my understanding would cost me hundreds every year?
It's a great idea, don't think I'm shitting on it in any way! Just asking questions bc I'd like to use it just not sure I want to pay for every individual instance I join
I too would like this. I think presently at best you would have to self-host all respective services on your own domain and setup SSO with single IdP for your custom domain. I doubt, though that all fediverse platforms actually support SSO though. And even so you still technically have an account on each platform with SSO.
As pretty as that would be it has its problems. For this to work you need an authentication service. If you use that service for everything then your accounts are linked to this auth provider and you get a problem if that service goes down. You create a single point of failure.
That being said matrix and mastodon support oauth providers. So it is possible to have unified authentication provider for these two. Lemmy doesn't support this yet.
I think at some point the various fediverse components will need to divide up by function, into generic account hosts, generic content hosts, and generic interface hosts. As long as those three functions are bound together, the possibilities for federating between platforms will be limited.
I think a true unification defeats the purpose of federation. That said, I have been using Lemmy Handshake to sync my subscriptions between accounts. I generally use one account to login, but sometimes an instance has technical issues or content seems to be missing so I like having a backup option in a pinch.
Then, would it be a better idea to create one mega-fediverse app that combines but also separates all the different features of each platform (eg: when viewing it on a browser, it would have a Lemmy tab, matrix tab, mastodon tab, etc) and then have the functionality and format be separate for each one of those instead of trying to pull a "can do everything, good at nothing" type of platform? That would solve the email issue, but I feel it would be more complicated to implement but I've also never developed anything remotely like that ever and so I'm not qualified to speak on it.
Honestly, I feel like the answer you're looking for is a federated single sign on app. The real challenge will be building the right tools and community mindset for determining what a "trusted" instance is.