Neocities Goes HTTPS
As posted by Kyle Drake on The Neocities Blog on 2016-11-10, it was announced that "Starting [2017-01-01], Neocities will be defaulting to SSL on all sites", this meant that on New Year's Day 2017, all of the subdomains on Neocities (such as neozones.neocities.org) would no longer be HTTP, but would become HTTPS.
As noted in the announcement, one of the reasons chosen to switch to HTTPS was as a way to "protect your users, it's critical that we switch to default encryption and make it harder to violate your user's privacy", another reason cited was thanks to search engines that have since started to "penalizing unencrypted sites in search results, meaning that without default SSL, your site will be less likely to show up on search results".
As also noted in the blog post by Kyle Dreak, webpages that uses embedded content will be effected;
Basically, anything that embeds content (such as images and videos) from a third-party site using http instead of https. For example, if you have an embedded image with <img src="http://example.com/image.png> instead of <img src="https://example.com/image.png> (see the s in http?). The problem is that web browsers will block loading of http content because it is considered Mixed Content. If your browser is expecting an HTTPS connection, it refuses to load any unencrypted HTTP content because it "leaks" the encryption.
An example of a user reaction would be of JeremyRedhead, who in early January 2017, in an E-Mail posted on NeoMail, wrote a how-to guide for how people should deal with the possible issues that might effect them, writing a guide on how to handle it;
Example: <img src="http://example.com/example-image.jpg%22>
Step 2: Anything hosted on another site that supports https, just change the protocol to either https, or "relative", which loads based on the protocol the page is being used over. If it's another neocities site, this should be easy!
Example of https: <img src="https://anlucas.neocities.org/worldwideweb_badge.gif%22> Example of relative: <img src="//anlucas.neocities.org/worldwideweb_badge.gif">
If the site doesn't support https, you can do a couple different things:
If the resource is, for example, something that's intended to be shared, or in the public domain like a 88x31 button gif, you can probably safely download and re-host it on your site Example before: <img src="http://www.hat.net/abs/gif/noclick.gif%22> Example after: <img src="/noclick.gif">
Finally, if you have a link that opens in a frame that doesn't support https, just open it in a new tab! :)
Step 3: There is no no step three! Congratulations, you're done! :D See, that wasn't that hard.
Another user reaction was by Cass "Owly" Python, who makes note that her site only would become HTTPS five days after the roll-out
- Original wiki article about this subject
- How-To Geek: "HTTPS is much more secure than HTTP".
- Neocities Blog - IMPORTANT: We're switching to default SSL (HTTPS). Here's what you need to know
- From blog; text used is probably open-source as the main git uses an open license, but regardless, if not this text falls under fair use (also called fair dealing)
- Also from blog
- NeoMail -- Neocities defaulting to https
- Just look at that nice URL, HTTPS, nice