So now if someone who hosts&#x2F;rents a small server for side projects&#x2F;hosting small services like community forums or a simple game wants to make something experimenting with geolocation they&#x27;ll have to buy an HTTPS cert, make an app (which requires paying for the ability to put apps on major app stores unless you want to only support Android, where the OS discourages users from installing 3rd party apps with messages about how they might harm your phone, or jailbroken iPhones), or only support non-Chrome browsers (as long as other browsers don&#x27;t follow in this). Is it really a good thing to restrict web functionality even more from small players? How does it matter if someone sniffs your GPS location from an HTTP connection? Are there situations where that&#x27;s feasible and your precise geographic location isn&#x27;t something the attacker doesn&#x27;t already know? The only major situation I&#x27;m aware of is wifi hotspots where the location is already known.<p>Edit: Apparently there are free certificate suppliers, but will those be sustainable if HTTP is eventually fully phased out? Browsers display errors with self-signed certificates, so it still seems problematic in the long run to have to depend on the good graces of other parties if you want to serve web content.