this post was submitted on 12 Sep 2025
214 points (99.1% liked)
Fediverse
36820 readers
201 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It usually comes down to a difference in vision, the fediverses schtick is that you can follow Reddit from Twitter or whatever, whereas on atproto you use a different appview for different formats, like frontpage.fyi for links, and whtwnd.net for blogging.
It's a difference in vision, but I don't like BlueSky's vision here.
Combining the Reddit-like and Twitter-like experiences in one place is a little awkward, but following a blog or a Youtube-like from a Twitter-like isn't. Having the option to switch to a more optimal appview is great, but realistically a lot more people would follow a blog from BlueSky than would use their BlueSky identity to sign into WhiteWind.
Well, it's a bit more than just using their identity to sign in, data is also stored on their PDS.
It's entirely possible to make a server that accepts several different lexicons, wafrn plans on doing this for articles.
When a substantial fraction of users are actually using an appview with that trait, that will be great.
Sure, but its not a fault of the protocol itself. You could easily choose to discard
article
ornote
objects on ActivityPub.You can write software to filter on arbitrary criteria with ActivityPub, or email, or IRC, or virtually any other protocol. My point is that ATProto is designed to actively encourage it, and the flagship implementation does so. Subtle hints in interfaces have a big impact on how people, including developers use software.