Bloodwoosj

Dit geldt namelijk óók voor mij...... Schijnbaar uitgekotst voor het leven. Maar dat "probleem" is met dit forum opgelost:-))) En geloof mij of niet; je "mist" daar niets. -= GensNet =- Jawel ik mis daar wel iets en daar ben ik heel blij om. Op dat forum loopt niemand rond die zo lang, zo veel en op zoveel plaatsen zo negatief over één bepaalde persoon in NL loopt te zaniken, zeuren en zeveren en zakkenwassen dat het zoveel mensen de keel uitkomt. Vandaar ook dat ik het bijzonder treurig vind dat dit nieuwe nederlandtalige .com forum wederom wordt aangegrepen om je persoonlijk beklag te doen op precies dezelfde wijze als waarop je nu al in zoveel andere fora gedaan hebt. Jouw probleem wordt echt niet opgelost met dit forum en dat weet je zelf ook best. Greetz, Bloodwoosj.

I don't know if this idea can work out fine in a country with more than one official language. For instance Belgium (Dutch, French and German language) or Switzerland (with four official languages). Greetz Bloodwoosj.

I'm sorry, but there's no mention about that in my original post. There's no intention whatsoever to weed out poor quality this way. In fact, you will not find anything mentioning quality in my original post. I just stated that it would be nice if there was something like the number of people ignoring a cache vs. the number of people watching a cache. Greetz Bloodwoosj.

In my opinion anyone using this as a rating system is using numbers the wrong way. Neither the number of people watching, nor the number of people ignoring a cache can or shoyld be used as a rating tool. If people do so anyway, no one can prevent them, but hey, then you could argue why we don't want to abolish the number of people watching a cache...

To me it just makes no sense why the number of people watching a cache is an accepted feature while the number of people ignoring a cache is not accepted. I agree, there is no sense in it being a kind of rating system. It's not the intention of the number of people watching a cache, neither is it the intention of the number of people ignoring a cache. And no, revealing which users are ignoring the cache is not the intention either. This would be against privacy policy I guess (however I find it to be strange that PMO-cacheowners can see which users have taken a look at their caches?!). Someone who wants the world to know they do ignore a certain cache can make a public bookmarklist of his/her caches being ignored. Just since the ability to see the number of watchers it also would be very nice to see the number of people ignoring a cache. Without numbers being some kind of quality judge, as y'all know: there are lies, damned lies and statistics ;-) Greetz Bloodwoosj.

For several years now there's the possibility to see the number of users watching a cache. For several reasons people like to watch a cache (there's a coin in this cache I'm following, judging to the logs this seems to be a cache that's very interesting, I'd like to see who is going to be FTF, etc. etc) It would be very nice if one was also able to see the number of people ignoring a cache. On the right hand side of the cache listing this could look a bit like this: 12 user(s) watching this cache. 7 user(s) ignoring this cache. Greetz, Bloodwoosj PS, this idea it was not my own, it has been suggested on the Dutch Forum. I thought it to be fit to bring to your attention on the Groundspeak forum.

Same problem over here (Netherlands). Two caches both published in Belgium last weekend, both well within the insta-notify radius, less than one mile apart from each other. One insta-notify mail from cache no. 1 in my mailbox, NO insta-notify from no. 2 less than 24 hours later. It's definitely not a spambox-problem, neither a provider or email problem. A friend of mine has noticed the same problem with the same two caches. Problem has been going on since a month or so, new caches keep appearing on the maps, received notification of most of them, but there are several caches without any instanotify message at all. Hope this can be solved. Greetz, Bloodwoosj.

My closest unfound cache must be somewhere within 10 yards from me right now. It's a magnetic micro hat my wife has hidden somewhere in the house and which I will rehide it for her to find as soon as I have found it. But I haven't found it for 5 weeks now

If the box or can is not rusty I don't repaint it. The yellow letters mentioning the original ammunition are easily removed (just a matter of seconds) with acetone. Greetz, Bloodwoosj.

This person has also posted notes on at least one other (but probably more) cachelistings with same content. Can these notes also be removed? Greetz, Bloodwoosj.

Hey everybody. Think I found a partial solution for everybody suffering the parsing and scrolling problems. At least it works for me, maybe this will help the tech-guys from the website to solve the problem. Discovered it during experiments while suffering the parsing problem today. If I use the zoom-out button on the map (the one with the minus sign on) and move the pointer across the screen, no new caches will appear in the now enlarged area and the parsing problem turns up. But... If I reload the map and take the same actions, but keep the pointer without any movement (inside the zoom-out button area), then there's no parsing problem and all available caches appear on the new map. After that moving the pointer is no problem I can repeat the process as many times as I want, zooming in and zooming out, until I move the pointer before the map has been reloaded and the parsing problem will appear again. The same with the scrolling problem. Leftclick the map, get a hold on it, and move it into the desired direction. Let loose of the map, do NOT move your pointer, wait a few seconds, and the new map will appear (at least it does on my pc). If the pointer is being moved, before the new map has reloaded, the parsing problem will appear again. Try it yourself, hope this will be of some help to you. Greetz and good luck, Bloodwoosj P.S., As said in a previous post: I use XP, IE7, DSL connection.

Browser: IE version 7.0.5730.11 Op. System: XP Connection: DSL Scroll and parsing problems with the map. Still hoping someone can find the cause...