Ah, yes. The existing interface is key. I think that's why transfers make the most sense, but they do require logging in with the active key, which is not that user-friendly. Still though, filling up blogs with transfer messages seems a bit odd to me.
I do like the thinking behind the resteem over the "buying votes" perspective. Good thinking there. I'm just concerned about promoting a project which could lead to a bunch of spam-like content. Kinda torn here. I do really like the idea though.
Me too, and I'm torn there as well. The reason I'm not using transfer memos, other than the active key issue, is that using posts to transfer allows the system to post confirmation messages as replies.
I suppose an alternative to using a new root post for every transfer is to have each person make a single blog post and treat replies to that particular post as transfer instructions. Might work.
Ah, that might be interesting. You could go even further, kind of like a PGP signature has begin and end comments. You could make it a normal post with useful content, explaining what POCTEST is, etc, etc and then in the body, search for your specific BEGIN and END tags and get the code you want out of that. Could be something like:
BEGIN POCTEST (commands here) END POCTESTThat way it's not a spammy blog post, but a real one. One that also has real functionality in it. Should be simple enough to parse the post looking for the code, as long as it has the right tag, right?
Make it so commands could be inserted into any blog post? That's not a bad idea.
Yeah, as long as the correct control tag is there so you don't have to go parsing every single post. That way everyone gets the best of both worlds. A human-readable explanation of the contract/command/transaction along with whatever else and a real commend to do something.
I really like that because then commands could also be after thoughts, almost like a signature to the post. "Don't mind this, just running some commands for a side chain here."