Case for Disappearing Content on HIVE, 3Speak, BLURT and Microblogging

avatar

Impossible to censor is one of the most important things about HIVE and project built around it. It is possible for various front ends to enforce censorship due to various reasons. @penguinpablo's blog on Steemit is one such example. Even though you cannot see his content providing valuable statistics about HIVE and STEEM (that clearly show HIVE doing better than the blockchain it forked from), they are still part of STEM. You have to be more technically proficient than the average web suffer to access them.

Steemit.png

Some front ends decide not to take part in censorship. This was the case with SteemPeak. Now they are not supporting browsing STEEM blockchain. The old content + new content is well preserved on HIVE anyways.

SteemPeak.png

What If You Don't Need Forever

One size fits all solutions are usually very bad solutions. Imagine there were only ships for traveling across oceans. Imagine there were only planes flying over the seas. Cargo is better transported on ships and planes offer a better way to carry passengers. There is no need to preserve every little thing!

Timers and/or Epochs

I see two ways to create transitory content on HIVE, @threespeak and even BLURT. You can have a timer similar to the ones already used in messaging applications such as Telegram, Signal etc. The content will be pruned from the blockchain after a set amount of time.

The other methods is a way to have wild conversations happening around for a short period of time (be it a day, few hours or a month) and have all the conversations deleted at the end of the period. Think of all the Threads that are created. Imagine you could discuss anything without the embarrassment of having everything you type stored forever. You can make mistakes or even share certain private details without having to worry about having them stored forever. Eg: sharing a wallet address.

Cheaper For Block Producers

I see this as a very important detail. Pruning data from a blockchain like Dash designed to act as Digital Cash can be great for privacy. Social media blockchains do not have such luxuries. Content disappearing would go against the whole selling point of HIVE, BLURT, 3Speak etc. Thus we have to sell a new type of posting on blockchain. These Timers and/or Epochs can be a part of Communities or have a similar setup. Epochs can especially be used to quickly create a space for things like AMAs right on blockchain.

Be Efficient With Storage

Efficiently allows to do more with less. If HIVE, BLURT, 3Speak etc. can be run at a low cost, it will make the entire system more antifragile. It will bring better profits to block producers. It will remove at least some of the content that may not have much use preserving for long. How important is a random chat? I would not mind if it was gone. In some cases, the disappearing could be the preferred choice.

What we need here is the ability to opt in. These posts could still earn from the reward pool. They could even be made to have a separate Token although I would consider it adding too much complexity without much of a gain. Ultimately it is upto the blockchain developers to implement these ideas. I'm not a programmer. What I can do is suggest ideas.

Happy Hiving!

Posted Using LeoFinance Beta



0
0
0.000
7 comments
avatar

I guess this is against HIVE/blockchain rules.

Also, a frontend can intentionally hide a post/comment as a feature, but other new dapps can unintentionally show unless it is stored as a special json instead of a post/comment.

0
0
0.000
avatar

As I know it, the blockchain stores the data and it will be up to the front-ends to show that data. If they wish to mute (hide) users on front-ends, they can do so already. It doesn't change the fact that this data is still stored onto the blockchain.

Posted Using LeoFinance Beta

0
0
0.000
avatar

Yes, that's how blockchains should theoretically work.

0
0
0.000
avatar

Thanks for your contribution to the STEMsocial community. Feel free to join us on discord to get to know the rest of us!

Please consider delegating to the @stemsocial account (85% of the curation rewards are returned).

You may also include @stemsocial as a beneficiary of the rewards of this post to get a stronger support. 
 

0
0
0.000
avatar

Congratulations @vimukthi! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s):

You distributed more than 46000 upvotes.
Your next target is to reach 47000 upvotes.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

To support your work, I also upvoted your post!

Check out the last post from @hivebuzz:

The Hive community is in mourning. Farewell @erikasue!
0
0
0.000
avatar

There is use in knowing the historical data but I do agree that there is some redundant stuff that is left better to some application rather than a blog post. However, I just don't think it fits what Hive is because it's going to store all the transactions that happened. It might be possible for certain applications to do things centrally on their server and push things after the fact onto Hive but I don't agree with deleting the data.

Posted Using LeoFinance Beta

0
0
0.000