Bernike

Since a day doesn't end at 23.45, it would be more useful to set any time we want and not just .00, .15, .30 or .45. So please make the day end at 23.59.59 ??

I know, but I try to seek help wherever I can =)

Who called others names? I didn't hijack this thread, I am also disappointed by Groundspeak's attitude. The topic IS about that.. Problem?

Call it whatever, rules, listing guidelines and requirements, the name doesn't matter. Here is an excerpt from 2018: "Additional events for the same main day and area of the Mega/Giga-Event are not eligible to be published. The "main day" of the Mega/Giga-Event is the date on the cache page." When my event was published, then shortly after retracted (YES, it was published altough it violated the "guidelines"), then it was actually a harder 'rule' that included one day before and after the MEGA that one couldn't have an event. Now it is milder and only includes the MEGA day. It still is a violation if an event is being published on the MEGA day, additionally being close to the MEGA GZ. It should have been retracted like mine in 2016. So, technically, both my event in 2016 and the one in 2018 violated the exact same rules/guidelines. Both were published, but only one retracted. Here's where the problem starts. The sentence "Additional events for the same main day and area of the Mega/Giga-Event are not eligible to be published." states clearly what applies. No way this can be misinterpreted nor it could be in any way flexible! This was valid both in 2016 and in 2018, but still, the outcome/"solution" is different.. Interesting.

nope

"Additional events for the same main day and area of the Mega/Giga-Event are not eligible to be published. The "main day" of the Mega/Giga-Event is the date on the cache page." Nowhere in the above quote it is stated that there can be exceptions. /not sarcasm

"Additional events for the same main day and area of the Mega/Giga-Event are not eligible to be published. The "main day" of the Mega/Giga-Event is the date on the cache page." Then what is this? Some get to have a published event, some don't.. It's clearly stated: no events on the same day and area as the MEGA.

Well, my event was against the rules back then. Not much to do against it. Felt like it was an unnecessary rule. But a rule is a rule and it should be valid for EVERYONE!! I would be happy if everyone were treated equally. No exceptions! Otherwise why have rules? If A can, then B as well. If A can't, then B either. Simple as that. It would be way less complaints if they treated everyone equally and listened to the cachers when they point out mistakes. If a rule is flexible, then this should be stated, maybe?

Then why are there rules? :)))))))

Groundspeak has rules. For EVERYONE. Seemingly, there are customized exceptions. That is what I can't understand. The WHY part.. Why aren't the rules applied to everyone? Why are there exceptions?

They HAD the answer, the plaque/infoboard was still in place, otherwise they would't have logged it.. Einstein! But my point is, if HQ goes and modifies their logs, then why the hell don't they do anything against an event that broke the rules? Just to be clear, I am not grudging over that my event was retracted. I am grudging over the fact that the rules are not applied equally to EVERYONE. If I can't have an event that breaks the rules, then the next one, either. Isn't that logical? Okay, a reviewer made a mistake. But when I contact HQ to do something about is, just like they DID something on the archived virtual, then they have power to DO SOMETHING. In any case.

Define 'not supposed to'! It was no sign at all that the archived cache could/shall not be logged.

Logically, a law/rule comes out first and then it is applied. Otherwise, HQ can just claim whatever they want. This is not fair!

What difference does it make? A find is a find, archived or not. It IS allowed to log archived caches. If they don't want people to log something, then lock it or I dunno. But it is insane to MODIFY their logs from found to DNF a year after they found it. Whaaat? No explanation, nothing. A friend of mine was denied to get a challenge published because of some upcoming rules. What? So, if something is NOT in power YET, it can still block a cacher from having a cache published. So, a criminal may be charged with a crime there is no law for yet, but it will come in the near future. How insane is that??

It's not forbidden to log archived caches if they are still in place..

And I know they do not publish caches, but when someone warns Groundspeak about a broken rule, then they CAN actually take their time and fix it! Yes, nobody is perfect, but rules are rules. THEY made them..

Imagine this. A virtual in Estonia was archived. A team of 10+ cachers logged it in 2016 after the archiving. Nowhere it is written that you cannot log an archived virtual. HQ locked it after a year and changed everyone's log after the archiving into a DNF. Why? After several contact mails to HQ, they don't answer anything. I also wrote to them about the MEGA and the event being on the same day. A rule was broken. They actually CAN fix the problem, but they give a dadgum. This post is about being disappointed in HQ, that is why I wrote my story. They can be unfair.. I do not like this. I think they should concentrate on fixing caches and event that are against the rules and then ask about cache quality. HQ/Groundspeak quality, anyone??

I am not holding a grudge, I just think it was unfair in my case. BUT, I am asking who the rules apply to as it is clearly stated that it can NOT occur an event on the same day as the MEGA, thus an unofficial event was published in May 2018. So, RECENTLY!! Read my post carefully. It is a recent rule with a recent happening!! Still, HQ does not seem to care. In my case they cared 2 years ago. WHY don't they care NOW??

I also have an issue that I mailed HQ about and they don't seem to care for some reason.. I'm disappointed!! Here are some rules.. Geocachers often host "side events" on Mega/Giga-Event weekends. Over the years, some of these side events have become more numerous and can unfortunately distract from the main event. As a result, there are now some limitations on side events around Mega/Giga-Events. Additional events for the same main day and area of the Mega/Giga-Event are not eligible to be published. The "main day" of the Mega/Giga-Event is the date on the cache page. Additional activities on the main day should be listed as activities in the main Mega/Giga-Event page (with separate waypoints as needed). Emphasys on the NOT eligible!! Yet, I have seen such a non official event published, having the same day as the MEGA. No reaction from HQ. The event was very near the MEGA GZ. Additionally, TWO non official events were published a day after the MEGA. Rules for this one: Unofficial side events (not hosted by the main event organizers) on the days before and/or after the Giga-/Mega-Event day may only be published if they don't conflict with official side events. These were also very near the MEGA GZ. This happened in May 2018. Yet, in 2016, I was not allowed to have a birthday event one day BEFORE the MEGA. There were NO side events that day. My event would have been approx. 3 miles from the MEGA GZ, and definitely NOT 0.5-1 miles as in the case of the 2018 MEGA. Now, the big question. WHO do the official rules apply to? WHO??? The cachers? The organizers? HQ? It seems that it only applies to some people and NOT everybody!! Now, the rules might have changed since 2016, so whatever that my event could not be published.. (I'm sorry, it WAS published, but then retracted actually...) The reason was that over 900 cachers would come to my event. Would I have been bothered by that? Definitely NO! I would just have been glad that someone comes for my birthday event as nobody wanted to come to that MEGA, no family, no friends. What is wrong with some company? Ok, rules might have changed. But now, in 2018, these rules exist. No side events on the same day as the MEGA, thus such an event was pulished. WHY? WHY? WHY And WHY does HQ not bother resolving this issue?? Rules should apply to everyone!

Well, I knew what GC it was supposed to be, but only after pushing the 'Activate Your Trackable' button I saw it's a completely different name and it was already activated, so no way back! I wrote to Groundspeak now. Let's see what they can do about my typo..

Thanks! Sooner or later I would have written to them, but I thought maybe there's a simpler way. Guess not!(:

Hi! I really need some help here. I have ordered some geocoins and when activating the Oreo cookie one, I misread the tracking code. Instead of a 'Z', I typed a '2', silly me! Even with the wrong code I still managed to activate it and when I saw the name suggestion (California car or so - totally differing from what it should have been, an Oreo Cookie), I realised my mistake. Now I have both the 'right/Cookie' and the 'wrong/Car' coded geocoins activated. What to do? I activated something I don't own:(

Hi! I am just wondering how to geocache more effectively. I currently have a Garmin etrex Venture and we've uploaded POIs on it, so that it shows some info about the cache, but still not everything. I'm planning to buy a Nokia that has a GPS. Would it be wise, as I heard it has Symbian or Windows and Android phones are better. Is that true? I'm a huge Nokia fan, so I'd really like to know what kind of apps I could use. My choice would be a Nokia N8:) I've never used a smartphone for geocaching and I'm also considering buying a Premium membership. How would it work, then? Load the caches onto the GPS? But with what app? Also, how would it be possible to geocache abroad and log them at the same time without paying a high Internet bill? Thank you:)

Umm, I thought of max. 200 euros! And I'd like to buy a used GPS in any case, just wanna know what I should be looking for, then

Oh, thanks! Then which Garmin GPSmap 60 is better to buy? I have no choice, but to buy a new GPS.. A newer one