this post was submitted on 17 Jul 2024
20 points (100.0% liked)
Furry Chat
682 readers
1 users here now
Yiffit chat! Talk about anything you want here.
Mention @[email protected] from your favorite Fediverse / Mastodon client to post here directly, or post directly via any Lemmy instance.
Community Icon (CC-BY-NC-SA) Tom Fischbach
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
ActivityPub only goes so far, which is why you have such diversity in Fediverse applications.
However, I do want more consistent experiences over the Fediverse.
For example I haven’t yet found a way to view Mastodon posts on Lemmy (unless the posts mention a community), but the other way round is fairly easy.
Also I would like that client and server are more detached so I can use a Lemmy UI on a Mastodon instance or vice versa
So this got born out of the question of direct messages. Intuitively, I would expect those to just work, a user is a user, a message is a message. As far as I can tell, you can't direct message. I haven't played around with mentions yet. As far as viewing posts, its bad both ways. For example, this is the only post I see in this community from Mastodon. I think that is due to the same discovery issues throughout the fediverse, that is, if you don't already know about it, you won't find it. And when you discover, you might only see new things unless interactions are done to old things.
For lemmy, the UI and the server are completely separate. There is a moderately well documented API for interacting directly with the server.
Some kind of unified account creation would help with this, I think. Something where you create an account somewhere "central" (which I get is kind of antithetical to the fediverse mentality, but work with me here), and then can "link" that account to multiple fediverse servers.
Right now, I can create an account on pawb, and I can create an account on yiffit, but even though they might have the same username, they're completely separate. It'd be ideal to be able to link those both to a single 'meta' account, which would then allow me to log into and browse either service, while maintaining a unified post history, etc.
Basically, someone clicking my profile on either service would see my global post history across all fediverse services I'd linked.
This could indirectly assist with the discoverability issue slightly. Rather than being on Mastodon, trying to view Lemmy threads, and seeing only new things where specific tags were used, the user could link their account to Lemmy servers (or other Mastodon servers or whatever), and be able to use one unified identity to browse each of those services independently.
Technically there's nothing stopping someone from having accounts on multiple services now, but having those accounts be completely independent kind of defeats the purpose.
I don't know how antithetical it is to the fediverse mentality. You could have a server that talks a wide variety of activity pub and on the client side you select your view and you can have a forum like view or microblog format, or a images format. I thought the whole point of the fediverse was interoperability between servers and services.
I have this account as primary, I have a backup on pawb, an abandoned one on world (different user name), and now one on furry.engineer. I think discovery is a core shortcoming of the fediverse. Activity pup can't send everything everywhere if it doesn't know where everywhere is.
@l_[email protected] That's actually exactly what Mbin can do, i can switch between microblogs and threads view, so I can both follow accounts from the wider Fediverse and interact with Lemmy communities (almost) seamlessly
@[email protected] @l_[email protected] @[email protected] @[email protected]
Lemmy doesn't have any kind of interoperability with Mastodon (outside of the specific use case you mention), but kbin has interoperability with both Lemmy and Mastodon content, for what it's worth.
I believe kbin is dead, mbin is the active fork.