> There is zero reason for an ad to be using the Geolocation API. IP-based geolocation is more than enough.
There was also zero reason for billboards by highways, before there were highways. :)
Obviously this is all a sliding scale and has nuance, but I'd say ads should not be using anything that is behind a permission prompt, like geolocation. Tremendously hostile to both the user and the site hosting their ad.
More than likely they'll just correlate browsing habits with location and sell that information to third parties, though. High quality advertising is just not in this reality.
I mean, for all you know, I'm in a domestic abuse shelter. Are you going to take responsibility for my well-being if your clients' database gets leaked? And are you confident that your clients know how to competently secure a database if they can't even use HTTPS?
edit: Sorry, partial post due to accidentally hitting enter.
Geolocation API is pretty powerful. It's one thing for a random website to know approximate location, but to be able to track location within 10m is something else.
I'm weird, but it always grates slightly when companies throw their weight around - even if the endgame is a positive outcome.
Plus the cynic in me assumes they have an advertising product in the works and this is facilitating it.
While we do use geolocation and ads on one of our sites, it's only a single page so this doesn't really affect us that much. I can see it causing big problems with ad-supported sites / services that use geolocation as a primary feature though as I've experienced first-hand the revenue drop that HTTPS causes.
The reason for wanting the user's location doesn't matter. It's incredibly irresponsible to send the user's location (or any other user data) over the network unencrypted.
Edit: never mind, that is apparently also "insecure", leading me to think they are doing this because they get a kickback from the SSL cert vampires somehow.
In a way, it's good -- privacy on the web improved more in the last 3 years than in the previous 15 -- but it's also a massive charade.
Do they support just downloading a file from them and then uploading it my server, as proof that I control the domain? That should be enough.
You can use one of the alternate clients people have written, or write your own:
https://github.com/xenolf/lego
https://github.com/ericchiang/letsencrypt
Or use this web interface:
Also you can configure it to give you longer lasting certs.