Public feed generators drink from a firehose that permissioned data never enters, so a feed that includes space content has to become a syncer, keep a live model of who can see what, and serve a different skeleton to every viewer.
Permissioned Data Shapes: Community-Moderated Content - Nick's Blog
A community can own spaces the way a person does: a club's members post to each other under a dedicated community DID, with a feed space for content, a moderation space for notes, a labels space for filtering, and a single app view as the only window into any of it.
Permissioned Data Shapes: Forums - Nick's Blog
A forum with public categories, private categories, and one set of record shapes across both: members own their posts, the forum owns the submission wrappers that admit them into categories, and moderators deactivate into tombstones instead of deleting.
Permissioned Data Shapes: Notifications - Nick's Blog
A self-keyed space gives notifications a home you control: every app gets an append-only sink to write into, you pick the reader that turns them into pushes and emails, and allowing or revoking an app is an access control you already have.
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…
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…
Adding Content to Reader - Readwise Docs
The Feed is where things go that are automatically pushed to you, such as RSS feed content, and it's divided into two locations: Unseen and Seen. As you find...
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.
RSS Feed to Social Media | Fedica
Fedica's RSS Feed to Social Media auto-posts new articles, videos, or podcasts to 13 platforms via Pipeline, with auto-formatting and thread-splitting.
Permissioned Data Diary 2: Buckets - Daniel's Leaflets
The second in a series of posts building up a solution to permissioned data on atproto. We introduce buckets: a new protocol primitive for creating a shared social context.
Permissioned Data Shapes: Self-Only Bookmarks - Nick's Blog
A self-only space is the smallest shape permissioned data can take: one authority, one member, one repo, and private bookmarks that share a record shape and a write path with public ones.
Permissioned Data: Space Access - Nick's Blog
Stepping outside the shapes series for a deep dive: how space configuration decides which people and which apps get credentials. Here be dragons.
Permissioned Data Diary 4: The Big Picture - Daniel's Leaflets
A special edition of the data diary that sketches out the rough shape of where we're heading.
Permissioned Data Shapes: Polls - Nick's Blog
A poll is a space, a ballot is an address, and read_self is the ballot screen: voters cast and change their own votes while no voter's client can read anyone else's.
Feedrabbit - RSS and Atom web feed to email service
Follow your favorite blogs, news sites and comics by email. No apps to install, no extra sites to visit, your email is never shared, you are in control.
Sixth in the permissioned data series: what spaces do to feeds. The firehose stops at the space boundary, the credential flow becomes your membership source-of-truth, and one feed URI serves a different skeleton to every viewer.
Permissioned Data Shapes: Feeds
ngerakines.leaflet.pub