This blog and its posts are now on ATProto, the data backend that powers Bluesky. To what end, I couldn't say just yet. I'm just playing around. This didn't involve any changes whatsoever to the website that you're looking at[1]. It just means that when I publish a new post I also write a new record into my Personal Data Server (PDS) which includes the post's title, publication timestamp, and a URL. This gets slurped off by ATProto relays that subscribe to me and if there's anybody who cares about my posts, they get to find out about it more or less in realtime.
ATProto, POSSE, and Personal Sites
My little weekend experiment to bring micro updates to my personal site
What is atproto?
What is atproto? atproto is two things: A protocol for creating open social networks An open social network atproto, the open social network Today the atproto network has 36+ million users and powers Bluesky and a handful of other apps. Almost all atproto data is public. Content like posts, likes, follows, and photos/videos are publicly accessible to any network participant in a permissionless way. As an example of how open the network is, here’s how easy it is to stream all public data on the network using a public atproto Relay like bsky.network:
Becoming a better atproto citizen
The blog's standard.site records now carry cover images, a publication icon and theme, and the strongRefs Bluesky uses for enhanced link cards.
@essentialrandom.bsky.social's livestream on Streamplace
Day 4 of Reading the ATproto permissioned data spec (dramatic)
Introducing ATProtoFans: A New Way to Support Creators You Love - ATProtoFans Blog
Welcome to the new atproto.com - AT Protocol
We've updated just about everything about atproto.com to make it easier for developers to just build things.
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
I love atproto bc wdym I can post my @leaflet.pub posts to my @bsky.app and then those can show up immediately on my @blento.app AND people can read these posts from any other compatible atproto blogging site like @pckt.blog ???
Andrew🪴
First ever Leaflet?? And a homelab???
My recollection of this is that even if you just pop a new ATProto account into existence and start spitting out `app.bsky.feed.post` records, they don't show up unless you actually go through a Bluesky onboarding & agreeing to ToS, so they should have an email for you through that process.
My website is now on the Atmosphere! I've been building atproto apps for a while (@skyreader.app, Skyboard, SembleIt). Now my website is one too. Blog posts are @standard.site records on my PDS, rendered by a SvelteKit app. But also... 1/2 disnetdev.com/blog/an-atmospheric-website
An Atmospheric Website
www.disnetdev.comMy blog is all ATProto-powered -- you can click most records to see where they're hosted on my PDS. My website (cameron.stream) now: - Shows my @leaflet.pub articles - @at.fund endorsements - @margin.at annotations - @semble.so collections fuckin love atproto dude
the critical thing that got me on board with atproto is relays incrementalize sync of the entire dataset, which eliminates polling when crawling the old web is currently being crushed under crawler load and I don't think it's going away, so I think atproto is the only way to save the open web
