Comment by Cyberdog

I don't understand the cryptographic aspect of it. Unless I'm misreading things, which may be the case, it will take several minutes of basically cryptocurrency-style "mining" to find a key which matches a message on current relatively fast consumer hardware before a "board" can be posted. If the goal is validating a message hasn't been tampered with, is that serving some goal that something like sha512 or even crc32 wouldn't match? (It also means that it would basically be impossible to create a Spring '83 message using hardware actually contemporary to spring '83.)

Also, I'm not sure how important having the month and year in the identifier is to the whole thing, but using only two digits for the year has obvious ambiguities.

That the client must "situate each board inside its own Shadow DOM" seems to imply that all clients must effectively be web browsers too. A far cry from the original RFC 865 which could basically be done with netcat.

All in all this seems like a complex way to solve a seemingly easy problem.