> I think the American First Amendment would obliterate this government body and probably the whole institution if it was ever tried.
This is not a government body, Ofcom is the relevant government body, like the US has the FCC, which you are aware of. The FCC has broadcasting rules. Your supreme court upheld their ability to issue sanctions for violations. This has lead to broad self-censorship by US broadcasters in much the same way the UK has Clearcast, to the point that censorship of stuff like swearwords is a recognizable trait of quite a few TV shows exported from the US. In the past year there have been multiple cases of censorship in response to threats from the FCC and other government bodies, much worse situations than banning an ad. The first amendment has done nothing to stop this.
I'm not here to defend the UK, they have some extremely scary laws on the books, but the US is really not notably different on this front.
I'd go so far as to say any implementation that doesn't conform to RFC 4180[1] is broken and should be fixed. The vast majority of implementations get this right, it's just that some that don't are so high profile it causes people to throw up their hands and give up.
It helps a bit that it's written in Zig, but its primary differentiating feature in the sea of terminal emulators is that it's created by mitchellh, who is kind of a celebrity in some circles.
You can turn on a feature documented as allowing the terminal to be controlled by escape sequences, but then output of programs can control the terminal! Whoop-de-do.
BearSSL is really cool, but it claims beta quality with the latest release in 2018, doesn't support TLS 1.3, and hasn't seen meaningful development in years. It's averaging about 1 commit per year recently, and they're not big ones.
This documentation page[1] seems pretty clear. One primary at a time, any number of read replicas that automatically proxy writes to the primary, when compute scales to zero the data is in object storage and a new primary can spin up elsewhere.
According to their ToS all customer accounts registered on or after September 3, 2024 are signed on to a US company, so no they're not doing what's necessary to keep US hands off the data.
After a different company detected it, figured out what it did, and reported it to Apple. The app was notarized on November 17, screenshots in the researchers' post are from December 16. That's a month of fully notarized distribution.
There is[1][2][3], the one for 2025 just isn't out yet.
[1]: https://thephp.foundation/blog/2025/03/31/transparency-and-i...
[2]: https://thephp.foundation/blog/2024/02/26/transparency-and-i...
[3]: https://thephp.foundation/blog/2022/11/22/transparency-and-i...
reply