Just migrated my personal site from Squarespace to self-hosted, consolidating it with my Bluesky PDS on one server using Caddy's host-based routing. Hit every possible gotcha. Here's what I learned about DNS propagation and certificate acquisition. ๐งต
Tiny self-promotion: I maintain a simple Ansible playbook for maintaining/installing my own PDS.
The most interesting part is the Caddyfile -> github.com/fry69/altq.n...
It includes support for @baileytownsend.dev's 2FA gatekeeper.
Maybe this also helps for inspiration.
wait nvm it *was* CORS. set it on the .well-known dir and all is well now
pds.ls/at://did:web... still shows "missing PDS"
it's set on both my PDS and on lizthegrey.com now
There are some sharp edges, for instance @pds.ls doesn't fully work on did:web accounts.
Join me as a did:web!
This blog post on the @atprotocol.dev site has my byline on it.
We may have some other takes to share, @knowtheory.net has been thinking this through for a while.
The tone here is - welcome! We're happy to have you, hope you'll lead with joy and dig in to help out.
I've found myself retyping a lot of the same troubleshooting tips if someone has problems accessing Bluesky after an account migration. So I wrote a checklist, a self-guided troubleshooting guide! So if you or someone you know finds they can't post after migrating, maybe give this a read.
if you work on Atmosphere/ATProto-related things and need a technical writer or simply someone to give a cool name to a thing you're working on, i'm available on a freelance basis
send a DM on here or email at@heika.dog
I finally wrote that essay about how I got an IPv6 prefix of my own to serve pds.lizthegrey.com on: whtwnd.com/lizthegrey.c...
First community labeler taking actions on atproto using @roost.toolsโs Osprey. entire Ozone and Osprey stack running on a $50/m OVH machine, with up to seven days of full firehose backfill for investigating patterns and exploring the network.
New year, new job. And it's been updated on the ATmosphere thanks to @protopro.blue. beta.protopro.blue/profile/lizt...
(don't worry, I am not going anywhere, I'm still at @honeycomb.io, just wearing a different hat!)
we pretty clearly acknowledge that Cloudflare and Fastly are online intermediaries but not a publisher, for most purposes.
to what extent is a relay operator or appview operator exposed, if they are an indiscriminate conduit for content that lives at rest elsewhere?
I think there are some very open questions with distributed PDS network and appviews as to whether an appview is a publisher if it is merely a proxy to view content that's hosted elsewhere.
see, whtwnd, would you argue it is a "publisher", or merely a portal to view content that lives on PDSes?
Wrote a getting started guide for Tap tonight! The new tool from Bluesky to backfill records and track future ones easier. Includes install directions, some explanation of what it does and how to configure it as well to help you get started.
Nerding out about the question of whether the client or the server should be the one who speaks to the PDS
DIDS: 21,147,892 Link targets: 1,942,647,037 Linking records: 10,009,837,457
yup that's officially 10 billion atproto backlinks
indexed by constellation
across every lexicon
that you can query
at constellation.microcosm.blue
Announcing ATmosphereConf 2026, coming to Vancouver March 26th to 29th.
We've got the full announcement and future news and updates on our new site news.atmosphereconf.org/3m3cwwz4mpk2j
Oh hey, looks like Blacksky has its appview up! I can see @spacelawshitpost.me / @did:plc:63hvnyjvqi2nzzcsjgnry5we via slingshot.microcosm.blue
Check it out! blacksky.community/profile/did:...
In other news, the ATmosphere treats censorship as damage and routes around it! XD
ASCII art at the Blacksky App View homepage
2421 evts/sec throughput
Fetching my own profile from the blacksky app view
123 MiB/s inbound bandwidth
Cooking up an app-view ๐ง๐พโ๐ณ
a bunch of folks are wondering about how mod comms work for other PDS instances. this is also a problem for, eg, labelers trying to reply to appeals.
the plan is this proposal, which we have been making slow progress towards (it has been a very very busy 12 months for mod eng team)
for atproto devs and protocol watchers, I published an overview of the network moderation architecture.
it tries to cover all the mod actions possible for each service type. this design has been around a while, but not well documented.
this doc is not very polished, but could clarify some details
So there's nothing stopping me from using developer tools / chrome extensions to override the Atproto-Proxy header for interactions between a web client and my own PDS, right? I can make that decision independently of Blacksky (or Bluesky PBLLC even!) changing their minified JS code?
+1 on that. Iโve been doing my appview stuff since December and spent ages going โwell itโs not that important yetโ and here we are
We've been working on a moderation inbox protocol but it hasnt quite shipped yet, it's being prioritized.
It is done.
@pds.labeler.tny.im exists now, which is good because @decentralised.goeo.lol deactivated.
btw you can assert this via a custom DID assertion! see for instance mine which asserts I am also @web.lizthegrey.com: web.plc.directory/did/did:plc:...
