@Yehuda > Is the #Bluesky PDS open source?

Yeah: https://github.com/bluesky-social/pds

> Presumably you could modify it or build your PDS code to be more in control of what it does with the Relay?

Technically… yes?… But that would be kinda going against the protocol design imho.

@thenexusofprivacy @hailey @Sarahp

The point here is that it is not clear what has happened. Like so much from #Bluesky we get snippets of information and are then left to fill in a coherent story by reading the tea leaves. It would be very easy to spell out what happened, but it is not forthcoming.

1/

@mike @wfryer

That's really interesting. I'd never even heard of #Blacksky. I will definitely look that up.

Though to be honest I haven't spent as much time on Bluesky as I intended.

I know that's an odd thing to say here, but i intended to give #Bluesky a fair shot. I haven't really found the time to do that.

I'm getting a little bored of #social #networking if the truth be told.

I'm not sure why I've spent so much time here really. I think it's mostly the culture.

Bluesky, from the times I've been there, seems like a place where you're meant to follow people, rather than actually talk to them.

I've seen numerous times where people will ask others why they're replying when they don't follow them.

That seems more like grandstanding than networking to me. It also seems a bit rude, like they can't be bothered to actually interact with people.

I'm not sure why this place is so open to discussion. Sometimes it just comes down to #serendipity I guess.

An interesting followon to the Bluesky verification discussion I haven't seen discussion of over here: @aviva.gay introduced the ability for users to appoint their own "Trusted Verifiers" to their bluesky alt client, deer.social

OK, relatively few people adopt alternate clients, so this doesn't immediately help everybody (just like phanpy's UI doesn't help the vast majority of people who run the official Mastodon apps and don't even know about the alterantives). Still, it's a signficiant development, and there's a lot to learn.

Speaking of a lot to learn, here's a very good thread about Trusted Networks and how it relates to "verification" -- so I wanted to add it here as well. https://bsky.app/profile/rhalin.bsky.social

#Bluesky CTO continued:

A user asks about the source of the DDoS attack, and Frazee responds that they think it was an "accident by a 3p".

So, presumably not malicious.

"3p" apparently means third party.

So, it seems like #Bluesky is saying a third party, whatever that is, accidently did something that DDoSed all Bluesky PDSs and caused them all to fail simultaneously.

This is still confusing, and it would be good to get more details.

3/3

#Bluesky CTO continued:

Frazee: "ActivityPub doesn't scale correctly for the social media usecase anyway so this is a pretty pointless debate."

To which ActivityPub developer Christine Lemmer-Webber (here @cwebber) replies "hm"

2/

For anyone interested in the specific communications from #Bluesky CTO Paul Frazee on this (https://bsky.app/profile/pfrazee.com/post/3lnnfwf3tns22).

7:15am: All of our PDSes got DDOSed. Any PDS that wasn't stayed online. If the same happened to AP, they would've had the same outage

1/

Two more tech media articles that provide a little more information and also report the outage related to something affecting all #Bluesky PDSs, but no real specifics.

https://winbuzzer.com/2025/04/26/blueskys-decentralized-network-faces-major-outage-caused-by-centralized-servers-xcxwbn/

https://www.perplexity.ai/page/bluesky-suffers-outage-despite-b5tuvcMDT.6SI7QyiCS5EA