3 ms·

OK I'm done with fighting fires for now and can answer that last question. Cloudflare offer "functions" and "workers", they're like functions that run on the ed

OK I'm done with fighting fires for now and can answer that last question. Cloudflare offer "functions" and "workers", they're like functions that run on the edge CDN nodes. These functions receive geolocation information via a function argument. So I've a function that intercepts requests to the app, grabs the geolocation information, and rewrites the URL (inserting the coordinates e.g. /lat,lng). I go into more detail about this in the blog post but originally it just opened in Cork for everyone. I disliked the idea of having an annoying browser prompt for location permissions. I made it for my dad so having no geolocation was fine to begin with and I eventually added the geolocation I described above. Less friction, no extra client-side requests.

whoopdedo 5y ago
Those "annoying prompts" are there for a reason. How do you justify ignoring the users' wishes with regards to accessing personally identifiable information? Also, why WebGL?
- adamlynch 5y ago
  >Those "annoying prompts" are there for a reason Yep, but not worth ruining the UX for marginally better geolocation in my case. > How do you justify ignoring the users' wishes with regards to accessing personally identifiable information? I don't know what you're referring to. If you're suggesting I'd prefer that apps & sites could access our location without asking, you're mistaken. >Also, why WebGL? The no-streets OSM raster map tiles were discontinued and I had to switch to custom Maptiler layers. They don't allow raster map tiles on the free plan.