Difference between revisions of "User talk:Eupeodes"

From Geohashing
(Historical data)
(mastodon feed: new section)
 
(3 intermediate revisions by 3 users not shown)
Line 30: Line 30:
 
Hi, and many thanks for your co-ordinates tool, which is great! I read somewhere a comment from you that seemed to imply you had a database of historical DJIA opening values data. This is something I've been trying to source because I'd like to do my own little project of finding patterns and detecting retrohashes. Is there data publicly available, by any chance? Thanks! --[[User:Macronencer|Macronencer]] ([[User talk:Macronencer|talk]]) 08:42, 3 March 2020 (UTC)
 
Hi, and many thanks for your co-ordinates tool, which is great! I read somewhere a comment from you that seemed to imply you had a database of historical DJIA opening values data. This is something I've been trying to source because I'd like to do my own little project of finding patterns and detecting retrohashes. Is there data publicly available, by any chance? Thanks! --[[User:Macronencer|Macronencer]] ([[User talk:Macronencer|talk]]) 08:42, 3 March 2020 (UTC)
 
:I'm not Eupeodes, but: https://data.geohashing.info/ --[[User:Fippe|Fippe]] ([[User talk:Fippe|talk]]) 09:13, 3 March 2020 (UTC)
 
:I'm not Eupeodes, but: https://data.geohashing.info/ --[[User:Fippe|Fippe]] ([[User talk:Fippe|talk]]) 09:13, 3 March 2020 (UTC)
 +
::Oh, that is AWESOME. Thanks, Fippe! :) --[[User:Macronencer|Macronencer]] ([[User talk:Macronencer|talk]])
 +
 +
== Wrong DJIA value for 2020-07-08 ==
 +
 +
I am not quite sure if I should report this here, but geohashing.info is using a wrong [https://data.geohashing.info/dow/2020/07/08 DJIA value of 0.00] to calculate the {{egl|2020-07-09|54|13|text=2020-07-09 hash}} pointing to a wrong location. The Geohash Droid App seems to make the same mistake and I don't know if it's because it uses the same source for the DJIA value as you do. It looks like the peeron map shows the right location for tomorrow's hash. --[[User:SastRe.O|SastRe.O]] ([[User talk:SastRe.O|talk]]) 16:55, 8 July 2020 (UTC)
 +
:It looks like the app is now displaying the correct coordinates, but geohashing.info still shows the wrong ones. --[[User:Fippe|Fippe]] ([[User talk:Fippe|talk]]) 07:48, 9 July 2020 (UTC)
 +
 +
== mastodon feed ==
 +
 +
Thanks for federating the expedition feed! It seems to have trouble with some Unicode, though: https://mapstodon.space/@geohashing/109733928191110162 should be [[user:π π π]], not [[user:? ? ?]]. [[User:Arlo|Arlo]] ([[User talk:Arlo|talk]]) 17:41, 22 January 2023 (UTC)

Latest revision as of 17:41, 22 January 2023

Geohashing.info

Hey your new coordinate calculator is awesome... especially for weekends when there's a ton of options, globalhashes, etc. and you just want to quickly find out what the situation is! Great design! -- OtherJack (talk) 13:38, 22 April 2014 (EDT)

Thanks, I indeed developed it mainly for the weekends. And I keep on developing based on user comments.--Eupeodes (talk) 13:44, 22 April 2014 (EDT)

Hi, it looks like geohashing.info run ahead of itself - now it shows coordinates for any date in the future. It is confusing a bit... -- Malgond (talk) 14:07, 2 November 2017 (UTC)

Hmm, today it looks fine... - Malgond (talk) 13:23, 6 November 2017 (UTC)
There indeed has been an issue on 2 November, I made an error migrating one of the tables from my old server to the new resulting in the bot thinking every day until the end of 2018 is a holiday. I have fixed the script and removed the faulty data from the database already on 2 November. I haven't seen the message here, but got a notification today. --Eupeodes (talk) 14:28, 6 November 2017 (UTC)

WIKI problems with coordinates

Hello again - the IRC chat topic now says "peeron and the wiki work reliably again! | http://geohashing.org | http://geohashing.info http://bit.ly/smanthill http://bit.ly/ghposter | Sat(W) 0.3495836, 0.2750481 | Sat(E) 0.2863239, 0.8238417 | Sun 0.9223329, 0.2975105 | Mon(E) 0.7381283, 0.6532" Is this for real? Is it cool to remove the red caution box from the wiki now, or are you waiting to make sure? -- OtherJack (talk) 16:45, 7 March 2015 (EST)

I was away, but I see it is removed now. Which is of course great since everything worked again. Although I am not sure if everything is still working now.--Eupeodes (talk) 10:54, 9 March 2015 (EDT)

Hallo Eupeodes,
maybe the following information could be helpful:
The 2015-03-10 coordinates seem to be ok on my Android smartphone with Geohash Droid in graticule 49/8:
49° 40.758' N 8° 42.835' E.
Best greetings --Q-Owl (talk) 02:59, 11 March 2015 (EDT)

Hi Q-Owl, The main problem seems to be that one of the few DOW sources that is used widely is having problems, I guess Geohash Droid is using one of the other sources since those coordinates look right to me. If I would have time I would look into fixing the DOW source the wiki uses or tell the wiki to use a different source. But at the moment I don't have time to do such things--Eupeodes (talk) 03:10, 11 March 2015 (EDT)

Geohashing statbar

Eupeodes, Is it possible to use your nice statbar as a template on a user page? I can generate a static .png file and display it as an image, but it would be really nice to put something on the user page that displayed the current stats rather than a fixed (and probably out-of-date) image. Thanks! Mcbaneg (talk) 04:06, 14 January 2019 (UTC)

An admin of the wiki will have to whitelist geohashing.info to allow embedding stuf from my domain. When that is done there is probably no reason that prevents embedding. I will try to get the admins to whitelist geohashing.info, than I should be able to make a wiki template to include the statbar in a page. --Eupeodes (talk) 09:49, 14 January 2019 (UTC)
I'd enjoy that; thank you! Mcbaneg (talk) 13:21, 14 January 2019 (UTC)
Just a short update, I haven't been able to reach Joannac and based on reports on the xkcd wiki it is challenging to reach a admin. So for now I can not make it happen. I guess we have to wait until an admin shows up --Eupeodes (talk) 13:17, 2 February 2019 (UTC)
Thanks for the update, and for your efforts. Maybe someday! Mcbaneg (talk) 15:37, 2 February 2019 (UTC)

Coordinate Precision

I noticed that since 2019-07-04, data.geohashing.info returns coordinate values with 5 decimal places, instead of the previous 16. Did you follow the advice of xkcd #2170 or is it a coincidence? --Fippe (talk) 17:37, 10 July 2019 (UTC)

This is indeed based on xkcd #2170 --Eupeodes (talk) 18:00, 10 July 2019 (UTC)

Historical data

Hi, and many thanks for your co-ordinates tool, which is great! I read somewhere a comment from you that seemed to imply you had a database of historical DJIA opening values data. This is something I've been trying to source because I'd like to do my own little project of finding patterns and detecting retrohashes. Is there data publicly available, by any chance? Thanks! --Macronencer (talk) 08:42, 3 March 2020 (UTC)

I'm not Eupeodes, but: https://data.geohashing.info/ --Fippe (talk) 09:13, 3 March 2020 (UTC)
Oh, that is AWESOME. Thanks, Fippe! :) --Macronencer (talk)

Wrong DJIA value for 2020-07-08

I am not quite sure if I should report this here, but geohashing.info is using a wrong DJIA value of 0.00 to calculate the 2020-07-09 hash pointing to a wrong location. The Geohash Droid App seems to make the same mistake and I don't know if it's because it uses the same source for the DJIA value as you do. It looks like the peeron map shows the right location for tomorrow's hash. --SastRe.O (talk) 16:55, 8 July 2020 (UTC)

It looks like the app is now displaying the correct coordinates, but geohashing.info still shows the wrong ones. --Fippe (talk) 07:48, 9 July 2020 (UTC)

mastodon feed

Thanks for federating the expedition feed! It seems to have trouble with some Unicode, though: https://mapstodon.space/@geohashing/109733928191110162 should be user:π π π, not user:? ? ?. Arlo (talk) 17:41, 22 January 2023 (UTC)