Difference between revisions of "2011-05-01 38 -84"

Latest revision as of 06:21, 9 August 2019

Location

This hashpoint is right near the exit ramps of I-64 to Kentucky State Highway 859 (Haley Road). More specifically, it's on the westbound side of the highway.

Participants

Just myself, CaptainSpam.

Plans

One day last week, I got a Geohash Droid group posting from a user by the name of Jevanyn. Apparently, writes Jevanyn, there's an issue with the app where it seems to give Incorrect Password errors when posting. That's odd, I thought. It never did that for me. Therefore, I needed to investigate. Not just on my development test wiki, but on the REAL wiki, where there's a bunch of options and such I don't know about.

And, as luck would have it, that very Sunday (today), there was a hashpoint a mere 5.6mi from my home! Right on I-64, in fact! The perfect opportunity to figure out just what's going on without dumping garbage posts on the wiki! With nothing accompanying me except my car, my phone, and a head cold, I set out for a quick test run.

Since I knew this point was effectively ON the highway itself, and there was no place nearby I could stop (welcome to rural Kentucky, pal!), and the Kentucky State Highway Patrol are pretty vigilant about cars stopped on the side of the road (good if your car's broken down, bad if you need to explain why you're taking pictures of a seemingly random spot on the side of a highway in the middle of nowhere), I decided right away this would only be a drive-by picture-taking expedition. Good thing I happen to have another app I'm developing which automatically snaps pictures while driving so I don't have to!

Expedition

Time for another Hashing expedition through Central Kentucky! -- CaptainSpam @38.0198,-84.4189 14:20, 1 May 2011 (EDT)

Well, that IS disturbing. Got bad password errors out in the field. Hence the lack of updates. Though if this goes through, it works from home. Odd... -- CaptainSpam 15:00, 1 May 2011 (EDT)

The first of those two posts was made from the parking lot of a nearby Meijer gas station. Once I post the video, that's also the first frame and starting point of the pictures. That one was directly posted over a 3G connection, and it worked perfectly. Fair enough.

A short drive later, I passed by the point going eastbound and decided to pull off the road to make another post. A bit of aimless driving looking for someplace to park later (don't try this in rural Kentucky unless you're comfortable with disappointment), I tried making a post. Sure enough, that one failed with an Incorrect Password error. Very disturbing. I went back on the road to return home and made the second of the two posts above. That one worked. Most odd.

Jevanyn posted the theory that the wiki is now using a CAPTCHA service which may be disturbing the posting API. However, that doesn't explain why I'm explicitly getting bad password responses (that response is different from the "CAPTACHA needed" response), nor does it explain why the post DID work from 3G near a gas station but didn't work from what I believe is EDGE in the boonies. Unless there's IP blocking in effect and that area just happens to fall in the block range? Maybe? That doesn't make too much sense either, but I'm rather a bit lost.

I might need to talk with the wiki admins about this. I obviously can't just keep driving out to the middle of nowhere every time I need test logs.

Photos

(pictures coming soon)

Video

Via YouTube: A distance-lapse video of driving past the point, as close as I could get.

Achievements

Land Geohash

@@ Line 1: / Line 1: @@
-<!-- If you did not specify these parameters in the template, please substitute appropriate values for IMAGE, LAT, LON, and DATE (YYYY-MM-DD format)
-[[Image:{{{image|IMAGE}}}|thumb|left]]
-Remove this section if you don't want an image at the top (left) of your report.   You should remove the "Image:" or "File:"
-tag from your image file name, and replace the all upper-case word IMAGE in the above line.
-And DON'T FORGET to add your expedition and the best photo you took to the gallery on the Main Page! We'd love to read your report, but that means we first have to discover it!
--->
 {{meetup graticule
 | lat=38
@@ Line 14: / Line 6: @@
 }}
-<!-- edit as necessary -->
 __NOTOC__
 == Location ==
-<!-- where you've surveyed the hash to be -->
+This hashpoint is right near the exit ramps of I-64 to Kentucky State Highway 859 (Haley Road).  More specifically, it's on the westbound side of the highway.
 == Participants ==
-<!-- who attended -->
+Just myself, [[User:CaptainSpam|CaptainSpam]].
 == Plans ==
-<!-- what were the original plans -->
+One day last week, I got a Geohash Droid group posting from a user by the name of Jevanyn.  Apparently, writes Jevanyn, there's an issue with the app where it seems to give Incorrect Password errors when posting.  That's odd, I thought.  It never did that for me.  Therefore, I needed to investigate.  Not just on my development test wiki, but on the REAL wiki, where there's a bunch of options and such I don't know about.
+And, as luck would have it, that very Sunday (today), there was a hashpoint a mere 5.6mi from my home!  Right on I-64, in fact!  The perfect opportunity to figure out just what's going on without dumping garbage posts on the wiki!  With nothing accompanying me except my car, my phone, and a head cold, I set out for a quick test run.
+Since I knew this point was effectively ON the highway itself, and there was no place nearby I could stop (welcome to rural Kentucky, pal!), and the Kentucky State Highway Patrol are pretty vigilant about cars stopped on the side of the road (good if your car's broken down, bad if you need to explain why you're taking pictures of a seemingly random spot on the side of a highway in the middle of nowhere), I decided right away this would only be a drive-by picture-taking expedition.  Good thing I happen to have another app I'm developing which automatically snaps pictures while driving so I don't have to!
 == Expedition ==
-<!-- how it all turned out. your narrative goes here. -->
 *Time for another Hashing expedition through Central Kentucky!  -- [[User:CaptainSpam|CaptainSpam]] [http://www.openstreetmap.org/?lat=38.01979689&lon=-84.41887785&zoom=16&layers=B000FTF @38.0198,-84.4189] 14:20, 1 May 2011 (EDT)
 *Well, that IS disturbing.  Got bad password errors out in the field.  Hence the lack of updates.  Though if this goes through, it works from home.  Odd...  -- [[User:CaptainSpam|CaptainSpam]] 15:00, 1 May 2011 (EDT)
-== Tracklog ==
-<!-- if your GPS device keeps a log, you may post a link here -->
+The first of those two posts was made from the parking lot of a nearby Meijer gas station.  Once I post the video, that's also the first frame and starting point of the pictures.  That one was directly posted over a 3G connection, and it worked perfectly.  Fair enough.
+A short drive later, I passed by the point going eastbound and decided to pull off the road to make another post.  A bit of aimless driving looking for someplace to park later (don't try this in rural Kentucky unless you're comfortable with disappointment), I tried making a post.  Sure enough, that one failed with an Incorrect Password error.  Very disturbing.  I went back on the road to return home and made the second of the two posts above.  That one worked.  Most odd.
+Jevanyn posted the theory that the wiki is now using a CAPTCHA service which may be disturbing the posting API.  However, that doesn't explain why I'm explicitly getting bad password responses (that response is different from the "CAPTACHA needed" response), nor does it explain why the post DID work from 3G near a gas station but didn't work from what I believe is EDGE in the boonies.  Unless there's IP blocking in effect and that area just happens to fall in the block range?  Maybe?  That doesn't make too much sense either, but I'm rather a bit lost.
+I might need to talk with the wiki admins about this.  I obviously can't just keep driving out to the middle of nowhere every time I need test logs.
 == Photos ==
+(pictures coming soon)
 <!-- Insert pictures between the gallery tags using the following format:
 Image:2010-##-## ## ## Alpha.jpg | Witty Comment
@@ Line 41: / Line 43: @@
 <gallery perrow="5">
 </gallery>
+== Video ==
+* [http://www.youtube.com/watch?v=9yP4HDi08sc Via YouTube:] A distance-lapse video of driving past the point, as close as I could get.
 == Achievements ==
-{{#vardefine:ribbonwidth|800px}}
+* Land Geohash
-<!-- Add any achievement ribbons you earned below, or remove this section -->
-<!-- =============== USEFUL CATEGORIES FOLLOW ================
+[[Category:Expeditions]]
-Delete the next line ONLY if you have chosen the appropriate categories below. If you are unsure, don't worry. People will read your report and help you with the classification. -->
-[[Category:New report]]
-<!-- Potential categories. Please include all the ones appropriate to your expedition -->
-<!-- If this is a planning page:
-[[Category:Expedition planning]]
--->
-<!-- An actual expedition:
-[[Category:Expeditions]]
--- and one or more of --
 [[Category:Expeditions with photos]]
-[[Category:Expeditions with videos]]
-[[Category:Expedition without GPS]]
--->
-<!-- if you reached your coords:
 [[Category:Coordinates reached]]
--->
+[[Category:Expeditions with videos]]
+{{location|US|KY|FA}}
-<!-- or if you failed :(
-[[Category:Coordinates not reached]]
--- and a reason --
-[[Category:Not reached - Mother Nature]]     when there is a natural obstacle between you and the target
-[[Category:Not reached - No public access]]  when there is a man-made obstacle between you and the target
-[[Category:Not reached - Technology]]        when you failed get your GPS, car, bike or such to work
-[[Category:Not reached - Did not attempt]]   when you went to an alternate location, or decided early on to abort the expedition.
--->


Sun 1 May 2011 in 38,-84: 38.0469730, -84.3310002 geohashing.info google osm bing/os kml crox