3 ms·

HTTPS is bad: - It wastes resources. - It adds complexity. - You can solve everything HTTPS solves over HTTP! - It encourages passive destructive behavior.

by bullen 7y ago

HTTPS is bad: - It wastes resources. - It adds complexity. - You can solve everything HTTPS solves over HTTP! - It encourages passive destructive behavior. - Troy Hunt probably has money coming in from certificates somehow. HTTP/2 and HTTP/3 are also bad. WebSockets are bad. As a side note: Vulkan is bad. HDMI is bad. Wakeup people. Time to get off that over-engineering couch and downvote the guy telling the truth again!

pmlnr 7y ago
So... you are both correct and not, which is probably why you're getting downvoted. Is much of the current tech overengineered? Yes, it definitely is. HTTPS on it's own - having TLS and a certificate - is not. It never was. But with stapling, CORS, X-XSS, and the rest, it becomes a beast. Those are becoming requirements, and they are making things _very_ complicated. I hear you, and I tend to agree on many things. Serial ports were gloriously simple whereas USB3 is a nightmare on every level. VGA was beautiful in it's simplicity, HDMI 1.4 with Ethernet included is certainly too much. mta-sts is probably the worst idea that could have been added to email, by relying on HTTPS requests. My personal take on this: use all of them responsibly. Use HTTPS, but don't make it exclusive, let the user make the choice: keep HTTP as well. Leave CORS, STS, Referrer Policy, etc out.
- bullen 7y ago
  You are the first person in the world who has a dialogue with me about this. Thank you! Here are a bunch of solutions I use instead of complexity: I hash with one time server generated salt for login: http://talk.binarytask.com http://talk.binarytask.com I use Comet-Stream for real-time communication over HTTP: http://fuse.rupy.se http://fuse.rupy.se And my latest finding is DPI for video: http://talk.binarytask.com/task?id=2433316338364993026 http://talk.binarytask.com/task?id=2433316338364993026

by bullen 7y ago

pmlnr 7y ago

So... you are both correct and not, which is probably why you're getting downvoted. Is much of the current tech overengineered? Yes, it definitely is. HTTPS on it's own - having TLS and a certificate - is not. It never was. But with stapling, CORS, X-XSS, and the rest, it becomes a beast. Those are becoming requirements, and they are making things _very_ complicated. I hear you, and I tend to agree on many things. Serial ports were gloriously simple whereas USB3 is a nightmare on every level. VGA was beautiful in it's simplicity, HDMI 1.4 with Ethernet included is certainly too much. mta-sts is probably the worst idea that could have been added to email, by relying on HTTPS requests. My personal take on this: use all of them responsibly. Use HTTPS, but don't make it exclusive, let the user make the choice: keep HTTP as well. Leave CORS, STS, Referrer Policy, etc out.

bullen 7y ago
You are the first person in the world who has a dialogue with me about this. Thank you! Here are a bunch of solutions I use instead of complexity: I hash with one time server generated salt for login: http://talk.binarytask.com http://talk.binarytask.com I use Comet-Stream for real-time communication over HTTP: http://fuse.rupy.se http://fuse.rupy.se And my latest finding is DPI for video: http://talk.binarytask.com/task?id=2433316338364993026 http://talk.binarytask.com/task?id=2433316338364993026