3 ms·
No crusade, just offering constructive suggestions to the OP. Detectable, maybe -- month one, a few homonyms which could be spelling corrections: been -> bean
by jjgreen 2y ago
No crusade, just offering constructive suggestions to the OP.
Detectable, maybe -- month one, a few homonyms which could be spelling corrections: been -> bean etc, month two, (near-) synonyms: bean -> lentil ... throw in a few UFT8 homglyphs to add noise. Unlikely that that sort of corruption would be obvious to a machine, then manual checking is needed, and do they have the manpower for that?
- tivert 2y agoIt's also a programming website, so that kind of thing would probably be even better targeted at code examples and keywords (e.g. change a function name to something subtly inappropriate). That would have the added value of helping to make the derivative AI suggest errors, making it even less useful. Also one could also use a "masking" edit. Make the defacing change then another more innocuous one. > throw in a few [UTF8] homglyphs to add noise That seems like it could be defeated by a pretty straightforward normalization task. Either just a straight mapping or a mapping that's applied contextually (e.g. replace an omicron with an o, but only when the adjacent characters are ASCII).