Hey 👋 if you don't know us already, we're building Frontpage; an AT Procol based federated link aggregator. We shipped an initial MVP in closed beta recently and have since been thinking about the road to general availability.

This post is an RFC (Request for Comments) targeted at technically minded folks who are interested in seeing the progression of atproto for non-Bluesky/microblogging use cases. All that's to say the language that follows assumes some knowledge about how Bluesky and atproto work! I've tried to include links to explain what all of the jargon means though, so hopefully it's not entirely nonsense for folks a little less familiar!

When you post on Frontpage, we propose that a mirror post will also be created in your Bluesky account. When you comment on Frontpage, we propose that a mirror reply will be created in your Bluesky account.

Conversely, when you reply to one of these mirrored posts in Bluesky - we will show it as a reply in Frontpage.

Additionally, Bluesky likes will be translated to Frontpage votes and vice versa.

you are viewing a single comment's thread
view the rest of the comments

[–] kplaceholder@lemmy.ml 12 points 2 months ago (3 children)

Conceptually, I think the way Lemmy and Mastodon would be able to interop is pretty straightforward: Each thread in either is basically just a tree of replies. They are just shown differently depending on the platform. Furthermore, Lemmy communities show up as Mastodon groups, and Lemmy threads show up as retoots from those groups, which I think is the most elegant solution.

The only issue that makes this interoperation unusable really is that Mastodon groups representing Lemmy communities just "retoot" every single comment, obliterating the TL of anyone who dares to follow those groups. Which as far as I know only happens because Mastodon refuses to be cooperative and properly follow the standards.

As for the other comments asking "why even care about this": I think it's worth as a long-term goal for the Fediverse to entirely separate the "view" aspect from the "content" aspect of platforms where reasonably possible, so that each user can browse all the content in their preferred platform. Not all fedi platforms need to conform to some absolute feature parity, but as I just said, there's basically a one-to-one relationship between Lemmy and Mastodon content, so it is reasonable in this case. I've seen enough people here claim that they very much prefer the Lemmy format to read conversations.

Personally, my Mastodon account has different vibes from Lemmy, and for that reason alone there is a bunch of Lemmy communities I wouldn't subscribe to, but would follow from Mastodon. The only reason why I don't do that is because Mastodon's side of the interop fucking sucks.

[–] tuckerm@supermeter.social 2 points 2 months ago

I think it's worth as a long-term goal for the Fediverse to entirely separate the "view" aspect from the "content" aspect of platforms where reasonably possible

This perfectly describes my ideal fediverse, too. Pretty much everything we're doing here is posting text; it can be a comment on someone else's text, or a comment on a video, or a top-level post in a community, or a top-level post on your microblog (which is basically your own community where you're the only top-level poster). IMO the type of fediverse server you choose should be based on which one has the best UI for the viewing and posting you'll be doing most often, but they should all be able to show everyone else's content as much as possible.

If I need to, I'll create separate accounts for separate interests, like one for games and one for professional things. But I'd like to use the same account for following indie game developers (on Mastodon) and gaming communities (on Lemmy) and commenting on game review videos (on Peertube).

load more comments (2 replies)