Jump to content

Search the Community

Showing results for '길음역텍사스위치오라 카이 인사동 스위츠[Talk:Za31]모든 요구 사항 충족'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Geocaching HQ communications
    • Geocaching HQ communications
  • General geocaching discussions
    • How do I...?
    • General geocaching topics
    • Trackables
    • Geocache types and additional GPS-based gameplay
  • Adventure Lab® Discussions
    • Playing Adventures
    • Creating Adventures
  • Community
    • Geocaching Discussions by Country
  • Bug reports and feature discussions
    • Website
    • Official Geocaching® apps
    • Authorized Developer applications (API)
  • Geocaching and...
    • GPS technology and devices

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




  1. Sad I missed @bootron last night on the Geocaching Talk Network's livestream about everything Waymarking. Just watched the recorded video and it was interesting seeing the history of the site and how it has grown over the years. Thanks bootron for everything you do to keep both Geocaching and Waymarking possible! Hopefully more people will start Waymarking For those wanting to watch the recorded live stream, here's the video link:
  2. Yeah... I went to find a couple caches for a promotion. Most had maintenance issues, but one was only the top of a bison tube. People were finding that "top" and claiming it a find for over a year. A jerk like me (by talk at events) comes in and NM it. The only NM on that cache... The "CO" got in a huff and archived all caches in the park. I picked up the bison top and a couple others two weeks later, but there's a bunch still there. People were happy to find a top and claim it a find...
  3. Greetings from the WISA Woodsat HQ! After the announcement of WISA Woodsat satellite trackable (TB9GB8G) mid August, we have over 6200 people on the watch list! That also means that I have received a fair amount of messages regarding the satellite itself, the procedure of logging it, launch schedule and many others. Unfortunately I am not able to answer them one by one, so, let's talk satellites in this discussion thread. The most common question is, how you can log the satellite trackable. I have added the instructions to the trackable page https://coord.info/TB9GB8G. The thing to note is that you can only do that AFTER the satellite has been launched. The trackable code is only visibile in the photos taken by the satellite itself with its selfie-camera. You can follow WISA Woodsat project progress on https://wisawoodsat.space. We have blogs and videos showing how the satellite materials are made, how they are machined, and tested. You can also find WISA Woodsat on Instagram and Twitter with the handles @wisawoodsat and #wisawoodsat. Anything else you would like to know about the satellite?
  4. Skimming topics, i decided to dip into the other remaining source of GPS expertise, the GSAK forum. (Duly noting that OP is on a Mac and this does them no/little good.) https://gsak.net/board/index.php?showtopic=36383&view=findpost&p=279765 concludes that there is MTP voodoo within GSAK (!?!?) Perhaps, this being a Microsoft creation as part of Windows Media, plinking around media files is easier there and GSAK somehow hooks to some kind of OS interface to do this. (We've also had people declare the end of Garmin MTP about every six months since the original Nuvi 350, so I don't know if the 67 is really really the end or not...) Still, when I see authoritative-sounding MTP Library things on the web saying things like: It seems quite likely that if Clyde came to me before May, 2008, I'd have told him to take off as it's MS-only and after May, 2008, I'd have told him to take off as sounds like the standard compliance is poor and reading things like https://github.com/libmtp/libmtp (search for 'kext') encouraging people to disable their USB mass storage devices, which requires unlocking several security checks, it just sounds like a bad idea even on MacOS. (I can be a jerk like that...) In that same doc, we have both: "Windows Media Player apparently never close the session to an MTP device." ... "The "Unix way" of running small programs that open the device, do something, then close the device, isn't really working with such devices and you cannot expect to have command line tools like the mtp examples work with them." You may be able to think of a program that very much embraces The Unix Way. It seems likely that you'd be deeply annoyed at GPSBabel running forever or requiring you to reboot between times of talking to your GPS. That's just incredibly dumb, but that's 2000's era Microsoft for you. So even now, if they were to ask, the words "take off" may not appear literally in my response, but without someone else paying for the engineering to bring a quality MTP implementation into GPSBabel along with a device testing budget, I don't see it happening. Heck, Maybe Garmin had to develop one for Basecamp that's usable open source (hahahahaha). Maybe iCaching is interested in developing some kind of code to talk to these things, but I don't particularly see this landing on my desk as an accepted action item without some divine intervention. (That happened on the 60 Cx...) Since I hadn't finished reading the entire internet before posting that (workin' on it!) it possible that https://openmtp.ganeshrvel.com/ may be better, worse, or at least broken in a _different_ way. It doesn't look particularly Mac-like for a Mac app, but I have no vote. Working + Homely > Attractive + Dysfunctional (This is also solid dating advice...)
  5. Ok, let me ask you a question: Why does a magazine cover depicting a shot black kid (I suppose this is the cover in question) need to be on a geocache page? What does it add to the cache and the caching experience of the family trying to find it? Also, you talk about deflecting, but you don't say what the communication with the reviewer about placing a cache on a postal structure looked like.
  6. I'm closing this thread because this is the forum for discussing Geocaching.com's smartphone apps - not for discussing handheld GPS units. There is a separate forum section to talk about GPS and Technology. There's a pinned thread at the top of that forum section, and the most recent post in that forum is in a thread asking the same question.
  7. Hmmmm, seems like I had a small breakthrough here (after several breakdowns): I created this Input: Then I made this flow to handle the "On get input": Then I put a "Talk to girl" command on the "Girl" character and eneabled/handled it: Now, if I click "Yes" the girl is moved to my inventory, and if I click "No" the message is shown with an "ok" button. If I click the "ok" button I am returned to the main screen and can try to accept helping her instead. There are so many "Unhandled" places to click that it's a bit of a jungle at first. Is this a good way to handle this, or are there better options available. Don't get med wrong, I'm pretty happy to get this far. I also wonder how to prevent the input "Talk to girl" from running when she has been moved to my inventory and I click on her?
  8. Based on the other caches you found I could see that there are several events within say 20km of that find location coming up. Why not join and event, talk to people and learn more about placing your first cache there? The community is generally very friendly and helpful.
  9. Spam: Again, opt-in. Harvesting of usernames may be possible if replies are received, but that's also attainable from the gc website itself. Usernames couldn't be harvested from some central list since that wouldn't exist publicly. I'm sure throttling could also be implemented so bots don't spam every combination of letters to find valid/active forwarding emails. Incoming email: I'm not 100% on the technicalities of email distribution, but there's no email transfer to the gc servers if forwarding - the email process would have the servers exchange info and the forwarding server would simply be indicating the redirect destination. It wouldn't be millions of emails being transferred, just pings to tell the sending server where to send the email and how. Not much more intense I'd expect than the already inundated servers being hammered by bots and hack attempts. A ping is negligible; an email forward would be a bit more than a ping, to my knowledge. If that's wrong, then at worst the server receives the email and bounces the content to the forwarding destination server; nothing stored, just proxied over, and that's the last that's heard between them (a bounced destination, eg, would be sent back to the sender's server, not via gc's server). Managing addresses: This would, I think, be the biggest resource. However it wouldn't start out at a list of millions of forwards, and likely there wouldn't even be millions. If it's opt-in, then it would at most provide for active premium members who want to use it. Harvesting: Again, there'd be no way to attain a private email address from this opt-in feature let alone a list. Even after sending an email to a known active user's forward address, the user's private email would only be exposed if they replied directly to the email after receiving it in their own personal external email inbox. Only the sender's email would be exposed, on sending an email to the user - which, is, well, how email works. Email forwarding is a pretty standard fair feature of email providers. Of course GC isn't an email provider, and the system to be able to administer an email forwarding list on their existing email server would need to be built, but it wouldn't be building a complex email management solution on top of what already exists; just a tool to manage the forwarding function, and mitigate/throttle request overloads. All that said, I don't really see this feature being implemented, but it's fun to talk about. Someone might have a good idea for how to make it work in some optimal way.
  10. This is a place where EVERYBODY can talk about the Hoosier state. Feel free to talk about TBs, Geocaches, GeoArts, etc., but keep it within Indiana. Thanks!
  11. Thanks for the report. I can repro this issue. I'll talk to the team!
  12. Thanks for your reply. I downloaded your cartridge and ran it in Webwigo, but even though I move the player into the zone - nothing happens? And the bit about creating a variable and input is the crux of my problems. I think I have managed to create an input: But I have no idea how to use the input. I have looked at the variable bit, but been unable to figure out how to set things up in Urwigo so that it takes the input and then how to use it. If you are able to provide a *.urwigo file with this flow set up, it would be very helpful and hopefully set me on the right path. I really don't understand which action(s) is/are the right one(s) to use. I found a tutorial on YouTube. He did set up a command "Talk to", but ironically he never got around to elaborate no how to set up the handling of it. If using ChatGPT and Urwigo is viable, I would be most grateful if you were able to look at the script to see why it doesn't work. Since even the "shrunk" version of the script failed, I've hit a pretty soild wall. Here I have uploaded my entire project: https://1drv.ms/f/s!Ah32GzvTZ0Lhgo5ykxPYbCRtBf1VJg?e=PsEDY8 Please feel free to download it to have a look at what I have done so far. You will certainly not be impressed, but you should get an idea at what I am aiming for. Again, I greatly appreciate you trying to help out a complete noob here.
  13. Thanks for the report. I will look into this and talk to the team.
  14. It's just inevitable, @Mineral2. If you'll think about it, you've seen this progression for decades. FAT filesystems were of the CPM and later DOS era then things were coded in assembly and for a single CPU to be reading and writing them. Imagine a filesystem on a "disk" (doesn't matter if it's a memory card or a shared buffer or punched paper or mercury tubes or whatever...) as a clay tablet (is that all I've got? We're going to overlook that a clay-tablet is write-mostly? Really? I've gotta work on my metaphors... :-) ) that always has to be internally consistent with itself in case it's suddenly disconnected from the writer. It has separate areas like an index and a table of contents and it has a list of space of what space has already been written on and what's free. With some clever chisel-work, you can make sure that this always works by having the chisel that carves out letters also updating the TOC and the free list all in the same blow of the hammer. It's atomic (unbreakable) on each hammer strike. Sure, the chisel is funny looking, but this is how filesystems work. If the writer is stricken by a diety while they're writing, the tablet is always self-consistent and there's no chance of it getting out of sync. Now, if you have TWO writers trying to hammer away on that same block, each with their own magic chisels, each may try to write into the same blank space twice, each with different data which will hose up the table of contents/index if block 1,347 could possibly contain two different entries. The wheels pretty much fall off of everything if you have TWO processors trying to write to the same filesystem. You've seen evidence of this for decades. Network operating systems work very hard so that hundreds of computers talk to IT and IT talks to the filesystems, introducing locking and such, so prevent this problem. (Remember 3Com and Novel?) Cameras (remember those?) have long had this problem. If the camera is displaying the list of photos while you're connecting to a computer and adding, deleting, and reordering photos, Bad Things happen. We introduced PTP, the Picture Tunneling Protocol to act like an NOS. The CPU on your MP3 Players (remember those?) can't index your songs and display your albums and play lists while you're connecting to a computer and reordering, adding, and removing things. So we extended PTP to become the Media Tunneling Protocol. The final entry in my walk down history lane will indeed be cell phones, notably the very Android that's mentioned when it added memory cards, introducing Android File Transfer (which has applications outside of Android, but has the advantage of being open source and widely adopted by now as well as open implementations for all the OSes that matter) to be the intermediary where everything (the big computer with a keyboard and the tiny computer with a battery) spoke a protocol to AFT and AFT spoke to the tablet, err, storage media. In all these examples, these things handled notifying the other readers/writers when a change happened, when another device connected, and so on. If you think about it, we've seen the same issues in GPSes for years.The Garmin 60CSx wouldn't let you store anything but maps on the SD card and it required a reboot to read them. The Garmin and the host couldn't both access the card at the same time. (Contrast that to the protocol-driven devices where you could watch them draw waypoints on the screen as they were added by software like mine as they transferred.) Nuvi 350, back in 2005, and before it, the i3, would basically go into a catatonic state with the local CPU doing nothing as long as the USB connection was detected. (This was annoying as hell if your charging cable happened to introduce Just Enough resistance on the pin it was supposed to leave unconnected so that your car charger would put your GPS into this flatline state.) When the USB cable disconnected, the device essentially rebooted, invalidating what it knew about the state of the clay tablet, err, filesystem, and would read them fresh. Eventually, most Nuvi mutants and later, the Drive models started using MTP or AFT to do this same thing. The handhelds at least through the Oregon 600 (which may well be my final geocaching GPS) were still essentially shutting down while connecting to USB for this same reason. USB isn't - and doesn't pretend to be - a network file system. USB mass storage actually exposes raw blocks on the device in SCSI command blocks (yes, really - and for an extra laugh, some versions of USB MSTO even exposed floppy drives as SCSI devices). So software liie AFT acts like a tiny little TFTP server that reads and writes files (not blocks, though it may allow partial writes within files, such as for appending) where everyone talks to it and it alone is responsible for actually managing the storage device. (Well, it probably delegates that to lower levels of the OS, such as the kernel's own filesystem and journaling and below that, block level management) Unlike that "DADT" model where everything talks to a server (like AFT) though, in the era of removable media, we often want to be able to take the memory card to something ELSE and read and write it there, like mounting that memory card of pictures in your TV to share with others in the room. For THAT, we can't pretend that the code below AFT has just handled everything for us and we still need everything to be able to read and write the block level jibberish that the appliacations write to the filesystem. While we've created scores of successful filesystems, none are as ubiquitous as DOS's own FAT12, FAT16, and FAT32. The relevant patents (complete with Ballmer-era shakedowns and litigations) have only very recently expired on those. So the filesystem bits (the etchings on those clay tablets) are useful to be able to read and write across devices. That's why we haven't all moved our external disks and our TiVos and whatever to EXT4, ZFS, and other, better designs. So really, Garmin's engineers have two possible stances while building a device - they either detect the edge of an insertion/removal and USB attachment/detachment and they put the host device into a catatonic state where it can no longer access the card data (else things like the map it was displaying might be removed in the middle of a frame draw) or they add something like AFT to negotiate the access of BOTH the internal and external (host computer) access to the common media. Software like GSAK has seen this train coming for years. So far, on dozens of models they've been able to turn off MTP mode and choose the "catatonic" model I've described. GSAK users have been doing this for a very long time. Again, it's a lot of words, but hopefully this explains why these things are this way. (And, yes, I did formerly engineer this sort of stuff for a living..)
  15. "I submitted a gazebo which has a square shape. Declined. Very fairly so as it says in the category that gazebos must be hexagonal or octagonal. What the heck!? I could give many more examples. So, talk about simplify, not complicate. " That sometimes depends on the reviewer who touches you. Thank goodness more reviewers are now being introduced in many categories. Now and there is less mafia in that subject and there are new nice reviewers. In gazebos, however if it is round you get approved. There are categories where it depends on who submits it is voted on or approved or denied, but that topic was talked about and censored in other forums. That said, now there are more reviewers (who are not those who have hundreds of categories) contributing. Which I love. Can we try to maintain "some" quality in Waymarking? This question is sometimes difficult and even seems to me a bit "false" at times. We can't have a party and a geocoin all happy because there were a million WM some time ago and then start to tighten categories to approve less WM or start to change and allow less things. Do you want quality or do you want 2 million? Is this professional? Does anyone get paid for it? Right now I see new people doing WM (and plenty of them in places like Spain, France, Netherlands, etc) who have been doing it for a long time and didn't get tired of it. So I don't think there is a loss of interest. In fact there are times when they say they want something more than geocaching.
  16. No, it shows there are still silly categories hidden out there. If that Bat House is possible, anything is possible, given the author of the crazy idea massages conveniently the peers in this forums with smooth talk and a fantastic presentation of the category.
  17. That the idea of imposing more troubles to whoever is contributing is awful. The requirements are good as they are and above all are those which the peers voted (well, it's editable, I know, but usually it applies what I said). Leave the categories alone. If something, I know quite a few which should be simplified. A practical example: gazebos. Unaware of the detail, I submitted a gazebo which has a square shape. Declined. Very fairly so as it says in the category that gazebos must be hexagonal or octagonal. What the heck!? I could give many more examples. So, talk about simplify, not complicate.
  18. I have published the Final route for the Lewiston Cache Machine. PDF map of the route Bookmark of the caches on the route on geocaching.com A numbered list of all the caches on the route. Link to the Cachetur.no Template file of the route. A Google doc of all this information. https://coord.info/GCAMWGK Lewiston ID Cache Machine Dinner Where: KC's Burgers and Brew Address: 541 Thain Rd Lewiston, ID 83501 When: April 6, 2024, 19:30 - 21:00 Why: To talk about geocaching in the Lewiston Area. See you all there. Terrible Ts
  19. The event has been published. https://coord.info/GCAMWGK Lewiston ID Cache Machine Dinner Where: KC's Burgers and Brew Address: 541 Thain Rd Lewiston, ID 83501 When: April 6, 2024, 19:30 - 21:00 Why: To talk about geocaching in the Lewiston Area.
  20. Phones or GPSrs, everyone I know who doesn't log right away has something - a draft or a flag on the device - that they set when they find it. Offline. Chance they'll log them all when they get home? 50/50 at best. I regularly hold drafts for a few days these days unless I feel the urge to post them or have an imminent immediate reason to (like ftf logs). I don't know anyone who tries to mentally "remember" which cache they found, let alone that and forget the date they found it. Side note: I feel like sometimes there's a bit of cross-talk about the term 'date you found it'. Sometimes I see questions about whether you should 'log the cache the date you found it'. Some people interpret that as referring to the value of the date field on the log, and some interpret it as when you physically post the find log to the listing. I think the vast majority of cachers make sure the Date of the Found It is accurate the date it was found, even if they post the log on a different date. But I think there are some who do have a personal ethic of posting their Finds on the same date they actually found the cache (thus the Date Found value is implied accurate). But there is no rule/guideline saying that the Found It log must be posted on the same date as the log was signed nor the same date in the Date Found value; but it is good practice to date the Found It for the date it was actually signed, regardless of when you post the log to the listing.
  21. Yeah.... no. Not so much a security feature as a sufficiently annoying requirement that would become a game-killer. Won't happen. OK, all this talk of codes and tokens just screams ALR! ALR! to me so I don't see it happening either. And I don't see a need for it. I've only been geocaching since 2017, but the simplicity of finding a cache, signing the physcial log (or sending answers for ECs and Virtuals) then logging a "Found it!" online and sharing the story of the find seems to work just fine. Yes, there are "cheaters", and unmaintained caches, but that has always been part of the game. Adding more to being able to log a find doesn't seem (to me) to be the way to improve the game.
  22. My map fails to load new tiles when I'm out of the data reception area. Such as downtown Peachtree City, or pretty much everywhere. Straight Talk Wireless is the worst! Yes, I know there are other phone companies. But I try to resist driving while watching for cache icons. Sure, a passenger might try it. But just seeing an icon on the map doesn't mean it's a viable cache. It may have been soaking wet and broken for years. If it's a park-n-grab, it likely is that bad. And it sure doesn't mean it's not out of your way. I've tried similar seat-of-the-pants caching where the icon is apparently right here, yet the approach is via the other side of town. Not to talk you out of trying it, though.
  23. I bought a GPSMAP 67 last March and have only charged it four times since then, and most of those times the remaining charge was still well above 50%. On one recent outing, I forgot to turn it off before putting it into my backpack after finding the cache and didn't discover that until the next day. No problem, stiill heaps of charge left. With the Oregon 700 I'd often have to swap AA Eneloops mid hike but the 67, talk about running on the smell of an oily rag!
  24. But there *are* no updates (for this problem) It's just... silence... Of couse, "posts in the bug reporting forum need to be constructive and helpful to the developers". So what do you need to know? Is there anything *I* can do? Is there a workaround? Is there a timeline? Talk to us!
  • Create New...