3 ms·

Everything past HTTP 1.1 has been a waste of time and energy. Everyone involved in making these protocols (HTTPS/WebSocket/HTTP2/HTTP3/etc.) are just victims o

by bullen 7y ago

Everything past HTTP 1.1 has been a waste of time and energy. Everyone involved in making these protocols (HTTPS/WebSocket/HTTP2/HTTP3/etc.) are just victims of: “It is difficult to get a man to understand something, when his salary depends upon his not understanding it!” - Upton Sinclair

AlEinstein 7y ago
Have fun in your HTTP 1.1 world.
gear54rus 7y ago
Bold claim. Let me guess: it's not gonna be backed up is it?
vardump 7y ago
HTTP 1.1 is somewhat broken. For example pipelining and keeping connection open, data integrity issues like no content length followed by unexpected connection loss, etc. It also allows ISP shenanigans like content modification to add unwanted advertising and unlimited tracking, even spying. So could you please explain your reasoning?
acdha 7y ago
Can you back that up? HTTPS is a requirement for doing anything securely. It seems like a lazy troll to just dismiss it with no explanation. Similarly, even a cursory amount of research into WebSockets or HTTP/2 will turn up real engineering problems which are solved by those protocols. Can you address any of them?
- bullen 7y ago
  I hash the password with a one-time server salt in the client (instead of HTTPS) and I use simple HTTP comet-stream for real-time data (instead of WebSockets): http://fuse.rupy.se http://fuse.rupy.se HTTP/2 has the TCP head of line problem which makes it completely useless. HTTP/3 is trying to be more nimble, but it's a protocol! Ossification is a _feature_ of protocols; for TCP it allows the backbone to evolve without everyone re-implementing everything over and over again at the edges! The solution is to make TCP like UDP instead, by allowing sockets to not resend missed packets. Another real solution is to remove the network kernel on linux.

3 ms·

Everything past HTTP 1.1 has been a waste of time and energy. Everyone involved in making these protocols (HTTPS/WebSocket/HTTP2/HTTP3/etc.) are just victims o

by bullen 7y ago

AlEinstein 7y ago
Have fun in your HTTP 1.1 world.
gear54rus 7y ago
Bold claim. Let me guess: it's not gonna be backed up is it?
vardump 7y ago
HTTP 1.1 is somewhat broken. For example pipelining and keeping connection open, data integrity issues like no content length followed by unexpected connection loss, etc. It also allows ISP shenanigans like content modification to add unwanted advertising and unlimited tracking, even spying. So could you please explain your reasoning?
acdha 7y ago
Can you back that up? HTTPS is a requirement for doing anything securely. It seems like a lazy troll to just dismiss it with no explanation. Similarly, even a cursory amount of research into WebSockets or HTTP/2 will turn up real engineering problems which are solved by those protocols. Can you address any of them?
- bullen 7y ago
  I hash the password with a one-time server salt in the client (instead of HTTPS) and I use simple HTTP comet-stream for real-time data (instead of WebSockets): http://fuse.rupy.se http://fuse.rupy.se HTTP/2 has the TCP head of line problem which makes it completely useless. HTTP/3 is trying to be more nimble, but it's a protocol! Ossification is a _feature_ of protocols; for TCP it allows the backbone to evolve without everyone re-implementing everything over and over again at the edges! The solution is to make TCP like UDP instead, by allowing sockets to not resend missed packets. Another real solution is to remove the network kernel on linux.