Anyone who has engaged in Threadcasts has seen the value of them.
As mentioned in a recent article, 
It is also encouraging to see the weekly Leofinance AMA utilizing a Threadcast. This is a great way to engage with Khal during the show, asking questions which he addresses on air.
The CTT show also had a Threadcast each of the last couple weeks. This is also encouraging have them supporting LeoThreads. People are incentivized by them as they go through with upvotes for those participating.
These are just a few examples of what is taking place. It is a good start but only that.
We need to get creative with our thinking.
Here is a comment that the aforementioned Jimmy left on my last post:
His ideas are valid. Let us consider all the different activities that Threadcasts can be developed for:
The point is we have a great deal of versatility with these. It is something that can stand out and bring users to LeoThreads. Perhaps it can evolve into something more depending upon development of the platform. For now, it can be an adjunct to live broadcasts of some type.
Anything that people are interested in can use Threadcasts.
This could be tied to gaming. Many like to stream their gaming activities which can be augmented by a Threadcast. We also could utilize platforms such as VIMM for the streaming.
Of course, right now anyone can set one up and share it with others.
If we want to take this to another level, the application could implement a Threadcast schedule. This will be similar to the guide on our cable system, alerting us to what is coming up.
The feature would look something like this:
For example, do you know if there are any Los Angeles Charger fans on LeoThreads? As the user base grows, it is hard to know what people are into.
If I am a fan of this team, perhaps I schedule a Threadcast for the Thursday night telecast. If it is up there a day or two early, others can go through the schedule.
What if another fan or two see the Threadcast on the schedule? Now there is the ability to people to get "together" when watching the game. In this situation, there are a few people "conversing" about their favorite team. Of course, if they are playing the Raiders, perhaps a could of those fans join in too.
The idea is to create this feature as a centerpoint of LeoThreads. At the same time, it will help to increase the amount of engagement taking place on LeoThreads.
To me, the future success of LeoThreads comes down to activity. This is actually true for all of Hive. We are committed to microblogging on the blockchain. However, just claiming to offer this is not enough.
We have to create things that differentiate LeoThreads from Twitter. While this could be done on Twitter, it is really overlooked. They do have AMAs, something we can neatly house in Threadcasts.
As stated in the last post, imagine a dozen Threadcasts per day with 8-10 people in them (at a minimum). How much activity would that generate?
The key is the simplicity of this. It is a rather basic idea that is easy to implement. Hence, when it comes to programming, it only requires setting up a schedule feature in the user interfact. This could even be tied to a calendar to make it more visually appealing.
How often do we want to follow a broadcast of a show, only to have to hunt for the links to the show? Here is another benefit of having a Threadcast. The links to YouTube, Twitter, VIMM, Facebook, or wherever it is being broadcast could be dropped in there.
It becomes a self contained repository for that particiular event.
If you do some scouting around different sports blogs, the ones that have a comment section can get thousands during a game. This is something that I can envision happening on LeoThreads with Threadcasts. If two people can put up 125-150 threads during a baseball game, imagine what 10-15 can do.
At this point, it makes sense to me to incorporate this into the frontend and make it a central feature that people can utilize.
What are your thoughts on it? Let us know in the comment section.
If you found this article informative, please give an upvote and rehive.
gif by 
logo by 
