4 ms·
You found out the right first step yourself: Block the source IP address. Sure it will turn into a game of whack-a-mole with them changing their IP but eventual
by pilom 13y ago
You found out the right first step yourself: Block the source IP address. Sure it will turn into a game of whack-a-mole with them changing their IP but eventually, their customers will get fed up with their downtime.
Second idea: Javascript redirect all of your pages to your own subdomain. Again, its just a step in an arms race, but this would be a little too hard/expensive to take to court. You can win an arms race if you try.
- joeyjones 13y agoFor now I have added a news post with a link to the proper site and am debating between blocking the IP or delivering a static page with a link to the proper URL or a javascript redirect to the proper site.
- fragmede 13y agoI'd do a javascript redirect so you get the ad-views and the users of the site see the new URL. (for now)
- deleted 13y ago[deleted]
- jarrett 13y agoIf you have a hard time determining their IP, here's a trick that might work. Visit their site with a unique but innocuous-looking path or query that would never be accessed by a normal user. For example: http://4co.in/?q=1 http://4co.in/?q=1 If the query string is being passed through, which I suspect it is, you can use the query string to easily locate the corresponding entry in your own logs. Or, if the query string isn't being passed through, you can use a path instead: http://4co.in/q http://4co.in/q You probably already thought of this technique. I decided to post it anyway in case you hadn't, or in case anyone else is facing a similar challenge.
- xauronx 13y agoClever solution! I like it
- intev 13y agoBuilding on this, you could create a script on your server that requests a random url, then greps that url in your logs to figure out the IP and then add that to the banned list. It'll be an auto banning machine!
- geolqued 13y agocountermove: he works it out and blocks your magic query - query needs to be made from somewhere indistinguishable from normal requests. Changing IP would be best... maybe via tor. A unique sequence of legitimate requests might be more difficult to for the other side to detect and it won't result in 404s. Could randomise the sequence and each can come from a different IP as long as they were synchronised properly.
- jarrett 13y ago> countermove: he works it out and blocks your magic query He very well might. But my estimation of the thief's skills is low. I could be wrong, of course. > A unique sequence of legitimate requests might be more difficult to for the other side to detect and it won't result in 404s. Could randomise the sequence and each can come from a different IP as long as they were synchronised properly. That's probably the best bet. A legitimate but very winding path through actual links on the site would work quite well. Given enough steps, it would almost certainly be unique. Because you'd be varying the path each time, the thief would find it hard or impossible to block you.
- lmg643 13y agointeresting that they didn't change the donation addresses. so if someone uses theirs, and likes it, sends some BTC to them, it will go to you?
- joeyjones 13y agoYup, donations should still go to me.
- trevelyan 13y agoWhy do you jump to the assumption that they're malicious then? Put a few more branding elements into your page design, so that visitors to their site will understand that they're redirecting your data. Then take advantage of the extra publicity that they're giving you.
- LanceH 13y agoThe more subtle response is to feed them bad data until they can't trust you.
- mcv 13y agoBad data would have my vote. It's nasty, subtle, harder to detect, and it would undermine people's trust in the culprit.