Well done Eddie for getting a TLS certificate.
This means that passwords are now sent encrypted.
I noticed that, in a few cases, the favicon is still sent using http: instead of https:. From now on I'll note where this occurs if it would be helpful to do so. (I am not sure that this actually matters)
(As an aside, has anyone else noticed the Quantcast GDPR preferences screen?)
No idea what all that means, but you've been missing for a while so welcome back.
R
Thank you. :-)Quote:
Originally Posted by ralphy
Anyone translate that please. :angel12:
Which bit? ;-)Quote:
Originally Posted by luddite
u wot m8
Green padlock. Good thing, innit.
Hi Mark, good to hear from you.
Encrypted passwords and GDPR compliance help keep everyone’s data safe, so good to see.
Thanks. :-)Quote:
Originally Posted by alfat33
I must have had a couple too many... I didn’t get any of that :la:
There needs to be a sub-forum along the lines of “Site Feedback” so this type of webhostingtalk doesn’t bore normal people in Watch Talk...
PS: For the record, I’m neither normal nor bored.
Haven't had a TZ favicon for ages.Quote:
Originally Posted by markrlondon
And this is on (watch talk) because? Anyway good to see TLS is working.
Works fine here.Quote:
Originally Posted by Kingstepper
Yup, we could do with one. It would be a meta subforum.Quote:
Originally Posted by FK77
Could call it "metatalk" or similar.
:thumbsup:Quote:
Originally Posted by markrlondon
Welcome back Mark:eagerness:
Now you fellers can trade watches without fear of your wives snooping on the traffic without extremely sophisticated eavesdropping attacks. I mean they all look like submariner right?
Coincidence that this guy is now back? I think not. Wives are getting technically better.
I was thinking the same thing.Quote:
Originally Posted by markrlondon
Sent from my iPhone using Tapatalk
Using Chrome/Windows, no favicons show in address bar as I thought they used to.Quote:
Originally Posted by markrlondon
Most sites show favicon on bookmarks/favourites bar but TZ doesn’t.
Thanks. :-)Quote:
Originally Posted by reggie747
HeheQuote:
Originally Posted by ollipekka
Weird. Chrome makes its own weird decisions about stuff like this.Quote:
Originally Posted by Kingstepper
Maybe it's because the favicon is served up via http, not https. Or perhaps it's just that the icon isn't up to Google's multifarious arbitrary standards.
I should add that I'm using Waterfox.
All of it. :la:Quote:
Originally Posted by markrlondon