Posts mit dem Label English werden angezeigt. Alle Posts anzeigen
Posts mit dem Label English werden angezeigt. Alle Posts anzeigen

Samstag, 31. Januar 2015

Do German geocachers take the game too seriously?



Among the German geocachers, the current big topic being heavily discussed is the existence of a list which holds final coordinates for more than 12,000 caches, mostly Mysteries, but also of Multi-caches plus answers for Earthcaches. Mainly located in Germany.

But let’s start from the beginning:

On Jan 29th, there was a blog post released (links can be found at the end of this article), talking about a “secret” German Facebook group, where the only topic was exchanging solutions and final coordinates for caches. The name of the group is “Geocaching Mystery Spoiler – Koords bitte !”, which translates to “Geocaching Mystery Spoiler – the coords, please!”.

Shortly after it became public that, in addition to the Facebook group, a spread-sheet exists which holds the name, cache id, state / region plus final coordinates of approx. 12,000 caches. As mentioned above, not only Mysteries, but Multis and Earthcaches as well.

And sometime yesterday, Jan 30th, it was confirmed that the (pretty popular) geochecker webpage "geocheck.org" was intruded, which means that the solutions for more than 20,000 geocaches were stolen.

So let’s walk through these three points:

Basically, talking about final cords is probably as old as geocaching (or, to be more precise, the existence of Mystery caches). Everybody who ever visited a local geocaching event catched a talk about this or probably even initiated one. And there’s nothing wrong with that, especially as in most cases, there’s only a clear hint given towards the path to choose to solve a mystery, not the final cords. Plus, and that is the main difference to the mentioned Facebook group, you talk local, probably about caches within a radius of 20 km or so around. Living in e.g. Munich, you hardly would discuss a mystery somewhere up north, e.g. in Hamburg or so.

However, the Facebook group was nation-wide; cords for the whole country of Germany were exchanged. By the way: I only saw extracts from the full list, so I‘m not 100% sure that the caches are really all placed in Germany. But at least the vast majority is in Germany.

But, coming to the second point, there was an additional list which came to light, which held the above mentioned data for the caches in a spread-sheet, so it is easy to search for a specific cache name, cache id or filter by state (one column of the spread-sheet mentioned the state of Germany, in which the cache is placed).

For the moment, it is not clear if the intrusion into the geocheck.org database is related to the list. It is indeed true the vast majority of caches in the mentioned spread-sheet uses geocheck.org as a geochecker, but there are also caches which use a different (or no) geochecker.

As said, all of this was German-centered. Well, actually of course nobody knows if not cachers from other countries participated, too, but for the moment, it has to be assumed it is mainly German geocachers.

Which leads to the question: why the hell geocachers do something like this? Are German geocachers are really that heavily focused on having as many “found it” as they can get? Looking at the above, the answer may be: yes, they are. Well, the number of geocachers which acted in this Facebook group and helped to complete the spread-sheet is definitely only a small fraction of the overall number of active German geocachers. But this small fraction is the one which gives geocaching as a game, which is supposed to be nothing but fun, a tremendous shift to the negative side.

For me, being a German geocacher as well, it is impossible to understand why somebody can be that heavily focused on the find count. What for? Ego boost? Showing up with the personal stats? The latter only works in case the other, “normal” geocachers, are open for that. And on the former: well, of course geocaching can work for that, no doubt. Probably every geocacher is proud (of himself) when finishing a cache with a high T-ranking or solves a difficult Mystery. But if somebody takes it that far heavily exchanging final cords of caches and even breaking into a geochecker server – which is a criminal and illegal act – there something wrong with this person for sure.

However, the impression left is: German geocachers take the game too seriously. Which is not true for the majority of geocachers, but, as mentioned above, is a small fraction of morons which create this impression, not the (silent) majority of german cachers. Which is a real pity!

Reportedly, the case is in the focus of Groundspeak already. Well, I guess Groundspeak has to act, as, as far as I know, Germany is the second biggest geocaching community after the US, so Groundspeak should have an interest to get things straight again.

And, finally: How does the whole issue affect the “daily geocaching” in Germany? Well, you got the full range. Some cache owners removed their Mysteries immediately and put them to the archive while others say: “Ok, let’s see what happens next and how the whole thing develops.”

From my side, having approx. 60 mysteries out in the field, it seems like a bit less than half of them are on this list. And most of them are the easier one. The tougher ones are not listed. Anyway, for the moment, I will leave all caches active. In case we I rushed with logs, I will probably re-think what to do. But I doubt that the number of logs will increase drastically.

But, again, the whole story is nothing but sad…


And here are the four links on the blog posts, which brought the whole thing to light. These are all German posts:

  • http://hilftdirweiter.de/bye-bye-raetselcaches-die-zerstoerung-durch-punktgeile-facebook-user
  • http://hilftdirweiter.de/update-zur-mystery-datenbank/
  • http://hilftdirweiter.de/der-morgen-danach-ein-weiteres-update-zur-mystery-datenbank/
  • http://hilftdirweiter.de/wenn-steine-ins-rollen-kommen/

Sonntag, 12. Januar 2014

An Outlook onto pygcstats 0.7

Note upfront: this is a translation of the original, German-language blog post "Ausblick auf pygcstats 0.7"

For last months it was a bit quiet around pygcstats. The last version 0.6.2 dates back to end of May 2013. However, as there is not a single bug report until today, this release seems to work fairly well.

For all of you who do not know pygcstats (yet): in short words, it is a program which can generate all kinds of statistics on your found caches (at geocaching.com). Statistics can be output onto the screen or into a HTML file.
pygcstats is written and maintained by 25% of the GC-Team DerSchnelleLinus.
Although there are no bugs reported, pygcstats is not perfect. Despite the fact that release 0.6.x is considered as "feature complete" by the author, there are some weak points which should be removed for 0.7.


The main issue of pygcstats up to and including version 0.6 is the template system. Although it works as it is supposed to work, it is not language-agnostic. pygcstats ships with a number of English and German-language templates, but no other languages. In theory, it is not problem to write templates in any other language (like e.g. French, Spanish etc.). But to do so, the user would have to dive into the usage of JSON Template, the so far underlying template engine, as the templates do not contain text and placeholders only, but also some template logic like loops and conditions. Which is, for the common user, a pretty big to too big step.

As a consequence of that, the template system for pygcstats 0.7 was completely re-written. Templates are logic-free now, containing text and placeholders only. This makes it very easy to write templates in other languages and customize existing templates to fit your demands.
A nice side-effect of this is that now pygcstats does not need any external libraries like the a.m. JSON Template any more. Only Python 2.7 or 3.x need to be installed on your computer.


Furthermore, the "custom search" functionality was removed from the HTML user-interface of pygcstats. It is now (again) focused on generating statistics. Nevertheless, searching through your found caches can be pretty handy. Thus, this feature will be moved into its own program (probably to be called "pygcbrowse" or so), which hopefully will be released soon.

The output of the statistical data to the Terminal was removed as well. pygcstats now always generates a HTML file, which can easily be opened and viewed in your browser.

In terms of statistical data, there is not too much new stuff in release 0.7. The biggest addition may be that pygcstats now can generate GeoAchivement badges as well, in addition to the existing myGEOtools and Badgegen Badges.

The programming for pygcstats 0.7.0 is done and this version is already ready for download from the project page, for Python 2.7 as well as Python 3.x. But as the update of the documentation as well as the homepage is still under progress, the announcement official release may take another one or two weeks.