This weeks report is collectively curated and could have not been possible without curation efforts fromĀ , , , and . Check out the open collection to participate in future reports.

Check out last weeks reportĀ here.

Cloud Formations

  • The IEFT working group for atproto has been approved. This is a major milestone that shifts the protocol towards non-Bluesky governance.

  • received a $20k grant from Bluesky to build out Hubble, a full network mirror/archive.

  • and announced a partnership to build out the open social web.

  • Bluesky announced a $100 million Series B from a year ago. Lots of discussion arose from why they waited so long. , Bluesky's interim CEO, shared why his weekly recap.

  • released an auth-proxy.

  • spurred some projects by (here) and (here) to collect logos for atproto apps.

  • created a thread reader in the style of 5D chess time travel. They also made another tool to search through your previous interactions with someone else. also prototyped an alternative bluesky viewers in the theme of hackernews.

  • The atproto identity management service is now open to the public.

  • released ramjet, a new type of relay consumer.

  • Bots and spam:

    • released a new captcha system for PDS creation called PDS Gatekeeper.

    • Discussion ensued after a wave to spam bots came on to the network. wrote more about it.

    • The latest version of the Bluesky app added bot labels.

  • created some Astro loaders for syncing atproto collections.

  • released an early version of for pantry tracking, recipe management, and grocery planning.

  • New updates for , particularly the new profile tab for seeing long-form writing from other atproto apps.

  • open sourced a tools for accessing Bluesky records as markdown.

  • announced ATPhoto, to manage photos on atproto

  • teased an integration with .

  • released contrail, an atproto backend that runs on cloudflare. also previewed a backfilling/sync solution that runs on cloudflare.

  • released an alpha for Stargraph, to manage profiles across the atmosphere.

  • announced a blob proxy called Porxie.

  • has a place to propose feature requests.

  • shared a writeup of all of the changes they've been working on in the new year.

  • made a LinkedIn importer.

  • announced services for favicons, CDN, and Twitter mirroring.

  • made a proposal for PDS to PDS repo migrations.

  • released a FORTRAN bluesky client.

  • shared some explorations about using a PDS as a p2p sync relay.

  • shared an early version of p2pds, a local PDS archival/backup tool.

Flocks

  • is next week!

    • Submit launch announcements for the conf here.

    • shared some activities to do in Vancouver.

    • the full schedule can be found here and here.

  • The weekly atproto virtual hangout is this Sunday.

  • is looking for folks interested in presenting about atproto architecture at Ƙredev.

  • announced an alpha for atmosphere events.

Whispers in the Wind

  • wrote an essay about the purpose of protocols in response to 's essay Practical Decentralization. Paul responded by elaborated on why they decided to go with a VC funded corporation. also wrote a response.

  • published "The Decent Identity" part 1 and part 2.

  • continues their series on permissioned data, buckets have been renamed to spaces and shared higher-level overview.

  • continued their series on permissioned data.

  • started a conversation about UCAN and atproto.

  • wrote about breaking a habit of now building anything with atproto.

  • mentioned PDS as a user agent, related to 's idea of server user-agents.

  • shared some thoughts about atproto for normies.

  • A research paper about community Moderation and blocking on Bluesky.

  • was thinking about the association between atproto and DIDs and thinking about them in a cross-protocol/platform way.

  • wondered why the messaging around shared lexicons hasn't been resonating.

  • walks through about making custom feeds.

  • With the announcement that Instragram will be ending E2EE DMs, riffs of E2EE and atproto.

  • shared a mini-tutorial on migration did:web to a new pds. also announced the first successful did:web migration on PDS MOOver.

    • is thinking about "The AT Protocol Browser", which confirmed the bluesky team has mentioned they are not interested in.

    • prompted a discussion verifying the number of active accounts on atproto.

    • Posted about crossing $6k in monthly subscriptions.

  • drafted some thoughts on custom HTML elements for .

  • Submit your projects theme to .

  • started a discussion around AT URIs for app records.

  • suggests using CBOR for serialization with Activity Streams.

  • shares a post about 's integration with atproto.

  • wrote about did:cow.

  • writes about publishing with over Substack.

  • wrote about Mezzanine and permissioned data on atproto.

  • wrote about the power of community.

  • was thinking about why atproto "apps" might be a misleading name.

  • gathered some thoughts about private blobs.

  • wrote about building a PDS.

  • Discussion about cost to host a Mastodon server vs PDS arose.

  • asks how Blacksky can interact with Bluesky's off-protocol DMs and explains.

Thatā€™s all for this week,

Chris

(Note that next week there will not be a weather report because I will be traveling to Atmosphere conf. Follow the semble collection for the time being.)