[RESOLVED] Posting replies to Gear Swap listings may expose your email…

I’ve done many, many deals on Gearswap and I’ve never seen the other party’s email address revealed until one of us asks the other for their PayPal address so money can be exchanged.

If you post a comment on a Gear Swap it sends an email to the person who posted the Gear Swap. In that email is the Email Address of the person who commented.

I just verified this, as someone commented on my Gear Swap several hours ago. I now have their name and email address. Thankfully I am an honest person and will dispose of this info. :)

Sorry, this pertains to the Commenting section on the Gear Swap, not the link to send them a PM. That may have confused a bit there.

I brought this up months ago in the website issues forum, never heard anything else about it. It should be a known, albeit seemingly ignored, issue.

I’m sorry it got lost when you reported before, RMB.

Johan, can you make a comment on this test post I just made please? https://backpackinglight.com/gear-swaps/just-testing/

I’m not a programmer, but I’ve fiddled around with enough code in my life to know there is a good probability that such functionality could be commented out of the code without much risk. I think the intention is to automatically show email addresses for PayPal verifying, but not everyone would want that info disclosed just asking a question. And not everyone uses the same email for BPL as they do PayPal.

Ok. I got the notification and I see what you mean. I will log this and report back.

This has been marked as a priority for Dev team. I will update the thread as we get word on this. Thank you for bringing this to our attention.

The issue has been resolved!

I just tested it with the test post from yesterday and I only get the member’s username, not their email address.

There is a lot of work going on behind the scenes right now. We are setting up lots of systems. One of those is the ability to communicate and track bugs and feature requests more effectively.

Cool. I figured it must have been a super easy and low risk fix. Such things like this in code usually require some specific logic for displaying character strings, and is very unlikely a buggy byproduct of other systems, thus it probably just needed to be removed from the code logic, that would be pretty isolated from the rest, making it a safe fix.

I used to work as a video game designer, who created bugs and fixed bugs. It’s in my DNA to get mad at seeing bugs and then work to destroy them.

Our motto in the game industry is: “You gotta break S**T to make S**T.”

Or the song: “100 bugs of code in the queue, 100 bugs of code. You take one down, patch it around — 120 new bugs in the queue.”