Hacker News Reader

Comment by rmorrison | Hacker News Reader

I don't mean this to sound snarky but I'm having a hard time understanding the basic utility of blippys service.

It's the easiest way to share your credit card information with the world.

I was just thinking on the way into work this morning that not enough people have my Discover Card number.

(OT/X-Post Just getting to this now:) Silly, everybody knows you don't have a Discover card, because you're on Facebook, where all of us friends know this about you....

1) Get your discover card number as a tattoo (make sure to include your name as it appears on the card, expiration and 3 digit code from the back).

2) Submit photo to hacker news

i hope you mean it in sarcasm way...

btw i cant believe nobody point a finger on google yet, this part of their fault too. there should a 'proper' mechanism on their webmaster tool an option to excluded a sensitive data Or make it an opt-out features Or add one regex line to detect an anomaly data on their search.

ffs they have billions to tinker around with it

There is such a proper mechanism: robots.txt. Whenever I put all my users' credit card numbers on a public web server I make sure the URL is properly protected by robots.txt. If I want to be absolutely sure everything is safe I use CSS to make the numbers invisible on top of that! ;-)

Why on earth would you let credit card numbers be publicly accessible; furthermore, one can simply view source to see those numbers. Security through obscurity is not a very good approach - you should read up on PCI compliance by starting here: http://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Secu....

Obscurity? Pffft. Simplicity! Nothing beats an HTML page right there in htdocs. You can store anything there and it's totally NoSQL as well. Anything else would be premature optimization. Do the simplest thing that could possibly work! Agile! I've got it all covered by unit tests so there can't be a problem. And if there's a breach I'll just rewrite it all in Haskell. Who are you anyway to tell a seasoned professional how to deal with credit card numbers securely? :)

Google shouldn't bear responsibility for indexing something sensitive, as the sensitive information should not be reachable via any link anywhere, let alone on the public Internet. It's about as sane as expecting the government to clean up after one's own mistakes, and just as damaging to the concept of personal or corporate responsibility.

Reply on news.ycombinator.com