3 ms·

It's 20 minutes only if you are exactly in the regular use case and already know what you are doing. And it's 20 minutes for one thing. Imagine if each little d

It's 20 minutes only if you are exactly in the regular use case and already know what you are doing. And it's 20 minutes for one thing. Imagine if each little detail of your setup would take 20 minutes. And of course down the road you will have to figure out subdomains, cross domain requests, media streaming, embedding external unsecure content, debugging on mobile devices, etc. And of course this will work only if you are on a private server, cause on the simplest hosting you won't have this. You lost touch with the quantity of knowledge you accumulated over the years.

pixl97 10y ago
> embedding external unsecure content, There is an easy answer to that. DON'T Most browsers block it at this point, and rightfully so. A single unencrypted include can be used to inject malicious content on a web page. Lots of people use internet over untrusted connections (open wireless) or partially trusted connections (ISPs injecting content). >You lost touch with the quantity of knowledge you accumulated over the years. Therefore we must lobby that our skill set is protected by law and that protocols and best practices are not allowed to change! Uh? Sorry man, you are going to have to evolve as the internet changes. Well, you don't have to, but when all your devices are encrypted and asking for a few bit coins to unlock, you will have been warned that it was going to happen.
- sametmax 10y ago
  > There is an easy answer to that. > DON'T Easy to say when your business is no tied to advertisers on which you have zero leverage. > Therefore we must lobby that our skill set is protected by law and that protocols and best practices are not allowed to change! Making TLS optional on HTTP2 would have not taken anything from you. You are just here in your ivory tower looking down on people that are clearly not as pure as your are. Well sorry, but down there, among the humans, you have PHP dev that are using EasyPHP, people that don't know the command line, people using mixed content and have no control over it, people that can't spend hours to continuously learn new things every week, people that don't have private servers and so on. And you know what ? I'm not even among them. I run my service on private servers with https. I use docker, letsencrypt and react or whatever is useful to me. But giving trainings and having friends running side business, I know that it's not the only reality in IT. So basically, right now, HTTP2 is just built to be hard for a huge part of the dev population, with no good reasons.
  - pixl97 10y ago
    >Easy to say when your business is no tied to advertisers on which you have zero leverage. Then it is time for your business to die. Sorry about your luck. >Making TLS optional on HTTP2 would have not taken anything from you. It would have reduced my security in the future when developers used it inappropriately. >Well sorry, but down there, among the humans, you have PHP dev that are using EasyPHP, people that don't know the command line, people using mixed content and have no control over it, people that can't spend hours to continuously learn new things every week, people that don't have private servers and so on. Then evolutionary forces far beyond them are going to push them to extinction. Adapt or die as they say. Your friends running side businesses need to realize they are on the public internet subject to grand forces far beyond their imagination. Malicious governments watching recording everything they can on people. ISPs injecting ads into customer data streams and selling browsing habits to third parties. Blackhats compromising machines to steal, or to spread trojans to client computers. Those things are real threats that the 'lowly humans' have to know about if they want to do business on the Internet and not be totally compromised. The fact that bad people exist just raises the cost of doing business.
  - NoGravitas 10y ago
    Pretty sure that when you are arguing against TLS, in order to help advertizers, you're one of the baddies. It's like having a skull on your hat.

pixl97 10y ago

> embedding external unsecure content, There is an easy answer to that. DON'T Most browsers block it at this point, and rightfully so. A single unencrypted include can be used to inject malicious content on a web page. Lots of people use internet over untrusted connections (open wireless) or partially trusted connections (ISPs injecting content). >You lost touch with the quantity of knowledge you accumulated over the years. Therefore we must lobby that our skill set is protected by law and that protocols and best practices are not allowed to change! Uh? Sorry man, you are going to have to evolve as the internet changes. Well, you don't have to, but when all your devices are encrypted and asking for a few bit coins to unlock, you will have been warned that it was going to happen.

sametmax 10y ago
> There is an easy answer to that. > DON'T Easy to say when your business is no tied to advertisers on which you have zero leverage. > Therefore we must lobby that our skill set is protected by law and that protocols and best practices are not allowed to change! Making TLS optional on HTTP2 would have not taken anything from you. You are just here in your ivory tower looking down on people that are clearly not as pure as your are. Well sorry, but down there, among the humans, you have PHP dev that are using EasyPHP, people that don't know the command line, people using mixed content and have no control over it, people that can't spend hours to continuously learn new things every week, people that don't have private servers and so on. And you know what ? I'm not even among them. I run my service on private servers with https. I use docker, letsencrypt and react or whatever is useful to me. But giving trainings and having friends running side business, I know that it's not the only reality in IT. So basically, right now, HTTP2 is just built to be hard for a huge part of the dev population, with no good reasons.
- pixl97 10y ago
  >Easy to say when your business is no tied to advertisers on which you have zero leverage. Then it is time for your business to die. Sorry about your luck. >Making TLS optional on HTTP2 would have not taken anything from you. It would have reduced my security in the future when developers used it inappropriately. >Well sorry, but down there, among the humans, you have PHP dev that are using EasyPHP, people that don't know the command line, people using mixed content and have no control over it, people that can't spend hours to continuously learn new things every week, people that don't have private servers and so on. Then evolutionary forces far beyond them are going to push them to extinction. Adapt or die as they say. Your friends running side businesses need to realize they are on the public internet subject to grand forces far beyond their imagination. Malicious governments watching recording everything they can on people. ISPs injecting ads into customer data streams and selling browsing habits to third parties. Blackhats compromising machines to steal, or to spread trojans to client computers. Those things are real threats that the 'lowly humans' have to know about if they want to do business on the Internet and not be totally compromised. The fact that bad people exist just raises the cost of doing business.
- NoGravitas 10y ago
  Pretty sure that when you are arguing against TLS, in order to help advertizers, you're one of the baddies. It's like having a skull on your hat.