After playing with Attie for a bit, I think I get what they were going for. It is a tool to help people understand feeds and easily generate them tailored to their own particular interests. What it won’t do is replace bespoke feeds. I’ll share a few thoughts: 🧵1/11
Mar 31, 2026 at 2:53 PM
omni social | reclaim your feed
The fun side of the internet. Social video, messaging and more. Built on the AT Protocol.
Skyreader: A RSS Reader on the AT Protocol
Introducing a RSS reader for the AT Protocol where you feeds and article sharing are portable
Skyreader: A RSS Reader on the AT Protocol
Introducing a RSS reader for the AT Protocol where you feeds and article sharing are portable
Riven
A modern platform for original content, genuine conversation, and a feed that's actually yours. Built on the AT Protocol.
Current
An RSS reader that doesn't count. What happens when you stop treating your feeds like an inbox and start treating them like a river.
Custom Feeds Are Not Communities — A Design Theory of Feeds and Commons - Nightflight
Beginning I learned something from Hamakaze no Ryodan, who has deep expertise in creating Bluesky custom feeds. Feeds collect posts without the poster's co…
Middleware for Feed Recommendation in Practice: How Feed Creators Build, Maintain, and Sustain Custom Feeds on Bluesky
Scholars have long proposed third-party middleware as an alternative to centralized algorithmic feeds: feeds built and distributed by independent feed creators. This vision saw no large-scale instantiation until Bluesky, a decentralized microblogging platform, introduced custom feeds in 2023. Although central to the middleware ecosystem, we know little about how feed creators understand their role, build feeds, and sustain them. Through interviews with n = 26 feed creators and third-party developers of feed-building tools, and analysis of n = 88,302 custom feeds, we identify two creator orientations---utility-providing and community-building. Additionally, creators struggle to maintain feeds that fully realize middleware ideals: they lack granular interaction data, receive little feedback, and lack technical expertise to act on either. Finally, creators sustain their feeds as unpaid hobbyists with little platform support and are divided on whether to monetize beyond covering costs. We conclude with design and policy implications for strengthening the middleware feed ecosystem.
Making a feed is really easy
Aturi is a new service that provides universal links for traversing/sharing content in the ATmosphere. Share @bsky.app posts or @atproto.com data with in a way that lets recipients choose where they want to view it — @blackskyweb.xyz, @leaflet.pub, @anisota.net, @pdsls.dev, and more! aturi.to
aturi.to - Universal links for the ATmosphere
aturi.to
Anisota
ATmosphere Waypoints Powered by a new sister service called @aturi.to, navigate to different areas of the ATmosphere automatically like @blackskyweb.xyz, @leaflet.pub, and more. ➳ Jump to clients or apps ➳ Copy links to specific waypoints ➳ Configure default waypoint behavior anisota.net
Attie feels disconnected from what their user base is going to respond positively to I bet, which makes me wonder if they build things in service to their community or not. With that said, Graze has had (something like) this forever and didn't get the same backlash. That's worth acknowledging.
@attie.ai is interesting in many ways. With that said, use @graze.social if you actually want to manage a feed.
Lol no worries I think at least a few very basic functions of feeds could be simply improved if there was an innate way to treat individual hashtags as feeds, or if beside feeds people could also create collections of manually saved posts (cause some people use feeds to organize their own posts)
@toni.bsky.team @alexbenzer.com i think yall need to wrestle with the fact that the app’s most distinctive feature (“custom feeds”) is something only (relative) nerds use and benefit from. normal people won’t swipe between many algorithms or whatever. have a look at past designs for “communities”
