How to Fix IP GEO for google/youtube tv

Grant Taylor gtaylor at tnetconsulting.net
Thu Mar 11 19:57:56 UTC 2021


On 3/11/21 12:28 PM, Josh Luthman wrote:
> Based on how difficult it is to correct their data for them at no 
> charge, I'm not sure he's entirely wrong in that statement.

Difficult of doing something is not directly related to people's 
willingness / desire to do it.

I can guarantee you that there are Google employees who do want to have 
GeoIP (and other) information as correct as possible.  Said employees 
are grateful for such corrections.  Said employees try to process such 
corrections as expediently and efficiently as possible.

I can make this guarantee because I know / have witnessed multiple 
Google employees that have submitted and followed up on multiple GeoIP 
corrections.

I'm certain that there are still errors in Google's GeoIP data.  But I'm 
equally certain that multiple Google employees /do/ /wanna/ /improve/ 
/it/ (the GeoIP data).

> The fact that this thread exists, the latest of multiple, and has ended 
> in no resolution to the problem

How do you know that the OP's problem hasn't been resolved?

How do you know that the OP hasn't leveraged either of the suggestions 
that I provided?

Presuming the OP did leverage the suggestions that I provided, how can 
you say "no resolution" when it's been ~2 hours for a process that I 
indicated takes order of weeks?

> once again is a testament to how Google responds to this problem.

Based on your logic, the entire email industry must actually want spam 
because all efforts to the contrary have failed to stop it.

No, the email industry does not /want/ spam.
Yes Google has problems.
No, Google's problems do not accurately reflect the desires of the 
employees.



-- 
Grant. . . .
unix || die

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20210311/80977a64/attachment.bin>


More information about the NANOG mailing list