If you pay users to store copies of your data, how do you ensure that they don't claim they have extra copies? An interesting problem! Public Incompressible Encoding for e.g. FileCoin: https://hackingdistributed.com/2018/08/06/PIEs/
Related Posts
I'm working on arity errors in Garden, my toy programming language.
Rather than just saying "expected 3, got 4 arguments", I'm trying to report where the extra argument is, or what extra argument was expected.
It's incredibly hard to explain adversarial problems to users. I see gamers sincerely asking "why doesn't the publisher just fix the cheater problem?".
This is exacerbated by the fact that sharing too many details of anticheat can make the problem worse.
I'm playing with Zeal/Dash so I can view stdlib docs offline.
(I've been coding on public transport recently, without a reliable data connection.)
Anyone have tips for making the most of this setup? AFAICT docsets are basically HTML underneath.