Weekly update on progress and growth.

Hello D.Buzz development enthusiasts!

It has been a good week for D.Buzz development and future development planning! While we did not roll out any big news, we have counted on our progress forward.

One issue that is coming up with the new video feature is that on other front ends, the video does not show and only a link is presented. This we find unacceptable and we are working on fixing it.

The solution we are developing for this is, that when a user uploads a video to D.Buzz, we generate a thumbnail of that video by capturing the 1st frame. We then add that image to the buzz and place a graphic on top that says "Click here to view this video on D.Buzz".

This way, when the buzz is viewed on the other frontends, the viewer will see the buzz text and an image of the video with instructions to go to D.Buzz to view that video.

When the Buzz is viewed on D.Buzz, we will link the image hash on the backend to the video file and swap out the Image for the video. This way, you will see the video on D.Buzz as it should be, but on the other frontends, you will see a clickable image and a link to D.Buzz to view that video. Hence, a more quality experience across all of Hive.

We also talked about developing a custom API that other frontends can implement and use to view the videos. However, as Hive grows, more and more services and frontends arrive. We can not ask all of them to embed our code for video viewing. As such, this solution just seemed to make more sense.

What are your thoughts on this solution? Do you like it? Do you have another method that would be better?

Progress on Hive Authentication Services (HAS)

We have sorted out the main bug we had last week and fixed the issue of automatic connection drop when using the Hive authentication client. At the moment, we are finishing some remaining operations using custom operations on HAC module.

With some good luck on our side, this should be the last hurdle we have to jump over before we can start to roll this out to the D.Buzz testnet.

Other Update and Notes

We have also worked on making a new branch in GitHub for D.Buzz to help roll out updates quicker and provide a more efficient work environment on the backend for our developers.

Lastly, a D.Buzz token. We spent some time talking about this, what it could be and how we could distribute it to the community based on D.Buzz use and posts, but we have not set any hard direction on this. We started to develop a white paper for it. If all goes well, this token will be the backbone for the future D.Buzz service and growth. So, stay tuned for more information about this.

Want to work with D.Buzz?

We are looking for a content writer and are always looking for developers that could fit in with our team. Send us a message on Discord or Matrix if you want to talk more about this.

Till next time.

- The D.Buzz

D.Buzz Online At:

				-