I grew up in a rural township 50 miles from a major city in the 1980s. We were never isolated and there were in fact a diverse set of peers my own age with interests and heritage all across the spectrum. Yes there were a few racists or religious zealots but 99% of the folks got along just fine.

My own lasting impression is that this is the “American experience” that is not dead nor impossible to recreate in 2026. We just all need to learn to be decent Americans again.

> I know other people like reading LLM output.

I haven’t met any of these people; I’m sure some may exist but does anyone actually “like” rather than “tolerate” LLM writing? Anybody have a link to a decent study or survey on this area?

> AWS designs and implements their foundational services holistically.

I’d say they implement their services circularly. The outage-inducing circular dependency between Dynamo and Route53 is not a “holistic” design.

SendGrid and their competitors are already the very definition of “sender pays” for email. “Sender pays” is how they make money. This isn’t a problem of monetary incentives.

The problem is that companies get their SendGrid credentials compromised via password re-use or phishing.

I mean the carrier pays the recipient , so Twilio and sendgrid bear some cost

They understood just fine. But because that cost passes through to the sendgrid customer, it wouldn't motivate sendgrid to stop enabling spam.

currently the costs are too low to affect policy. that's my point. and the recipients are making extremely high margins on ads, so they don't have much reason to push back, either.

For any reasonable email fee, sendgrid can continue passing it on to the customers and not care.

If you make the fee super high, then many email workflows completely break and sendgrid goes out of business.

I don't think there's a number where it does what you want and incentivizes sendgrid to be careful.

(And you might say to seek a middle ground, but I don't think there is one. My guess is that "too low for sendgrid to care much more about a couple percent of mail from hacked accounts" and "too high for sendgrid to still attract customers" probably overlap.)

spam volume is 10000x-1e6x higher rate, so even small fees would impact them much higher than legit senders.

These are the accounts of legit senders being coopted to send very targeted spam. I don't think you can distinguish it by volume, because the volume needed to make these schemes work is just a fraction of the basically-legitimate volume these services process.

The real bulk bulk spam is a different issue entirely.

It never was FIPS-approved and likely will never be. The wireguard protocol used by Tailscale uses ChaCha20 for encryption which is not FIPS approved.

Interesting. What is the FIPS version of wireguard?

There are some forks that are not compatible with regular wireguard, for example from wolfssl. Or just classic mTLS.

> What is the FIPS version of wireguard?

IPsec or TLS-based overlays which use AES encryption and NIST-approved ECC curves or (gasp) RSA for key exchange and authentication. They generally suck in comparison with wireguard, which is a clean-sheet modern cryptographic protocol.

We’re calling these organized criminals vendors now?

I can confirm terrible video quality on 1Gb/s Xfinity connection in Chicago area. The NFL streaming picture quality looks like RealPlayer on a 56kbps modem from 1998. The ball becomes invisible as soon as it is passed or kicked! Blocky and ghosting artifacts. Not a network issue, every other site/app working great, it’s simply Netflix falling over during a live event again.

For an opposite datapoint: I had no issues with either game that I noticed. Denver area.

You know you don’t have to give it permission to a whole zone right?

My DNS provider has per-record permissions, but you could delegate a subdomain even if your DNS provider lacks per-record permissions.

OCSP stapling adds two more signatures to the TLS handshake. Bad enough with RSA keys but post-quantum signatures are much larger. OCSP stapling was always a band-aid.

If the server must automatically reach out to retrieve a new OCSP response for stapling every 7 days, why not just get automatically a whole new certificate which is simpler and results in a lots less data on the wire for every TLS connection?