Hello #rustlang people, I would appreciate a hint if anyone is aware of a non-invasive, privacy respecting geolocation crate? I seem to be picking the wrong terms or it just is an impossible combination in the first place?

My first idea of using https://beacondb.net/ does not seem to pan out.

beaconDB

@danielsreichenbach by definition there is no privacy-respecting way of doing geolocation. What is the purpose? What do you need it for? That is the question I think.

@Katie_Luise While I agree that one should always ask the question why one needs personal information like geolocation. Privacy does require an answer to "why".

For context:

- routing for many CDN services is based on having some geo information, a country or a continent usually is sufficient
- a sole person does not have any leverage against a billion dollar company to change this

Anycast - Wikipedia

@Katie_Luise I know Anycast. Like I said, I can not change the service side. I have no means of introducing Anycast in the project.
@danielsreichenbach logging IP and doing the rest then is only solution. In principle IP logging is already privacy invasion so there's no way to achieve this goal without some privacy invasion. Just put into terms and conditions.

@Katie_Luise I know, it is already in the terms of service, and has millions of users. I am literally just trying to replace a horrible vendor of geolocation information with a community driven one here.

I did ask for practical help, not for a lesson or philosophy. My original request already made it clear I am trying to strike a balance here...

@danielsreichenbach there is no perfect solution. Type the following into Gemini Pro or Claude Opus:

I have an online service. What is the best way to determine routes to the client without privacy invasion?

(RFC 8805 seems to be the best)