I sent a sopuli link to my wife tonight and she sent this back to me.
There is no “www” in the sopuli URL.
That’s a subdomain. It also works, but it apparently doesn’t have a HTTPS cert.
Remove the “www” and the HTTPS encryption will work just fine.
Some time after going to sopuli.xyz on Firefox on my laptop and sharing the link to my wife the www was injected. I copied the address in Firefox’s address bar and pasted that into telegram. Which she then clicked that link on her phone.
That shouldn’t happen.
The “www” in a URL isn’t just random. It either isn’t part of a websites address, or it is. Whether it works, or redirects to something that works, is up to any given website.
Some don’t work at all if you add it when it’s not supposed to be there.
Just sat down at my laptop. When I type “sopuli.xyz” into firefox and hit enter it loads www.sopuli.xyz. It does not when I use Safari.
Apple is so annoying for not even letting you visit a site with an outdated certificate. (I’m assuming that’s what caused the warning)
I still want to see the page, it’s unlikely that someone is faking the data… A warning not to enter private data should be enough, right?
It’s not just Apple. Basically all modern browsers yell at you for trying this, and there is almost always an override.
