>>17
The main problem with
>>19 was that people using third-party clients to
post to
/prog/ sometimes end up being banned, which is not a great thing. The solution proposed by OP in that thread would only be convenient if it were possible to use a third-party program to post to
/prog/.
I would suggest a signing system similar to
>>19, but trivial to use even from within a browser.
My current idea would be to use algorithms (such as JSB-1) exactly as specified in the document from
>>19, but feed them the current UTC year (four digits) and UTC week number of year (00..53), with Monday as first day of week, in the "
date -u +%Y-%W" format (without the newline) and use the first 16 digits of the resulting hexadecimal hash as a tripcode. Using a trivial algorithm, it becomes easy to remove posts that are more than, say, one week away from the date they were posted. The key only needs to be generated every week, as I doubt that script kiddies will manage to crack a tripcode completely in any less than a week.
It will become easy to generate all the date-key associations in advance for a given algorithm, and a simple Javascript script will,
sans doute, manage to prune posts without a key or using an expired key.