The last week has had lots of ups and downs, here. Waiting for an upvote is time-consuming and frustrating. Sometimes comments and posts are "lost" (mine haven't been, but I have read of others).

And there's no reason for me to "wait" for an interface!

Thus, I've come up with the idea of a "Steemit agent" through which I'll read Steemit.

Basically, the idea is: it will cache my desires and release them at appropriate timing.

So, if I do a single upvote, it'll just do it for me. It'll also watch the result and if something failed, it'll retry. I suppose there should be a limit on retries, and it should email me if it gets a permanent error.

But then, if I perform two upvotes within two seconds of each other, it'll send the first one, with the above in mind to ensure that it's recorded; and then three seconds later, it'll send the second one, again ensuring it's recorded. For instance, I might open a post of mine with ten comments, all of which are two or three words ("nice post" etc), and just click to upvote all of them, which would take me about ten seconds.

Why should I wait three times as long to have the desired effect?

And in the past week, it's sometimes hundreds of times as long, as I have to deal with the errors.

So, my "agent" should record my desires, and then in a timely manner, obeying the delays, send them to the blockchain to be recorded.

Upvotes are the least of my concerns though! Often I'll have a "discussion post" with larger responses, and want to answer many comments. There's a limit of 20 seconds for comments, and I'm a fast typist. Penalized for developing a skill -- it's like I'm dealing with government! :)

And also sometimes I'll have taken a walk in the garden and gathered several photos and videos, and want to make a few posts -- but there's a limit of 5 minutes between posts. Computers are great at waiting! Me, not so much.

So, just curious whether anyone has started working on something like this. Thanks!

---