Hacker News new | ask | show | jobs
by dan_lupashku 1163 days ago
Yes, that was what we were thinking about when starting but we didn't want users to abuse our service.

However, I'm sure that we'll find a solution soon enough.

1 comments

Issue is, you need not mitigation but certainty (for normal database operation).

The quickest path could be having a testing environment set to determine a tentative value for your failure rate, declaring it to the public and declaring in your disclaimer the scope of the your product.

Yes, we'll do this