Re: Update on geo-hint header

I would argue slightly differently. I see the primary value in this
proposal that sharing this information accurately is now up to the client.
If the client wishes to be accurate about its location, it can be, without
waiting for multiple third parties to converge. Whether a client does so is
a different question. At a minimum, an interested user could go do
something more about it than waiting for geo-ip-dbs and origins to update.

- jana

On Thu, Jul 7, 2022 at 8:46 AM Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:

> --------
> Tommy Pauly writes:
>
> > Essentially, if the client (or whoever is involved in choosing the IP
> for
> > proxying cases, etc) wants to have their effective geolocation reflect
> the IP
> > they chose, they have an incentive to share an accurate database entry.
>
> I think it far more likely that people will set it wrong, either
> willfully or through through geo-data-incompetence.
>
> There may be other arguments for the geo-hint header, but precision is
> probably not one.
>
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
>
>