Hostname-based Privacy Tools Need to Evolve For Websocket Concerns
But what if the ads and tracking were to flow through the same hostname of the original website? What if the ads and tracking were woven though the same websocket connection that the main site ran through? How would we be able to block that?
Persistent websocket connections are the backbone for anything on the modern web that is collaborative or realtime. Phoenix LiveView is a library I personally enjoy using to build websocket-powered apps. A similar library called Turbo is also out there for Rails.
I don’t have much to else to add. I have no answers, just concerns. Is anyone else working on this right now?