4 ms·
recommendation: respond with fake data, based on source IP. the problem will take care of itself.
by icedchai 13y ago
recommendation: respond with fake data, based on source IP. the problem will take care of itself.
- joeyjones 13y agoI am going to lok into this later today through nginx. I am planning on having every request from their scraping IP return a static page linking to the proper site.
- kevin0722 13y agoExcellent. Keep us posted. Good luck.
- deleted 13y ago[deleted]
- MarkPNeyer 13y agothis is probably better than banning their source ip, as it will take longer to detect and piss off their customers. also, report them to adsense and anyone else serving their ads.
- beauzero 13y agoYes...yes...yes.
- macNchz 13y agoGigabytes of fake data. Let them eat /dev/urandom to their heart's content.
- Zancarius 13y ago> Let them eat /dev/urandom to their heart's content. No! You can't just give them purely random data. No, sir. That would be easy enough to detect. What you need is plausible randomness. Shift the value of every transaction by a small percent. Trending everything downward over time, but making it plausible, would be far more entertaining with random upward trends. Best buy now before it gets too expensive! Oh, I'm sorry? That wasn't the actual price? Well, you'd best use a reputable source! If you're going to poison the well, you don't want to be caught. You want them to wonder at what point their data set diverged and for how long they've been serving incorrect data. Sinister points for interspersing legitimate data with munged data. The trick with being evil in this case is to be subtle about it. They want to scrape all your metrics? Let them. You just can't guarantee the accuracy of the data they're scraping, right? [wink, wink]