OT What went wrong with webpage submission

Speak of the Devil....
I just came across this article about Google
inserting local ads into search results, including
on desktop PCs.

http://searchengineland.com/google-e...results-243985

I wouldn't be surprised if Google has their own
geo-location database composed of personal records,
to supplement an IP-based database. Many of the
people visiting their search engine will have already
given their address to Google.

[Default] On Sat, 5 Mar 2016 09:05:06 -0500, in
microsoft.public.windowsxp.general "Mayayana"
wrote:



In any case, Cruz's or Rubio's website
should have no difficulty at all in checking whether a visitor
is coming from a particular US state -- if that's what they
were trying to do.

The campaign sites wouldn't care, but the senate.gov sites all seem to
insist on an address in the state. I assumed that part of the
service was provided by the Congressional webmaster. But so much of
the pages are individualized that each congressman must have his own
webmaster too. They're not going to want to wait in line behind, say,
200 others to make changes.

Well, I went back to the "Governor of Ohio" non-campaign Kasich site
and it worked tonight. Said the limit was 1200 characters and didn't
tell me how many I'd used, but a line was about 100 characters, so I
sent 12 lines.

[Default] On Fri, 04 Mar 2016 09:30:09 -0500, in
microsoft.public.windowsxp.general Micky
wrote:


I'm curious about this. Do they use my IP address to decide I don't
live in Florida? If not, is it because the web server, Verizon,
isn't used in Florida? That doesn't make sense.

You don't have permission to access "http://www.cruz.senate.gov/?" on
this server.
Reference #18.98f24317.1457099856.bac518

OTOH, I tried this one again and got the same message, except only the
first two characters of the ref# were the same.

In article , am says...
According to your IP ...



Geolocation based in IP address can be problematic.

When I have tried various sites advertising geolocation service using my
IPv4 address, they all got the city (Salem, Oregon, USA) correct, though
there was variation on where in the city I live, but at least all the
locations were within 5 miles of my physical location. But then this
should have been easy for them to locate my city: my ISP has been doing
service in this city for decades, and the IPv4 range they have used for
this city has been stable for at least a decade.

When it comes to looking up IPv6 addresses, the story is quite
disappointing. It is better than it used to be: the sites that in the
past reporting that I live in Beaverton (Comcast's local hub, about 40
miles north of here) now report the correct city. However, I am getting
several results in Mt. Laurel, New Jersey (Comcast's administrative
office on file with ARIN; about 2,900 miles east of my real location,
yes, on the opposite side of the continential United States of America,
but at least the country is correct), one reported that I am in North
Dakota (a Comcast hub; about 1,300 miles east), one said I was in Brazil
(only way I can figure that happened was by incorrectly parcing my IPv6
address), but the majority of web sites that allow me to enter an IP
address claimed my IPv6 address was not a valid IP address.

For some ISPs, even IPv4 addresses may become less and less reliable,
especially as more ISPs start using CGNAT or other public IPv4 sharing
devices, quite possibly with the CGNAT (or equivalent) device located in
another state.

On DSLReports.com one user was complaining that Facebook consistently
warned her that someone in another state was using her credentials every
time she connected to Facebook, which again is an example of the
uncertainty at least today for using IPv6 for gelocation.

With the IPv4 address pool for IANA and four of the five regional
Internet registries exhausted, some day several geolocation companies
will have to come to the realization that if they can't do reliable IPv6
geolocation their future will be ... limited.