Re:You either die an MVP or live long enough to build conten...
by mrkurt on Tuesday September 28, 2021 @03:20PM
(#28686381)
We're primarily trying to prevent fraudulent payments combined with expensive VMs. Throttling CPU to almost nothing on high risk accounts sounds delightfully irritating.
We also get the less resource intensive, but still harmful abusive apps that port scan the internet. Those are relatively easy to detect. We generally don't want to be a source of port scans so we shut them off pretty quickly.
Re:You either die an MVP or live long enough to build conten...
by Nextgrid on Tuesday September 28, 2021 @07:02PM
(#28688470)
I wonder if you could return bogus but plausible results to port scans? Either whitelist a set of safe ports such as HTTP(S?) so that if they try to "curl google.com" to confirm whether everything is OK they get a good response but silently drop everything else causing their scan to return negative on all ports.
Re:You either die an MVP or live long enough to build conten...
by New_California on Wednesday September 29, 2021 @02:44AM
(#28690905)
How do you know the payment was fraudulent? Is there any possibility it can affect honest users?
If resources are free then you could even actually deploy their app and either whitelist it for their own IP or only allow very few requests before taking it down.
This would be even more frustrating and could ruin whatever they plan to do with their abusive app in the first place. Let's say they deploy their malware/phishing page, test it a couple of times (possibly from a different IP) and it works. They then start spamming the malicious link and waste decent amounts of time/money/processing power, not realizing that the link was dead after the first 10 hits.