[drdaeman]

This works with email, but not so much with Fediverse. There is no standard or - AFAIK - even attempts domain/account sharing (unless you hack your way around), you'll have to be [e-mail] and [e-mail] and [e-mail], but not [at least not easily] [e-mail] if you want to use it with multiple systems.

[ajdude]

I had absolutely no issues with hosting my own mastodon, I pay $7 dollars a month for a VPS with backups. I'm the only user that can register on my instance so it's just me.

I'm `@[e-mail]` and I can follow and have conversations with other mastodon users of various servers seamlessly. I was just doing it this evening in a thread while tagging four different people on four different servers. When people tag me in posts it just looks like `@aj`

This is the right way to do this stuff in my opinion.

[drdaeman]

> I had absolutely no issues with hosting my own mastodon

Just Mastodon - it's not what I'm talking about. Please let me know if my parent comment wasn't clear enough.

Mastodon certainly works and you can be just @aj (as long as no one else with the same host-local part walks in, I guess) no matter where the actual conversation is hosted. But what about Lemmy, Peertube, or other Fediverse systems? I'm aware that Mastodon can talk to them with some success, but AFAIK it is only optimized to present certain types of content, so if you want Reddit-like user experience rather than Twitter-like one you want Lenny. And then you need a different subdomain. And then you realize you're splitting your identity on the same network in two - and in my opinion that's an indicator that something is wrong.

[v64]

>I'm aware that Mastodon can talk to them with some success, but AFAIK it is only optimized to present certain types of content, so if you want Reddit-like user experience rather than Twitter-like one you want Lenny.

This is partially true. I run Pleroma, which is a microblogging server like Mastodon, so Mastodon content that federates to my instance shows up identically to my own posts. On a system like Lemmy, when their posts federate to me, what I see natively on my instance is a person posting a link that links to the originating website. I can see some replies inline, but they're linear and not threaded like on Lemmy. However, unlike what you said, still using my @[e-mail] identity, I can click the link from my instance to the Lemmy instance and interact with the content there natively. No need to create a different subdomain. There's no need to host a Lemmy instance yourself if you want to interact with Lemmy instances. Lemmy on the backend is still talking the ActivityPub protocol and it's only the frontend that alters how the posts are presented, so as long as your server speaks ActivityPub, you can use the same identity.

[ajdude]

Are you saying that the primary issue is that for each federated service we need a separate account / instance for it as opposed to email which is just one email account? I don't disagree with that but it's the same situation for Reddit, YouTube, Twitter. I have to maintain separate accounts on those platforms too.

[drdaeman]

Yes. And I get it that we all have separate accounts. The difference is they're entirely separate networks, not one. If I'm on Fediverse, and self-hosting, with my own domain, it's fairly natural to want to have a solid identity, isn't it?

Which is where it's different to email. When self-hosting mail, you can have separate identities too, but those will be created on a purpose (different addresses for different personas/purposes), rather than fragmented because of necessity.

[myaccountonhn]

But you don't have separate identities for Youtube, Gmail, Meet et.c. For a federated internet, you should have the same ID for all federated services so that you can build the same product experience as with Apple or Microsoft or Google.

[JoshTriplett]

It'd be nice if there were a standard forwarding-interoperability server such that several services could share the same account name and local copies of the messages to/from that account. But in the meantime, having @[e-mail] be a Fediverse service like Pleroma or Mastodon, and then having @[e-mail] be the handle for each specialized service, still seems preferable to using a third-party server. And if in the future some mechanism exists for those services to share, you would then be able to use the standard redirect mechanism to preserve the old names while using the shared top-level one as the canonical account name.