deaf_coder

You mean like Bluesky, Threads, or Mastodon?

Those services are available, however, people would not stop using Twitter and will continue to do so until we stop consuming their content, then maybe they will finally get off Twitter...

It's so simple and straightforward, and that's why Douglas Crockford claims he "discovered" it, rather than invented it.

It might be a little sketchy for some, but you can patch the .iso to remove the TPM requirement and get Windows 11 to install on non-compliant computers. I forgot where to download the patch from, it was from some GitHub page I found on the internet. I have done it so on my ancient desktop with Intel i5-3750K without issues.

A warning though, water won't 100% wash away any scum. I recall reading an article somewhere saying that dentists still recommends conventional floss once in a while to remove any stubborn scum if you're using Waterpik. (That dentist doesn't say you should stop using Waterpik, though.)

going slightly off the tangent here, does FaaS cloud providers like AWS, CloudFlare, and etc support SSEs?

Last time I checked, they don't really support it.

In my case with this load balancer, I think it's just badly written. I think it is set to hold ALL data until the server ends the connection. I have tried leaving my SSE open to send over a few megabytes worth of data and the load balancer never forwarded it at all until I commanded the server to close the connection.

The dev who wrote that code probably didn't think too much about memory efficiency of proxying HTTP connections or case of streaming HTTP connections like SSE.

The part where it says:

> SSE works seamlessly with existing HTTP infrastructure:

I'd be careful with that assumption. I have tried using SSE through some 3rd party load balancer at my work and it doesn't work that well. Because SSE is long-lived and doesn't normally close immediately, this load balancer will keep collecting and collecting bytes from the server and not forward it until server closes the connection, effectively making SSEs useless. I had to use WebSockets instead to get around this limitation with the load balancer.