I think a lot of people are confused about what Hive is, with many conflating the interfaces for the blockchain itself. Because of this, many seem to also misunderstand what it means to be censorship resistant, with people thinking that filtering at the interface level is censorship at the blockchain level.
This is not the case. Once something is written to the Hive blockchain, it is there for good immutably, or at least without a massive amount of consensus needing to be applied to change it, making it highly resistant, but nothing is necessarily impossible. Interfaces however are able to show and hide content in ways they see fit, which is currently done via tags on posts and tags on communities. But, this method is very limited and is prone to abuse of various kinds, including miscategorization of content. But, it also limits the usecase of the Hive blockchain for specific kinds of communities, by limiting the ability to granularly filter content.
Yesterday I proposed a custom JSON interface that would allow for better content management as well as hiding of content. People hear "hiding content" and think it is censorship - this is not the case on Hive, it is for filtering purposes as well as being able to control experience.
Hive is not a blogging site, it is a protocol like the internet itself. What this means is that there has to be the ability to separate content based on what kind of content it is. While a blogging site can essentially be a catchall for content of all kinds, it is untenable if the use case is to for example, have an interface geared for children's content. The ability to filter in and out is part of the requirements and this has to be possible with a high level of precision.
The reason that censorship on the other platforms is an issue is because there is centralized control of the recording medium itself. While we witness the censoring on the platform through various ways of banding, users have no access to what is stored there. This is different on Hive as what is recorded can be retrieved and filtered into a new interface.
For example, imagine if Twitter had an open database and a new platform could call all the content and accounts that they banned, to build a community of the banished. On Hive, that would be possible, where for example an interface could be created to call upon all blacklisted accounts.
What people need to remember is that communities on Hive are centralized, but the blockchain isn't. Splinterlands for example own their interface and the capabilities that their users have when interacting with it. This is the whole point of communities, ownership. This means that people are able to build their unique businesses upon the Hive blockchain, while still being able to control the experience of the user environment and gain the benefits and protections of Hive itself.
The Hive blockchain doesn't care what content it serves and the witnesses don't care which blocks they sign, but users do care what content they are presented and how they can interact with it. For example, at some point there is going to be the ability to subscribe to user contents, which means that a consumer can automatically pay an author. What this means is that content can then segment itself further with some being behind paywalls. To put something behind a paywall on a blockchain whilst still maintaining the benefits of immutability requires being able to hide it except when called upon.
This could be done in several ways and I am not technical enough to do it myself, but for example, an account that paywalls its content could issue a unique key to a subscriber that allows access rights by decrypting the content. If needed, the owner of the paywall would have the control to rescind access also, for example at the end of a subscription period.
This would allow things like Patreon, learning courses and something like Onlyfans or private rooms to be built upon Hive. This gives an account real ownership over their content. It also means that a far wider set of usecases can be built, as a company wouldn't have to trust their content to anyone, as they would always have control, yet still get the immutable benefits, with even decentralized video hosting starting to be developed on Hive through @threespeak
This isn't censorship, it is the expansion of censor-resistance as it lowers the reliance on others to serve information. Build the tools, optionality and template these interfaces and any half-competent user would be able to build an interface for themselves. These could then for example be housed in a larger interface that aggregates them. This means that a user would be able to appear on a specific platform, but still maintain absolute control of their content and even monetization. Because of the possibilities of Hive, a user would be able to break their "channel" away from the aggregator by rescinding rights and still maintain their fanbase through various structures without having to start from scratch. This is impossible on YouTube because "Your Channel" is actually Their Channel, and "Your Fans" are Their Users and they can flick off the switch at any time and there is very little that can be done, other than complain.
If for example, Twitter worked like Hive, the banning of Trump on Twitter wouldn't shut down his account, it would just stop it appearing on their interface. If Trump actually owned the account and all of his followers also owned their accounts, they could simply and quickly build a new interface that looks exactly like Twitter and grant access to everyone who wants it. But, no one owns their Twitter account, which means they don't own the content on there either. If Twitter wants to delete it, they can and it is within their rights to do so because they own their business.
Hive's position as censorship resistant doesn't mean that everything built on Hive has to appear everywhere, it means that there is protection for it from being washed away. It means that it can be recalled now or at any time in the future and with a little more development, it would be possible to extend the ownership model for content, communities and accounts even further.
We are in the early stages of moving from Web 2.0 to 3.0 and a lot of development and consideration needs to take place to underpin and secure it. Hive as a protocol is much like the protocols of the internet itself, where while everyone can have access, what they have access to is segmented based on many variables, including location, age and ability to pay. Hive can support thousands of business models and millions of users, but in order to do so, it has to be customizable to support content segmentation. This doesn't encroach on the fundamentals of recording to the blockchain for immutability, it affects the second-layer functionality and user experience.
Pretty much, all front ends everywhere are centralized, as they are managed by particular people and groups who do things like, pay for the server hosting. What I find interesting is how many people believe they have a right to be on any platform at all. However, the Hive blockchain is not owned by a single user or group, it is owned by all users and even someone without any stake can build for and connect a platform to it, populating it with whatever they choose - while the blockchain below keeps on recording and protecting everything written to it.
The core reason that censorship happens is because we put the power to decide what is seen in the hands of others, rather than take ownership of it ourselves. How you manage your account, is your business.
Taraz
[ Gen1: Hive ]
After reading your post twice, and certain lines a few more times, I do believe I get the big picture and it seems to revolve around this line
(Hive can support thousands of business models and millions of users, but in order to do so, it has to be customizable to support content segmentation. )
Content segmentation as you explain is not censorship, but rather another way to hone in on what interests a person may have.
(This doesn't encroach on the fundamentals of recording to the blockchain for immutability, it affects the second-layer functionality and user experience.)
Ideas and implementation of interfaces, even to a greater degree than is presently done through communities, can only increase the ways the #hive blockchain can be utilized and in turn increase subscriber growth.
When it comes to all technical and development stuff I'm lost more often than not.
But, I do know one thing, it's people like yourself that have visions about #hive's future that is so exciting.
Yes. While people focus on narrow parts of it like censorship, there is also the bigger picture of usecase and functionality. Sometimes it is a tradeoff in certain areas, but on Hive at least, the blockchain is faithful to the content.
I wish I had the skills to code or have a team of coders at my disposal, as I think there are so many areas of opportunity that we need hundreds of dev teams.
Good points. If I'm reading it right, this is what we are missing that makes me want to use dapps like D.buzz. I don't want my Peakd stream filled with micro content. I would love to have a Twitter like experience on here, but it needs to be filtered to only show on D.buzz.
I really hope this is quickly addressed.
If I'm wishing for things I'm never going to be able to help with, I also think there needs to be some privacy options with concern to wallets.
I think that this has to be addressed in some way also, especially if price increases heavily. While I like the idea of transparency, I am not sure if it is useful having full transparency on everything immediately. Unfortunately, we still live in a world with a great deal of violence and very little nuance.
Exactly. It will absolutely deter some people.
Posted using Dapplr
didn't try to use it but i think you can eliminate d.buzz from your peakd feed.
d.buzz is a community hive-193084 so if you go to settings/content you have an option to "Hide posts with a specific tag or category from your following feed"
i did not use it, and i don't see a lot of d.buzz on my feed, maybe i will test it out, but in theory if you put "hive-193084" you should not see d.buzz on your peakd feed.
Immutability serves no purpose for private content behind paywalls. It's just an unnecessary technical limitation in that case. Immutability is needed to create trust where it otherwise couldn't exist and where it is needed, which would be the public sphere verifiability may be necessary such as is in the case of cryptocurrency.
Some content might benefit, some might not. However, the option to choose show and hide might be placed in both, where for example content would be time released after a period.
great write up, I'm starting to understand what web 3 is all about..
It is such a beast that it is hard to get a handle on, but hopefully I can be at least part of a bridge in some cases. It is difficult for me also and it is constantly advancing.
HIVE!D
Fantastic article!
Been Minding My Own BzzzNess on the block for 4 years now!
My 4 year anniversary is this month :)
Very good article on censorship, community management, and ownership. 😎 👏 👏
Cheers :)
I have to slowly reread and think about this post.
Yes or no?
That isn't really a suitable question, but just wondering what your thoughts are :)
Well said. I particularly like the taking ownership aspect. I think we've been so conditioned to have centralized power over us and tell us what to do that this concept is uncomfortable for some.
Posted using Dapplr
It is uncomfortable because we have traded ownership for convenience. We are starting to see the real cost of the trade, but most of us aren't in the condition for taking back control.
That was a worthwhile and interesting read providing clarity over what Hive’s immutable nature really means and how it could be engineered for other uses. Cheers for sharing
You are very welcome. Occacionally what I write has some value :)
I think the Hive blockchain is much more than a blogging chain, using the custom JSON we could do a lot of things on the chain and it will not disrupt the normal blogging experience.
I don't know enough to think through all the options, but I believe that a lot of innovative development could take place if the focus shifted to the second layer.
Excellent points, well my own issues with HIVE, is that it's transparency level is so high. I really wish they can work on that.
What would you like hidden?
Too me, a little privacy in one's wallet. I think someone mentioned that. Hive is expanding and some policies but friendly needs to be implemented for a better blogging/block chain.
#HIVEON.
Thanks for sharing
Awesome way of explaining everything in high details. I think this should reach to all the newbies and anyone who hears about the hive Blockchain but is not sure what it can offer.
I also learned some new things which I had no idea about, so I consider a well time spent reading your post and I'm happy I stopped by :)
I think your tagline should be "What I find interesting is..." XD
Hahaha.
I have tried to get out of the habit, but it is too strong in me. Like the dark side of the force.