AT Protocol Developers

AT Protocol Developers

@atproto.com

Social networking technology created by Bluesky. Developer-focused account. Follow @bsky.app for general announcements! Bluesky API docs: docs.bsky.app AT Protocol specs: atproto.com

121.6K followers21 following282 posts

AT Protocol Developers reposted

🪐 spaces alpha release 🪐 folks, this is the big one! lots of updates across pretty core protocol mechanisms. hopefully the last/only of it's kind (tho we are planning another release next Thurs)

discourse.atmosphere.communityAtproto spaces alpha updatesWe just cut another spaces alpha release today! This is the biggest yet, there are multiple breaking changes across core protocol pieces. This is likely the last/only release of this size. Though we ...

If you run an Ozone labeling/moderation service, this Ozone container update has a mitigation for just the eMudhra intermediate CA compromise.

Foysal@foysal.it

Ozone release v0.1.106 is out with the same runtime mitigation github.com/bluesky-soci... if you have watchtower enabled, it will auto update midnight UTC otherwise run `docker compose -f /ozone/compose.yaml --profile daemon up -d --pull always ozone ozone-daemo`

If you are running the stock PDS distribution, it should auto-update in the next 24 hours with a mitigation for the eMudhra intermediate CA. Or you can also update manually (see below). The latest tagged version is 0.4.5043. github.com/bluesky-soci...

bryan newbold@bnewbold.net

new reference PDS container has been published! if you do the classic self-hosting auto-update setup, you can force a faster refresh with: sudo pdsadmin update and while you are in there why not: sudo apt update sudo apt upgrade

View full thread

For those who run Node.js services—we are currently still waiting for a Node.js security release. In the meantime you can apply a runtime mitigation by adding `--import=@atproto-labs/fetch-node/emudhra-preload` to your service entrypoint. More details at: npmx.dev/package/@atp...

Updating operating system CA bundles is recommended, but they don't impact containerized environments (e.g. Docker). And lots of software does not inherit from the OS by default.

We have put together DID and handle resolution vectors that you can use to check if software you run may be vulnerable. The following handle should _not_ resolve to a DID: '@emudhra.divy.zone' The following DID should _not_ resolve to a DID document: 'did:web:emudhra.divy.zone'

Both resolutions should fail with TLS/SSL errors: ``` $ goat resolve emudhra.divy.zone error: handle resolution failed: HTTP well-known request error: Get "https://emudhra.divy.zone/.well-known/atproto-did": tls: failed to verify certificate: x509: certificate signed by unknown authority ```

AT Protocol Developers reposted

A little scoop before Oct 7, when ICANN publishes 1,000+ applications for new top-level domains: one of them is .bsky! It's a long road (18 to 24 months), but if it goes through, handles like alice.bsky become possible.

AT Protocol Developers reposted

what do yall think are the most impactful things we could do in the Bluesky app to support atproto builders?

AT Protocol Developers reposted

Voice notes are rolling out in Germ. Testflight users can update now to 3.1 (5991) for end-to-end encrypted voice notes with private, on-device transcription. Talk your talk. We won't hear a thing. 🗣️

Jim is also the lead engineer on Jetstream v2, so if you've got questions about how what went into the new and improved Jetstream, don't forget to ask.

Today we’re launching Bluesky Protocol Services, a new brand and website for the infrastructure Bluesky operates. And Jetstream v2, the best way for developers to use atproto at scale, now with network replay. atproto.com/blog/introdu...

atproto.comIntroducing Bluesky Protocol ServicesA new home for the infrastructure Bluesky runs on the open network — including Jetstream v2 with network replay, a new Jetstream SDK, and a lex-based TypeScript SDK