How Not to Handle Your Drafts!

in #hive21 days ago

Greetings, everyone!

One of the very important features of Web3 is that users do not rely on a single interface to access their content, which is very valuable when the server is compromised or under attack. With HIVE we have a broad landscape of user interfaces, and we all benefit from this competitive environment.

As an example from today, with InLeo down and little news from the official Discord channel, our experience continues to be unaltered and I'm writing this post from Peakd. At the same time, I interface with people via comments with Ecency.

All great, until I realized that our draft articles are not stored on the chain, but as part of the user interface. I have a few articles in work via InLeo and I am concerned, as some heavy work went into one of them.

How was this going under the radar of our community? A good practice would have been to store them on the chain, encrypted with the user Memo key. What do you think? Can we push this idea to the developers of the major interfaces to HIVE?

image.png

Sort:  

I draft in PeakD because it's up most of the time and copy over to LEO when I need to post.

Peakd is indeed impressive. Very high-quality services, and always interesting features are added all the time.