3 ms·

Why neither this nor tool in OP work with manually entering location is beyond me. My browser doesn't know my location. It doesn't help that it doesn't work eve

by rplnt 4y ago

Why neither this nor tool in OP work with manually entering location is beyond me. My browser doesn't know my location. It doesn't help that it doesn't work even when I allow location in Firefox. But both would be solved if I could just select the location myself, as in any other application.

runeks 4y ago
> Why neither this nor tool in OP work with manually entering location is beyond me. The reason is that it would be extra work, and it’s not clear how many people actually want this feature.
- tengwar2 4y ago
  And it would be very easy to find out how many people start the page load, and don't complete. This will be close to the number of people who cannot or will not allow their browser to divulge that information.
- wohfab 4y ago
  But it's extremely little additional work, though. The application is already able to find articles around a given address. The only thing that would be changed, is that you enter the address by hand instead of letting the browser locate you. This can be easily done in a day
  - orf 4y ago
    Unless you’re entering your location as lat/long, it’s a lot more work.
- Mordisquitos 4y ago
  "Extra" work? Accepting manually entered locations is utterly trivial compared to using the browser's location feature.
tuukkah 4y ago
The tools use the browser location as it's easy to access in a few lines of code, and the users can select the location themselves in multiple ways: * In the browser console * In the browser settings * In a browser extension Meanwhile, addresses are hard in a global context. Implementing address search can be a lot of work because browsers don't provide one so you need either a (global) address database or an API endpoint to access one. Also, people expect a search which is both fuzzy and with autocompletion, which works best by prioritising results based on the browser location. Finally, you need to implement a user interface for the search field.

by rplnt 4y ago

runeks 4y ago

> Why neither this nor tool in OP work with manually entering location is beyond me. The reason is that it would be extra work, and it’s not clear how many people actually want this feature.

tengwar2 4y ago
And it would be very easy to find out how many people start the page load, and don't complete. This will be close to the number of people who cannot or will not allow their browser to divulge that information.
wohfab 4y ago
But it's extremely little additional work, though. The application is already able to find articles around a given address. The only thing that would be changed, is that you enter the address by hand instead of letting the browser locate you. This can be easily done in a day
- orf 4y ago
  Unless you’re entering your location as lat/long, it’s a lot more work.
Mordisquitos 4y ago
"Extra" work? Accepting manually entered locations is utterly trivial compared to using the browser's location feature.

tuukkah 4y ago

The tools use the browser location as it's easy to access in a few lines of code, and the users can select the location themselves in multiple ways: * In the browser console * In the browser settings * In a browser extension Meanwhile, addresses are hard in a global context. Implementing address search can be a lot of work because browsers don't provide one so you need either a (global) address database or an API endpoint to access one. Also, people expect a search which is both fuzzy and with autocompletion, which works best by prioritising results based on the browser location. Finally, you need to implement a user interface for the search field.