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

[–] [email protected] 1 points 1 month ago (4 children)

It should be a toggle able setting but whata the issue with @ and # ?

[–] [email protected] 4 points 1 month ago (3 children)

I mean, by themselves, nothing.

The issue is the posting and visibility requirements for a Mastodon post lead to some ugly garbage when translated here. You get shit like

@community @user1 @user2 @otheruser Yep, I agree, this could be better #hashtag #hashtag2 #hashtag3 #hashtag4

Which uh, is not really parsed in any meaningful way, and is 75% noise when put into the format Lemmy uses for a post and/or reply.

[–] [email protected] 1 points 1 month ago (2 children)

I think tags need to be interoperable so tags become sudo communities

[–] [email protected] 2 points 1 month ago (1 children)

Pseudo?

[–] [email protected] 1 points 1 month ago

Yeah thats the one