Saving posts offline manually and then copying each post onto the Hive frontend for post scheduling still has room for forgetting (even though it makes the posts to be scheduled unlikely to be lost). What if I accidentally leave one day with a scheduled post at the wrong time, or without a scheduled post at all? There is also the risk (though low) that the backup document gets lost. 😨

My plan is actually to schedule posts on at least two separate Hive frontends (such as #PeakD and #Ecency) for each day (and burning payouts for a post when the two posts for the day are too similar). In case my scheduled posts get deleted from one Hive frontend for any reason, I still have the scheduled posts from the other frontend to restore my scheduled posts. A frontend losing all scheduled posts (of every user?) happens rarely, so two frontends losing all scheduled posts on the same day is extremely unlikely. Furthermore, to further ensure that I actually have posted during the day (to exclude minor risks such as running out of Resource Credits), I would partner with another active Hive user who also wants to be able to post (at least) once a day, where we should try to remind each other in case one of us hasn't posted yet for any day at the scheduled time (which is preferably 30 minutes after the start of each day for the #HiveBuzz bot which is at UTC time zone). 🤓🤓

I really think I should make this into a full post of its own. 😅

!ALIVE