blocking ads is evil grr
HTTP is a pull-based medium. it is within the original philosophy of HTTP to selectively pull the data, for example, a device that doesn't support images won't download them. by circumventing ad "blocking", you are spitting in the face of HTTP. a more accurate term would be ad rejection. ads are not "blocked", they are simply not asked for.
@aral @lynnesbian push isn't forced; the protocol sends a push frame to say it wants to push and the client is ultimately in control of accepting or rejecting it. The binary format saves processing time (e.g. faster) on both ends, in both directions, and takes less bandwidth to transport and power, making it better for the environment.
@dshafik @aral @lynnesbian I think it's popular here to hate Google, justified or not.
A lot of the tech enables soooo many cool things but "nooo they just want to push ads on you". Ffs people, there's a guy running a free photoshop in a browser. Web and web getting capabilities is a _good_ thing for us all!
@zladuric I'm not a fan of Google, but HTTP/2 isn't google either. ¯\_(ツ)_/¯
@dshafik no it isn't. But they're the ones who push the most with a lot of these things, including http/2. Also, google might be easy to hate. But that's 85 thousand people! You can't hate them all, some of these people are amazing, a lot of them are awesome and most of them are just cool. (Not you, people in general).
As for HTTP/2, it's not a #Google thing, but Google is who gains a comparative competitive advantage by its introduction and implementation complexity.
We should always remember that each increment in complexity strengthen the position of the biggest players and often half-addresses the problem they created.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!