Using Hive's Built-in Messaging System To Create An Alterlative To Discord
Hive has a lot of features that get overlooked. In this article we are going to discuss one that might have some possibilities regarding messaging.
This is being written to put forth some ideas along with getting feedback. It would be good to know the technical capabilities and how this could possibly be integrated.
We also can see a use case for HBD as well as HIVE by an application or integration of this sort.
Discord
We all saw articles on Hive, especially by communities, that contain "Join our Discord". There are valid reasons for this since it is a way to communicate information in real time. This is something that Hive is lacking. Is there a way to do this on-chain is the question?
Before getting to that, Discord is a centralized application. Like anything else, one is using that platform with permission. While they do not have the reputation like other social media companies, it is possible for then to pull out the ban button. As with anything centralized, it could turn political at some point. For example, we know that even though cannabis is legal in many states, the banking system ostracizes companies operating in this realm.
Discord has a lot of powerful features which might be beyond the scope of what can be created on Hive. However, is there a way to integrate what is available into a private messaging system with some group/community functions?
If we can do this, online activity will increase while also offering community an easier way to interact with other community members. After all, one of the nice features about Hive is a follower is that no matter which application is used. With Discord, an individual or community has to get people to sign up there also.
This is obviously a valuable service since Microsoft reportedly had a $10 billion interest in Discord.
Messages On Hive
The onset of this thought process started with this:
This is a message that showed up in my transactions on Peakd. It is done by transferring .001 HBD along using the memo feature. Hence, Hive has messaging.
Now we get to the point of where we have to ponder if this could be expanded. Since all of this is on-chain, it is only a matter of reading the information along with filtering it. We know this is possible since Peakd provides that feature.
Could this be integrated into different front ends? Is there a way to set up a community chat feature on Peakd or within something like Leofinance?
Or might this be ideal for a brand new application?
Micro-Transactions
Hive has the ability to conduct micro-transactions. As we see, sending .001 HBD is no problem. This is processed by the blockchain in the same way as one for $100. Without any direct fees, it can take place. Here we have another feature that separates Hive from most other blockchains.
By now it is evident we are looking at a system whereby interaction carries a cost. Unlike Discord which is free to users, this would be a pay as you go. Of course, we also have to bear in mind that .001 HBD is roughly 1/10th of a penny. That means one will have 1,000 transactions for each HBD.
This is likely something not going to affect too many people. Someone posting 50 messages a day will use 1 HBD every 20 days. It is likely that anyone doing on-chain posting will receive that through activity.
Is this something people would use?
Community Feature
As stated, we see most communities set up a Discord where people can ask questions, interact with other members, or bring up issues. Once again, this is taking someone away from where they found the community, a process that is likely to lose some people.
With the system being proposed here, the community could integrate messaging right on its own front end (or within a general app like PeakD). Each transaction with the memo is pulled and posted like a normal message. Of course, most would not see this since the front end would resemble any other messaging application. Simply logging in similar to any other Hive application would allow for engagement.
We also can presume since each transaction is recorded on-chain, the community moderators would be able to pin messages. The application would know where the transaction is located and could be directed there.
Direct Messages
This is a feature that seems easy to build in. In fact, it is the basis of the design at the blockchain level.
The application would simply read the transaction between the two participants. Here, too, we can see what is taking place on-chain. Of course, there might be some messages that people do not want everyone to see.
For this reason, the private/direct message feature requires the memo key (remember that one) to be used and encrypt the messages. Hence, the transaction is seen on-chain but the content of the message cannot be read.
Of course, direct messaging would also require the HBD transfer. However, in this instant, there would be a back and forth. It could end up being a net zero for each participant. The first message sends .001 HBD to the receiver. Upon reply, the same amount is sent back.
In group chat, the application could be coded, if desired, to send the HBD back to the participants, ending up with zero cost. Or it could be used as a profit center to help development of the application.
Commercial Activity For HBD
We recently did a series of what gives HBD value. Those articles were as follows:
We can see how this is incorporating the payment system into the application's operation providing a major use case for HBD. This means that individuals will have a reason to hold some liquid HBD. While the transactions are small, one will need a bit to engage with the messaging platform(s). Yet, the fees won't be so onerous that it will deter many from engaging.
There is an added benefit to this. Each transaction will require the user to have Resource Credits. Here we see how it provides another reason to have HIVE powered up.
At the same time, the application could easy contain a store whereby different products or services are sold. The payment system is already at the base layer and the application is simply expanding the use of it.
Does This Need To be On-Chain?
Many will ask if the messages really need to be on-chain?
Certainly, most of what is posted in these chats isn't worth much in the grand scheme of things. However, this is much more than making group chat immutable.
To start, communities will know their information is always safe. We all know how social media is operating these days. What happens if Discord decides to do a ban run like the other sites? Is it possible for a community to lose the ability to interact with their users?
With a system on Hive, that is impossible. Accounts cannot be closed down and one cannot be stopped from interacting. Thus, all activity ends up on-chain regardless of what anyone else says or does.
Therefore, we are looking at this from the account ownership standpoint. Blockchain is about ownership of data, at least to the degree that it is not controlled by a centralized entity. If Discord does shut down an account, individual or community, all is lost.
What Are Your Thoughts?
Is something like this possible?
It seems like this could be built, either from scratch or integrated into existing applications. The technical aspects seem possible since all activity is on-chain so it is only a matter of filtering the information.
We also will see activity increase. This is an important metric. We can see a way of increasing the number of transactions while extending the "social media offerings" on Hive.
What are your thoughts on this? Would something like this make sense? How would you like to see it designed?
Could this also stimulate other ideas around micro-transactions and how they could be use don Hive?
Let us know in the comment section below.
If you found this article informative, please give an upvote and rehive.
gif by @doze
logo by @st8z
Posted Using LeoFinance Beta
