Adam Fisk

Also, using those techniques at the atproto level would allow folks to run instances inside censored countries, which does have benefits like adding resilience to full internet fragmentation/shutdowns where the rest of the internet is shut off.

There are *a lot* of people living with that reality.

Many also require proxies that understand those, but some are also proxyless for accessing domains directly (say bsky.app).

So it would have to be in Bluesky apps to withstand state-sponsored censorship, but honestly we could integrate it with minimal impact on your code base.

Almost all of the techniques require some client-side tech, such as TLS record fragmentation, TCP packet splitting, things like Geneva (geneva.cs.umd.edu), Shadowsocks, TLS variations, etc.

@bnewbold.net I posted this over in GitHub discussions, but I'm curious if y'all would ever consider (aka accept a PR) for added censorship resistance to Bluesky/AT via simple integration of circumvention protocols like TLS record fragmentation, TCP packet splitting, proxying necessary traffic, etc.