SSL is becoming the standard for all browsers, not just Chrome, though Chrome is the one driving the standard.
Any site that a user inputs a password will be mandatory
to do over SSL
It's not that my codes won't work. It's the fact that ALL Jcink sites won't work soon unless they're viewed via HTTPS. That's why Jcink already made the changes. That's why all new Jcink boards are default enabled for HTTPS instead of HTTP.
Its not a matter of if
Shine does this. It's a matter of when
50% of users is massive. Professionally, something that affects just 10% of users is massive.
It's not about me though. It's not about my codes (my bad for using cutting edge browser features. But hey, you might get my browser notifications as a Jcink feature soon, so hey!). It's about functionality of the site -- everyone's site. I don't even run public Jcink board now. I have a premium account that I test things on... in all browsers, not just Chrome.
There's a reason John got free SSL certificates for all the sites. So you can use https://<site>.jcink.net as your URL instead of http://<site>.jcink.net (https://<site>.b1.jcink.com isn't available, he didn't get SSL certificates for b1.jcink.com)
But if you start using https now on your URLs, you'll see that some things are broken. It is my professional suggestion that you start using https NOW instead of LATER because once the first guest complains they can't login anymore because the site is being served over http, and the fix is to for the user to go to https instead http, and site's cbox and font's and images and anything external/embedded that isn't also served over https (the URLs in your wrappers and mini-profiles) doesn't show up. Just put a redirect script in your wrappers for now (which is the Official Jcink solution to this) to redirect http to https until he gets the "push button switch" in the admin panel working for everyone that is the server-side redirect. I'll write a script for it right now if you want (give me 30 minutes).
Like i said before, this was more of an FYI of things that are to come, as I am already experiencing it when I try to use the latest browser technology to make new features. This is just an attempt to get someone to look at the site on the HTTPS url, make note of what's broken over HTTPS (I already pointed out the cbox, and the fonts, but images were brought up on the Official Jcink forum because TinyPic urls don't work on https, but photobucket urls do), and be ready for when it starts, which will be within the year when Chrome rolls it out, which will take down 50% of your users, and then Firefox users, Safari users, Edge users...
I brought it to Shine's attention because since Shine is a Jcink Coding hub, and this is something that will affect all Jcink coders, not just Shine... something that will affect any kind of skinner, web developer, anyone who runs a site that requires a password (or personal information like credit card numbers, etc), then it'd help everyone future-proof their sites and have a resource to come to if they need help future-proofing their Jcink site.
But don't mind me. I just want everyone to change their site so that my codes work.
Edit: I'll just leave this here. Make note of the date.. https://forum.jcink.com/index.php?showtopic=27295