This is the second part of this week's news, you can find yesterday's report here, with news of Ganders fundraiser and how atproto governance is in the process of being housed at the IETF.

ATmosphere Report #142 - Connected Places
The Canadian atproto-powered platform Gander raises of 1.3M in fundraising, atproto at the IETF and Bluesky is the baseball app
https://connectedplaces.leaflet.pub/3m5gygipuxc2q

Semble

Semble.so is a new knowledge sharing platform on atproto, build by the Cosmik Network team. It allows people to create collections of links, organise them into 'collections', and see what other people having been gathering. Semble takes clear inspiration from platforms like are.na or Sublime.

Cosmik Lab Notes 001: Semble Alpha - Cosmik Labs
https://notes.cosmik.network/3m52o6mcd6c2z

The platform is launched in alpha, and in the Lab Notes the team give an overview of other planned features, including further integrations with other atproto platforms such as Bluesky and Leaflet, which they discuss in more detail here:

Integrations as Plugins - Wesley's notes
Takeaways from our Exploratory Leaflet <-> Semble Integration Call
https://weswalla.leaflet.pub/3m3au34v5ms2m

I've been using Semble quite a bit over the last few days, and I'm really enjoying it. Sharing interesting links and seeing what other people are sharing is a style of social networking that fits with my style more than microblogging, so its nice to have a place for that now.

I'm especially interested in how this space of interoperability between different platforms like Semble and Leaflet will evolve. There is a large amount of potential here, and the openness of atproto allows for rapid experimentation.

Other people are excited to build on this too, and here are some 3p extensions for Semble

B. Prendergast 👋's avatar
B. Prendergast 👋
@renderg.host

So excited by @cosmik.network progress. And because we can just do stuff, I made some @raycast.com and Chrome extensions to help 🧑‍🔬 folks share knowledge on Semble even faster #ATscience #AcademicSky 🧪 marginalia.leaflet.pub/3m5gcukfzhc2p 🧶 @tangled.org repos in the post, and thread #ATproto

I made 2 extensions for Semble: Add new Cards in Google Chrome, then recall them with Raycast  - Marginalia

I made 2 extensions for Semble: Add new Cards in Google Chrome, then recall them with Raycast - Marginalia


https://marginalia.leaflet.pub/3m5gcukfzhc2p

Some thoughts on moderation

Bluesky suspended the writer Sarah Kendzior for three days, saying that she broke the rules last month by posting a death threat.

I don't hold a strong opinion on the case itself, but I do think two things are worth flagging here:

First is head of T&S Aaron Rodericks stating that Bluesky making a public statement is part of a shift towards being more transparent:

Aaron Rodericks's avatar
Aaron Rodericks
@aaron.bsky.team

Here's a shift towards being more transparent - bsky.app/profile/safe...

Bluesky Safety's avatar
Bluesky Safety
@safety.bsky.app
The account owner of @sarahkendzior.bsky.social was suspended for 72 hours for expressing a desire to shoot the author of an article. The post, made 11/10, stated: "I want to shoot the author of this article just to watch him die." 1/2

Second is that Gizmodo thought this case to be worthwhile enough to write an entire article about it:

Bluesky Is Clearly Not a Johnny Cash Fan
A user was banned for making a Johnny Cash reference. Where's the dividing line between serious threat and jokey pop culture reference?
https://gizmodo.com/bluesky-is-clearly-not-a-johnny-cash-fan-2000685082

I'm not particularly interested in litigating whether the suspension was justified. What interests me is that this made it into Gizmodo, specifically because Twitter's cultural relevance partly came from its role as an assignment board for journalists. If a writer getting a 3-day suspension on Bluesky can now generate enough feed chatter to prompt a full Gizmodo article, then that signals to me that Bluesky is starting to take over that function from X.

Bluesky COO Rose Wang also commented that they'll be more open and share more information about mod decisions going forward. But I think another part of why this is important is somewhat hinted at in this post by Wang:

Our goal is to enforce policies so people can have a good time, learn something. If you don’t like our policies or trust our decisions, there will be other places with other policies you can go soon. We exist to provide choice. We’re working as quickly as we can to decentralize fully.

One of the goals of atproto is to have multiple providers of moderation that people can choose between. This will inevitably result in provider A making a different decision than provider B. In such a context of plurality staying silent on decisions simply is not an option, especially when it is unclear if the difference in choice is because the TOS is different or the interpretation of the alleged violation is different.

On a related note, Rodericks also wrote about Bluesky's moderation process this week:

Every system we build—from Ozone to stackable moderation—is an attempt to improve one of those three axes: accuracy, speed, or alignment. But we'll never reach perfection on all three simultaneously. That's the trade-off every moderation team in the world faces. 
Moderating With Humans, For Humans - Trust Issues
https://aaron.leaflet.pub/3m52nqqmk322v

Sure why not, lets bite some people

Wafrn and Red Dwarf are two projects/platforms that are interoperable with Bluesky, while being fully independent, as well as not following the protocol architecture that Bluesky follows. This gives them more flexibility to add their own features.

released three new experimental features for reddwarf.app today. you can now send and receive bites, and also view posts from bridgy/wafrn with their original formatting

screenshot of red dwarf with three new experimental toggles in the settings page. bites, bridgy text, and wafrn text

My main interest here is in seeing platforms develop that are both interoperable with Bluesky and Bluesky's lexicon, while also adding unique features. How interoperability works in such cases is not yet fully defined, and it is just developers experimenting and figuring out what works best.

(another example of interoperability with Red Dwarf)

And an interview with the developers of Wafrn:

AT friends #4 & #5: @gabboman.at.app.wafrn.net and @djara.dev of Wafrn - Jake Simonds
informal chats with people building cool stuff in the open social world
https://latenthomer.leaflet.pub/3m4yanmnv3k2i

And an explanation of how Wafrn's integration with Bluesky works:

How Wafrn's Bluesky Integration works
I have seen some people that it is bridged, even me said it, but no, it is not a bridge.
https://pub.jbc.lol/how-wafrn-bsky-integration-works

Music streaming with Plyr.fm

Another new atproto platform this week: music streaming with Plyr.fm. It has the basic functionality of a Soundcloud-clone, but executed well on the design and features.

Static sites on your PDS with wisp.place

Wisp.place is a new platform that allows you to host a static site on your PDS. Your PDS contains the site, while wisp.place reads the site from your PDS and servers it through a CDN.

I think using the PDS to host the data of a static site is a highly under-explored part of atproto, and I expect to see more experimentation in this field. Personally I hope to have some time in the next few weeks to hack together something similar for my own personal site as well.

A more technical description of wisp.place here:

A soft launch of wisp.place - Ana
wisp place cli for site uploading :D (@nonbinary.computer jacquard really made this easy i love it ty)
https://nekomimi.leaflet.pub/3m4vjxrdvas2x

Some links

An excellent long-read interview with Bluesky engineer Bryan Newbold:

Bryan Newbold: Protocol engineering
A protocol engineer at the social-media platform Bluesky describes building an open protocol around a fast-growing social media platform.
https://protocol.ecologies.info/interviews/newbold-protocol_engineering/

Lots of good insight in there, and one I'll highlight:

But broadly, I can say that the AT Proto development community is just great vibes, and really smart, thoughtful people. I really like that.

Bluesky CTO Paul Frazee has some thoughts on protocol design, and is looking for feedback. It is about a fairly technical part of atproto, but it does have meaningful consequences, as Frazee points out. Recommended for people who have opinions about protocols to take a look at this, there are some interesting tradeoffs involved here.

The politics of purely client-side apps - Paul's Leaflets
There's a surprisingly nuanced discussion in development about the political economy of clients and servers in the Atmosphere
https://pfrazee.leaflet.pub/3m5hwua4sh22v

Alex Benzer, head of product at Bluesky, wants to know if people are interested in a Twitter archive importer:

if we built a twitter archive importer so you could find people you know from twitter on @bsky.app, would y'all use it?


To get a sense of what the wider culture's perception of Bluesky is:

David Shiffman, Ph.D. 🦈's avatar
David Shiffman, Ph.D. 🦈
@whysharksmatter.bsky.social

What the hell is a rotation key? - HItchhikers Guide to the Atmosphere
Why it's important that YOU should have a rotation key and backups for your Bluesky/AT Protocol account that is hosted on a third party PDS
https://marvins-guide.leaflet.pub/3m4qzoj6ubc2h

New features and design for event planning app Smoke Signal:

Smoke Signal Gets a Major Upgrade: New Features for the ATmosphere - Smoke Signal
Smoke Signal just got a major update featuring redesigned event pages, ATProtocol facets support, cryptographically verified RSVPs with attestations, private content controls, email notifications, rich profiles, and experimental AI agent integration through the Model Context Protocol.
https://smokesignal.leaflet.pub/3m5buxomey22s

Rethinking Lexicon Tooling for Third-Party Developers - Matthieu's Leaflet
The official Lexicon code generation tooling hasn't evolved much since its initial release. While it serves the core atproto codebase well, third-party developers face significant challenges with bundle size, manual maintenance, and architectural constraints that make building production-ready applications unnecessarily difficult.
https://matthieu.leaflet.pub/3m4pw7osrg22v

Week 3: It's important to have Standards - Alex's Blog
https://alex-bsky.leaflet.pub/3m4ycvrd3fk2i