Today's summary: - migrated my PDS out of Docker (on the same server) - migrated my Mastodon instance from an ARM G11 at Netcup (Geekbench single core: 986) to VPS G12 (GB single core: 1982 😏) - I think it feels faster 😅

Also, when you open the page you're greeted with this 🫣 https://lab.martianbase.net/xrpc/com.atproto.sync.getBlob?did=did:plc:oio4hkxaop4ao4wz2pp3f4cr&cid=bafkreidzbos3c6xjidjhmxkdb3c5ehgzow4ke3beh3l5rxq7zckuxem3gu

Btw I liked your comment there!

Ok, I'm gonna try to decontainerize my PDS, if I don't come back, it's been nice knowing you 🫡

I'm wondering what was changed that many people are only now getting a popup requesting setting birth date in the profile, when I think this was a thing for a long, long time (see below)? 🤔 (yeah, I know it's connected to the verification, but wasn't it required already before?) View quoted note →

bsky.app/profile/bsky... View quoted note →

- is there any way for a client to detect if the service is expecting acks or running in no-ack mode, or does it need to have this hardcoded?

- does the acks mode mean that the service sends one event and then waits until it gets an ack in response before sending another? or that it streams them normally, but if they aren't acked at whatever point later, they will be re-sent on next connect?

In case you missed it: there's also a corresponding Tap client library in JS in the atproto repo for connecting to the Tap service: github.com/bluesky-soci... atproto/packages/tap at main ·...

- do I understand correctly that this is meant to have basically a single consumer (as opposed to jetstream having consumers processing copies of the same stream), so things like acks are tracked globally, not per connection?