Be there or be square
24.02.2026 06:38
👍 13
🔁 6
💬 1
📌 0
Be there or be square
Be wary of Bluesky, only the strong survive posters madness.
It's my birthday this weekend, in case anyone wants to treat me: throne.com/spookalucca
enforced by both the record and stratos since enrollment is tracked which might be similar to the shared group space you're all considering?
enable communities to exist wherever they need to and then its on the "community operator" to moderate the content.
And that's effectively where a new scheme comes in and the details are being worked out but it's really about data annotation at this point and the boundaries are mutually
data can exist beyond the PDS as long as they control it.
Couple with the concept of boundaries that can define groups we can in theory have a single Stratos service spanning multiple PDS which then bring in the moderation challenge and why the intent (and design) is to
that anyone on ATproto can adopt and I know pds operators will be hesitant to adopt a PDS implementation that is just ref+private data and no gurantees of keeping pace with PBC.
So I've taken a page from @ngerakines.me and adopted the hydration with stub design which takes the angle of a users
Thank you for the insight/feedback! I did the full implementation in the PDS and had to decide against it as I effectively had to rewrite the transaction backend to support dual-collections and determined it's not something we could maintain well at our current capacity plus the intent is a solution
I estimate around half of the trans people I know IRL are unemployed or underemployed. Probably a solid quarter of the trans people I know do subsistence sex work.
We are in crisis, and we're being utterly failed by this country's media and political establishment. Why is this not the narrative?
Introducing Ecosystem Action Research: a pilot program to address shared challenges in the AT Protocol ecosystem with a cooperative approach to strategic innovation.
By the community, for the community.
Sign up to participate here:
But I do have one for northsky stuff because sometimes I gotta do official business at the business factory.
My @atprotocol.dev talk has been accepted! #AtmosphereConf is going to be so much fun, I owe so many people drinks for all they’ve done with @transrights.northsky.social
Just PBC devrel sneak previews and like five different announcements for private data implementations coming soon.
The secret’s out!
And keeping your secrets just got easier.
Drop into Germ DM for AT Protocol—now live in the App Store and launching straight from Bluesky.
It will be built for community adoption. Can handle different boundaries, just prioritizing specific types at the start.
Yeah that’s pretty close to how I’m developing stratos. I wrote up a post on it last month with the initial design but since then I’ve taken the source hydration approach of a public record referencing a private one only accessible by those in the permissible boundary.
A screenshot of Germ DM. It shows my ATProto card and then in the ATProto (Bluesky) Profile DM Button section it shows Allow DMs from people I follow, and the Show button on my profile toggle is set to true. Those are the two important settings.
Germ lets you hide your button and/or close your inbox🔒, but for those of you out here being social rn — make sure your settings look like this, so your friends can see your Germ DM button! (To get to this page, just tap your card on Germ.)
Join us for an informal AT Protocol meetup February 24, 2026 in Berlin! We'll share project updates, demos, and lessons learned building on ATProto.
Please RSVP: smokesignal.events/did:plc:oals...
Location:
Bitcrowd offices
Köpenickerstr 126
10179 Berlin
We’ve had this problem with a few users and unfortunately our hands are tied, only bsky support can help here :(
We've made our migrator service code repository public so other communities that would like an entry point to their PDS and backend-powered PDS migrations can fork and host their own!
And thank thank thank you @aendra.com for your work, commitment and time working on the frontend! So much love and support for all our members and volunteers as we work together ❤️
One day someone is going to run with my end to sieve explainer but today it’s Daniel explaining it even better without a sterm that sounds like I’m ranting in a bar.
Big huge shout out to @ripperoni.com who did a _significant_ amount of work on the backend, couldn't have done it without you!. We had a great team of volunteers working alongside refining, fixing, and improving the tool as we discovered edge cases and surprises on how migrations worked on #atproto.
Our migration tools are built with a dedicated backend handling the heavily lifting for a fast robust migration with an intuitive frontend. Giving users from the very start an easy way to migrate was critical for us to protect our community.
github.com/NorthskySoci...
github.com/NorthskySoci...
Just over 2 months ago invites were sent out to welcome users to Northsky who used our migration tool to migrate. Throughout hundreds of migrations we've been fixing bugs and improving UX for a smoother experience to the point that we're now ready to release the source as we always intended.
Discord added a whole FAQ to their announcement because of the backlash. That doesn't matter because they clearly state it'll be required if you access "age-restricted experiences" including servers _and_ channels.
I'm in this and I don't like it.
ATProto has inverted mindfulness. Forget letting things go, we need to build our whole identity around it and find new ways to judge others.
That makes four different groups all digging into private data models. #ATproto has got the juice.