Starting October 2017, Chrome (version 62) will show a ‘NOT SECURE’ warning when users enter text in a form on an HTTP page, and for all HTTP pages in Incognito mode.
The following URLs on your site include text input fields (such as < input type=”text” > or < input type=”email” >) that will trigger the new Chrome warning. Review these examples to see where these warnings will appear, so that you can take action to help protect users’ data. This list is not exhaustive.
Here’s how to fix this problem:
Migrate to HTTPS
To prevent the “Not Secure” notification from appearing when Chrome users visit your site, only collect user input data on pages served using HTTPS.
Well, I’ve now converted the whole domain to https. Hope this works.
(Ralf is wearing a hat from NEXT, £10, a leather jacket from The Original Dr Who jacket, £480, a wristwatch from eBay, £6. Konstantin is wearing a shirt from Stella McCartney, $365 and a ring from Lord of the Rings Originals PLC, £2892. All other gadgets (vaping things and beer) courtesy of Vogue magazine.)
The other day I found a mail from Google in my inbox. The people (?) at Google were complaining about a gazillion of broken links in my weblog entries and asked nicely if I were inclined to do something about this.
Of course, all those broken links didn’t come as a surprise since this weblog is now almost 16 years old and many websites I once linked to have simply disappeared or have changed their location on the web. Even internal links were buggered after I moved the blog from Radio Userland over to WordPress.
It scanned my whole site, and after three days came back with … a lot of broken links. I now had the options of editing and relinking the broken URLs, link to the Waybackmachine or to simply trash the old posts.
In many cases I just made use of the “Trash” button. There were so many one-liner posts, only consisting of a link to long forgotten websites that it made no sense relinking to archive.org, which would only confuse matters even further; also, archive.org can be rather slow at times.
In quite a few cases I was able to either edit the URL or relink the content.
But still – it’s a dilemma. Is trashing old posts good or bad? I’m still not sure, but I’ll carry on regardless – mind you, the plugin is still scanning and still throws up bad links once a week.
Anyway, the Google Bots should be happy now. As should be the readers – there’s nothing more annoying than clicking on a link which ends up
in a grey nowhere zone.
With all this social media stuff like twitter, instagram and whatnot going on I almost forgot about about my flickr stream. Still a wonderful way to present photos. And mine comes with images like this one, which I think isn’t too bad: