The problem with this addition is that you are looking at it from a other blogger platform, single database perspectives.

But, this is painful to do on a distributed blockchain.

---

Doing this is from your computer extremely easy if you know how to talk to the block chain. If you are on a linux machine you can tell it to do it at any time you want. You just write a script, and viola, done. (see piston)

From a decentralized point of view, this is a pain in the ass, almost unsolvable problem.

As in, where do you store it?

• on the blockchain
• on your computer
• on some server you have control over.

If you store your post on the blockchain, everyone can read it. Why would anyone wait? You could write HTML code that would not show posts that are supposed to be in the future, but that often backfires on the developers. (if you have your computers clock set wrong, it shows no posts, type of problems)

So it can't go on the blockchain, so where does it go? It goes on your computer, or on some server. (that server not being steemit) If it is on your computer, you can just have a cron (cronological system on linux/ does something at a specific time) job execute a script and upload your saved post. But if your computer is turned off at that time, it won't do it until you turn it on again.

You could do the same thing on a server. Hostgator minimum package, and you run the cron job there. That server is almost always on. But that requires you to push your text file up to the server and start a cron job.

Now, an interface can be created for all this. It is both easy, and painfully long to write. There are so many piece that need interfaces... and then you have to port it to all the platforms...
The part of the interface I would have the hardest time with would be the what will it look like when uploaded. This is trying to hit a moving target as steemit modifies their display.

So, where do you want to store your posts for the future?