One of my biggest pet peeves is clutter. I could very well have OCD (though not formally diagnosed). I often find myself spending an insane amount of time organizing things or optimizing thing (ie, page load of this site), which could have very well been spent on things more important, like actually writing articles.
LPN (Application-Layer Protocol Negotiation) is a TLS extension that allows an efficient way to negotiate encrypted traffic between the browser and the server. In order to enable ALPN on a server, a web server needs to have HTTPS configured and support the HTTP/2 protocol. ALPN doesn’t provide any additional security benefit over HTTPS, it allows a browser to take advantage of speed benefit of HTTP/2 by lowering the initial handshake latency.
If you are running a Web App and you are storing user passwords, it is very easy to get things horribly wrong, it’s better to use third-party sign-in services like Facebook, Twitter or Google. In my experience, I have seen a lot of Web-Apps and Services going this route, not because they are lazy – but because they are offloading an aspect of your app that is incredibly difficult to get it right and secure.
Recently I have been spending an unholy amount of time learning a new programming language and improve my existing knowledge with lots of practice. My eventual goal is to reach a stage with a single programming language where I won’t have to refer to the documentation as frequently as I currently do.
I have been recently on a binge mode in converting all my sites to https. Including this one. It was long overdue. Thanks to the guys at “Let’s Encrypt” and their automated script called certbot, the whole process is insanely easy to set up. It literally took me less than 3 minutes each on all the sites I have enabled HTTPS for. I highly recommend that you also do the same.