>>14
There could be more features. Offering a tohouing complete scheme interpreter could invite denial of service attacks if its time and space access wasn't regulated.
I know, it's a bit crazy. It really doesn't have to be touring complete. Just a couple of functions (some hidden or undocumented, because it's fun) that could take arguments. It could be used to upload PGP keys. That way the feature doesn't go in the way of people not interested in it.
Yes. Spam is easy to detect. After all, it is computer generated. To keep the spirit of /prog/ that's the only thing that can be blocked.
I fully agree.
I'm hesitant to take away any features already existing here. I would aim to create a shiitchan clone, even going as far as to emulate its bugs that don't compromise anonymity. Tripcodes are not robust but they serve a purpose, and as long as some people like to use them they should remain. PGP keys would be nice as long as they didn't get in the way too much for those not interested in seeing them.
I guess you're right about tripcodes: I should not forget that the purpose is to offer something nice for the random user, not exclusively for me.
About emulating shiichan bugs, if you're only speaking of BBCode, it could be implemented as a feature
(markup shiit-compatible). Markdown? Sexp-code? One thing that I do miss here is the ability to use mathematic notation.
I was seeing the whole thing as a very minimalistic board, where most of the work is done client-side with user-scripts. (audience being a bunch of expert programmers). E.g, an user browsing with emacs can always use auctex to view the latex formula in the buffer. Firefox users would have to use a Greasemonkey script...