Atmospheric Weather Report #2

This weeks report could have not been possible without curation efforts from @byarielm.fyi, @ronentk.me, @youronly.one, @wesleyfinck.org, and @captaincalliope.blue. Get involved next week by contributing to the the open semble collection.

Check out last weeks report here.

Cloud Formations

• @jay.bsky.team shared that she is stepping down as CEO and into a new role as Bluesky’s Chief Innovation Officer. @toni.bsky.team, a venture capitalist and Bluesky board member, is set to serve as interim CEO, while they look for a new CEO. Toni later shared impressions from the first week.
• @l4.pm announced atvouch.dev, a place to vouch for others skills.
• @blackskyweb.xyz open sourced the code for their app view, @rude1.blacksky.team shared their monthly operating costs, and there 3 proposals for Blacksky-only posts based on community feedback.
• @thisismissem.social received a $40k grant from the Bluesky team to help champion the FedMC standard towards working with the decentralized web. Follow along at the leaflet publication. They shared that W3C is looking for implementations for DIDs v1.1.
• @tangled.org announced support for deploying static websites, webhooks, and more.
• PDS hosting service, @periwinkle.social, just launched. There was notable pushback across the community about this how they are positioning themselves.
• @leaflet.pub announced a paid plan called Leaflet Pro.
• @kandake.africa brought atprot to e-ink with an app for Kobo called sKeets.
• @dollspace.gay previewed an atproto SDK for Rust.
• @dame.is teased at://wormhole, an Apple shortcut to travel between atproto apps.
• An update for @sequoia.pub is out along with custom HTML elements that can be embedded into any webpage for displaying comments and subscribing to @standard.site publications.
• @semble.so teases connections between cards.
• @alice.mosphere.at introduces atproto-smoke, a smoke/e2e suite for testing PDS and perlsky.
• @aetheros.computer, a desktop for atproto is set to release an alpha tomorrow.

Flocks

• ATmosphereConf 2026 just passed 300 in-person attendees. Also more sponsors were announced, check them out here.
  1. @permadeath.com is gauging interest in hosting a meetup during ATmosphere in Boston or NYC.
  2. @tessa.germnetwork.com is hosting a pregame on March 17th.
• The lineup of for the first @atproto.la meetup on March 23 was announced.
• @endowment.dev joined Bluesky looking to fund their first round of critical open source projects.
• @atproto.science had their first chat for shared lexicons and is looking for other voices interested in shaping them.
• Save the date, @newpublic.org is partnering with @publicspaces.net on an event in the beginning of June.

Whispers in the Winds

• @knowtheory.net opened up conversation about the state of the atmosphere.
• Discourse around permissioned data continues across the community.
  1. @dholms.at published part 3 of his series on permissioned data, called buckets. He also questions if buckets are the right naming.
  2. @offline.arushibandi.com and @eagraf.dev from @habitat.network shared a series exploring permissioned data (I, II).
• PDS migration was in the air this week.
  1. @rude1.blacksky.team mentioned Blacksky might follow in @eurosky.social's footsteps of a server-based migration.
  2. @baileytownsend.dev posted about some updates to PDSMoover and some struggles around server-side migrations.
  3. A bug was reported to @tranquil.farm that stems from undocumented proxying behavior in Bluesky’s reference PDS, discussion ensued.
• @sweetbee.vip shares some thoughts about the bridging the the dev community and atmosphere userbase.
• @baileytownsend.dev shares some stats about top collections for non-bluesky PDSs.
• @pckt.blog edited a video of highlighting the universal identity across the atmosphere.
• @blaine.bsky.social wrote an article on how atproto and llms could empower communities.
• @rude1.blacksky.team thinks about creating did:onion accounts.
• @tynanpurdy.com raised an interesting conversation about the third party doctrine and PDS hosts and what that means for ownership of user data.
• @ricardo.bsky.social shared some thoughts about raising funding for atproto.
• @laurenshof.online wrote about community build on social protocols.
• @timburks.me write about the risks of did:plc.
• There was some discourse around cross-app authentication.
• @ngerakines.me is looking for suggestions on event-stream circuit breakers.

That's all this week,

Chris