3 ms·

I still don't understand the point of this project. I mean QUIC is here, waiting for us. Why throwing away 30 years of HTTP ideas . If images and cookies are

I still don't understand the point of this project. I mean QUIC is here, waiting for us. Why throwing away 30 years of HTTP ideas . If images and cookies are to be forbid that should be made from the web developper decision. Choosing Gemini is like accepting restriction by law. I feel like this is old behaviour, that confidence and responsability is the way forward. In a way Gemini could have been published by writer of European Union , North Korea or Soviet Union laws, I can't belive this is a US products, as it contains too much to liberty constrain ;)

tenebrisalietum 6y ago
> If images and cookies are to be forbid that should be made from the web developper decision. Unfortunately even today that's not 100% under your control. I don't have to accept cookies nor load images from your site with the proper settings or browser. You seem to be forgetting HTTP is a user-initiated protocol and while a lot of it is hidden behind Javascript and common browser features, ultimately it's the user agent that initiates everything. You as a web developer can only control the files on your webserver, put cookies in headers (which the user agent has to send back to you) and possibly take advantage of some other Javascript features like DOM storage (which I can turn off). I'm 100% on board with Gemini being a 'liberty constrain' for those who put information online - honestly it's not necessary for remote systems to be executing code on my system just to display text. Yes, you can't monetize it as easily. That's a feature, not a bug, for a user like me.