I like TreeBird's floss. They have silk and bamboo/charcoal kinds. They are very affordable, IMO. I buy their bamboo/charcoal refill pack for $18 and it lasts me a long time. I floss everyday and I use excessive yardage of floss, yet still it lasts a long time. Their containers are cool (glass and steel). Strongly recommend it.
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.)
> 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.
I had a similar issue at one point but if I remember correctly I just had to have my webserver send the header section without closing the connection.
Usually things would just get streamed through but for some reason until the full header was sent the proxy didn't forward and didn't acknowledge the connection.
Not saying that is your issue but definitely was mine.
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.
> SSE works seamlessly with existing HTTP infrastructure:
To stress how important it is to correct this error, even Mozilla's introductory page on server-sent events displays prominently with a big red text box that server-sent events are broken when not used over HTTP/2 due to browser's hard limit on open connections.
Yep, and in addition to that the ephemeral ports problem will araise at some scale with long-lived connections and infrastructure balancer/reverse proxy chain. So it's still required to tune.
https://treebirdeco.com/collections/floss