Be careful. Just because one of my privkeys signed the first input to a transaction, it doesn't mean I agree with the content of the CLAMspeech. The transaction could be a withdrawal from Just-Dice. When withdrawing from Just-Dice you can specify any CLAMspeech you like. The transaction's inputs will be signed by private keys in the hot wallet, but the owner of those keys doesn't endorse the content of the CLAMspeech.
This is a good point. It's another reason for me to step back and think more carefully about "design" issues.
In other words, it's been one of those days of taking two steps back.
I worry that we're going to end up hard-coding many different similar-but-different features into the CLAM client, and wonder if there's some way we could generalize it so we don't have to edit C++ code for the next person to dream up a use for CLAMspeech.
(Cue sighs and groans from Creative and Kef...)
I've read before that bitcoin restricted OP_RETURN to 40 bytes because this is enough for key value pairs for a distributed hash table. Maybe a feature for storing such key value pairs would be sufficient for many different purposes.