HN user
Hammer is not dangerous intrinsically. You can build shelter for people in need with it, or kill a human being.
Just like this tool; you can make a auto research bot, or automated spammer.
Even in that worst case: Remember that there were already bad human beings. This is why we created laws, intelligence agencies, militaries and police systems. And security practices for websites, such as bot protection systems.
LLaMA doesn't contain any meaningful training data in Turkish
Where should we follow you so we immediately know when you published that?
Microsoft just released Stable Diffusion competitor: https://designer.microsoft.com/
It's giving me:
We detected some suspicious activity. Please refresh the page or try on another browser again. If you still face the issue, please contact support to register an account.
1. Create fake url endpoint. And go to that endpoint in the adversary's website, when your server gets request, flag the ip. Do this nonstop with a script.
2. Create fake html elements and put unique strings inside. And you can search that string in search engines for finding similar fake sites on different domains.
3. Create fake html element and put all request details in encrypted format. Visit adversary's website and look for that element and flag that ip OR flag the headers.
4. Buy proxy databases, and when any user requests your webpage, check if its a proxy.
5. Instead of banning them, return fake content (fake titles and fake images etc) if proxy is detected OR the ip is flagged.
6. Don't ban the flagged ip's. She/He's gonna find another one. Make them angry and their user's angry so they give up on you.
7. Maybe write some bad words to the user on random places in the HTML when you detect flagged ip's :D So the user's will leave the site and this will reduce the SEO point of the adversary. Will be downranked.
8. Enable image hotlinking protection. Increase the cost of proxying for them.
9. Use @document CSS to hide the stuff when the URL is different.
10. Send abuse mail request to the hosting site.
11. Send abuse mail request to the domain provider.
12. Look for the flagged IPs and try to find the proxy provider. If you find, send mail to them too.
Edit: More ideas sparkled in my mind when I was in toilet:
1. Create fake big css files (10MB etc). And repeatedly download that from the adversary's website. This should cost them too much money on proxies.
2. When you detect proxy, return too big fake HTML files (10GB) etc. That could crash their server if they load the HTML into the memory when parsing.
Second one in Go:
func IsPrime(n int64) bool {
return big.NewInt(n).ProbablyPrime(0)
}
This is just anectodal evidence anyways. And these are tools in the and, and no point for a "tool fight".