So, as usual i checking updates for my favorite novels in NU using GChrome. seeing that some of em got updated, i so eager to read em. but, behold. some of the sites unable to open, even if they could be opened, i need to do some process to bypass em. all of those sites got traced as [Not secure] on their link. when i googling at why those happening, i got to know that google or rather Google Chrome decided that all HTTP sites and pages as not secure. as i read futher down, they said that like other websites, any WordPress websites that contain password and credit card input fields will trigger the Not Secure warning on Chrome browser. i dunno if the translator already considered to moved to HTTPS based pages or either already actived the SSL on their web. i dunno to whom i need to pray and hoped for, but please let us leecher, NEET, Silent Reader, fans or/and anyone from NU-Community able to read our favorite novels wit ease mind... i just hope that this rule never exist if they only caused more problem for regular internet community. source: https://wpism.com/remove-not-secure...ve_Not_Secure_Warning_in_Chrome_for_WordPress
but many the translators who using wordpress're not. see if your favorite TL sites already upgraded or not, if not then you'd feel what i was talkin about...
Understandable. SSL certificate costs money. The cheapest would be around a hundred or so dollars per annum. Depending on the provider, it might cost more. So the question then, should the translators buy a certificate (which he/she has to renew every year) to appease the readers (who might not number more than a few hundred, and not all of them affected by the problem) or just save the money. Also, AFAIK free wordpress accounts can't do SSL. I don't know if one of their paid tiers provide SSL as a bonus, but then again, it feels like a waste to buy a certificate when you don't even have your own domain.
With a service like Let's Encrypt, which offers free wildcard encryption certificates, and WordPress plugins like WordPress HTTPS, there's no good excuse for anyone to run a standard version of WordPress that doesn't include encryption by default. If you're browsing a site that doesn't use https, all communications will be transmitted in clear text. That means anyone who can sniff your packets can see everything that you send to the website and what the website sends to you. If you're logging in or sending or receiving any type of information, anyone with access to that data will be able to see your login credentials or any other information that is transmitted. Any site that doesn't respect its users enough to switch to HTTPS deserves to be blocked. It irresponsible to not add encryption when it's free and (relativelty) easy to do so.