Jim sits down with members of the core team building and governing Standard.site, the shared Lexicon for publishing longform writing on atproto. Brooke from pckt.blog, Jared from Leaflet, and Miguel from Offprint cover the design tradeoffs in creating a new shared format, tales of data migrations, strategies for shared governance, and why you shouldn't buy a premium domain name.
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
atproto made simple: publishing lexicons - underreacted
i find some atproto documentation extremely confusing. the section about publishing lexicons is one of those parts that makes me want to tear my hair out. it…
publish: atproto integration by gordonbrander · Pull Request #38 · gordonbrander/italic
Publish italic sites to an ATProto PDS Adds an italic publish command that syncs your site to your ATProto PDS as long-form standard.site records and optional Bluesky posts. italic stays a pure sta...
bnewbold.net
Bluesky released early documentation for the "AT Protocol" (atproto) a few weeks ago, and I've been noodling around with it. Technically, it strikes an appealing balance between rigid cryptographically signed content-addressable storage on the one hand, and familiar web-friendly schemas and integrations on the other. But at an ecosystem level, there are already a bunch of existing open social media projects. Does atproto bring anything interesting to the table? How might it fit in compared to other similar protocols?
Decentralisation and blogging on atproto - Connected Places
The space for blogging and long-form writing on atproto is rapidly developing, and it gives some interesting insight in what decentralisation on atproto looks like
atproto made simple: publishing lexicons - underreacted
#protocolsforpublishers #atproto #mcp #webapplets | Chad Kohalyk
Web publishing is facing its next challenge: a new iteration of centralizing platforms. BUT there is also a new wave of open protocols and standards that can help us gain our independence. Next month in NYC we are gathering a group of frontier technologists and popular web publishers to discuss how we can sail into this next platform shift as captains. #ProtocolsForPublishers Learn more and sign up here: https://pfp.unternet.co We will be hosting talks on #atproto #mcp #webapplets and web payments, and give publishers the opportunity to interact directly with developers working on these frontier technologies. Thank you to Unternet, Graze Social, Free our Feeds, and betaworks for their support.
What's new? - Sri's leaflets
Launching at.new - a new way to create atproto records and share drafts
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
Two Types of Interoperability Without Sharing Lexicons - Wesley's notes
Sharing lexicons is not the only way to leverage atproto’s interoperability
Yep. This is what is missing in the ATProto vision. The lexicons should've been a like schema.org instead of domain name-based. Everyone who wants to improve it can discuss it, similar to, well, schema.org. The frontend must be separate from the content. It's beneficial in many ways.
jack
we have standard.site but wen standard.pics? rn I’m juggling between @grain.social, @flashes.blue & @sprk.so for image sharing 😭
So who's building multi-author publication infra on atproto? Do any @standard.site platforms support this?
Eric Bailey
I have a lot of feelings about the whole CSS-Tricks debacle. Here's me trying to be constructive about it. ericwbailey.website/published/css-tricks-could-be…
New Build Notes article discussing ATProto and how we as developers can go about forming standard lexicons for common datatypes without being overly prescriptive on implementation details that would limit creativity and competition blog.stygiantech.dev/a/3msmoumcr4d23-atproto-stand…
ATProto Standards Bodies—Guiding the Future of the Network
blog.stygiantech.devI’ve been talking to @jimray.bsky.team & @pfrazee.com about ways to spreads the word on atproto — this could definitely work as a format challenges themselves are fun (could base them in cities with active atproto communities) & we could probably make some extras to highlight builders in the space
Knowledgebase Apps
Long form writing. Group access control. OIDC so we can use atproto. The commercial versions would be Notion or Confluence. An open version would be Outline Wiki.
Anytwo and the future of Anytype
Fichiers - La Suite Numérique
Docs - La Suite Numérique
Docs — Turn your team's content into knowledge
Enterprise-ready Wiki for Teams | Docmost
Outline – Team knowledge base & wiki
