hydreg

O to akurat bym się nie martwiła - kwestią jest migracja domeny. Z tego co się orientuję to checkery z project-gc wypluwają wynik w jako arbitralny html, więc wystarczyłoby pod domeną postawić aplikację, która na podstawie wyniku z checkera generowałaby kod uwierzytelnienia dla PTTK oraz wysyłałaby jakiś mail z potwierdzeniem do PTTK i osoby wnioskującej w przypadku sukcesu (zakładam, że tak to działało, PTTK nie jest znane z zaawansowanej technologii). Do tej pory weryfikacja działała tak: Wtedy technicznie rzecz biorąc uwierzytelnienie byłoby z domeny geocaching.pl, co nie wymagałoby zmiany regulaminu, co zazwyczaj jest największym dramatem każdej odznaki, bo są one propagowane na strony oddziałów terenowych zawrotną techniką kopiuj-i-wklej. Trzeba by też dopilnować, aby regulamin był pod tym samym adresem lub zrobić przekierowanie, aby nie musieli absolutnie nic zmieniać w opisie Składnicy PTTK, bo to trwałoby wieki.

I realize it's subjective, but so are attributes like Significant hike (what's the difference between Significant hike and Long hike anyway?), Difficult climbing, and Dangerous area or Recommended for kids, yet they exist. That's the thing with attributes - they're more warnings to let players plan accordingly than set in stone facts. Even if not all caches would be categorized accordingly, even some being marked would make a difference.

I've been going back and forth over it, since it seems attribute suggestions are usually shunned or mocked as far as I've read other topics, but... I propose adding "Hard To Reach" attribute to indicate cacheds that are *drumroll please* hard to reach for shorter players (let's say those placed higher than 1.8m/5.9ft above ground, but do not require climbing and no means of getting the cache down is provided). I admit it's very selfish suggestion, as I am a pretty short woman, but I've got talking with other female cashers at recent MEGA and it seems it's not only me with that problem. Imagine approaching a cache that requires significant hike or stealth only to discover you're unable to get it, because of your short stature. That's a major frustration and waste of time that's perfectly avoidable with one attribute. Now, I don't criticize caches placed like this, I'm perfectly capable of bringing small stepladder (yes, really), taking a bike to get a boost or bringing someone taller with me. It would be great to know in advance though, it would really improve caching experience for others like me. It would also serve as warning - I've seen many broken branches and bent fences in places where players attempted to reach caches placed a bit higher and caches muggled, because someone barely managed to reach it but failed to put it back or were spotted because someone was frantically jumping to get it. For those arguing that terrain diffuculty should be the indicator of this - CO's and player's milage may vary. What CO sees as 1.5* because they're tall enough to comfortably get it becomes 3* or more for someone else. Suitable for kids or Wheelchair accessible aren't good indicators either, because there's plenty of caches that are not suitable for kids or wheelchairs that a short person can get to, so filtering PQ with those attributes is a major overkill. tl;dr; "Hard To Reach" attribute would vastly improve quality of caching for shorter players

As the title suggest - new map is not draggable using graphic tablet (Wacom Bamboo) on Firefox (latest stable release). Works fine with Chrome and Edge. I have this issue with almost every single implementation of Leaflet on multiple devices. It's obscure use case, but it exists. I doubt anyone will do anything about it, but there it is - new map is completely unusable in this case. However I know for a fact that it can be implemented correctly, as https://www.gpsies.com/createTrack.do works just fine for me and it's Leaflet-based (on older version too).