D.Buzz Bi-Weekly Development Update Report Vol.25 : lots of updates, looking at the stars
Hello Developers and D.Buzz Users.
You may have noticed that we didn't post a development update last week (*Last one was 14 days ago HERE ) , this is because we're shifting from a one-week Sprint cycle into a two-week Sprint cycle.
We did this because we were drinking too much Red Bull, literary... and ... By drinking too much Red Bull we mean working too many long hours to get a weekly development out. With a two-week development sprint cycle we can now focus on providing better and more consistent updates, while honoring our developers and giving them time to recover. (* Hey D.Buzz Dev Team, WE LOVE YOU 😍 ).
Let's talk shop, what got done.
- We completely fixed the iPhone image upload bug which was super tricky and took A LOT longer than expected, and for more than one reason, but it's finally done. It's been pushed to Next.D.Buzz and D.Buzz already so it's live.
With this Bug Squashed and Feature Enabled,
It's Time to Talk about Marketing 👍
It's Time to Talk about Marketing 👍
- This bug was the main thing that blocked us from starting a marketing campaign, due to the fact that a lot of people do use iPhones, and we want to onboard them as well as Android users. ( Here's a great bit of statistical data on how many Iphone and Android users there are HERE ).
Our marketing efforts are slated to kick off at the end of December, bearing no crazy other upsets. We are shooting for the stars with the marketing initiative. Our goal is to onboard 1,000 - 3,000 users to D.Buzz by March 31, 2021. Let us say this again.
We want to onboard 1,000 - 3,000 new users to D.Buzz by March 31, 2021.
We also added other features in the last several weeks.
PeakD's Beacon service was integrated w/D.Buzz last week, so that our platform will choose the best Public API's, and if the one we are using goes down, it should switch to a better one automatically, this will increase uptime & reduce to eliminate downtime caused by Public API's.
Our Lead Devs took 2 days off, after having worked almost every day (minus sick days) since the start of development for D.Buzz 3.0, and starting in January, we will implement a mandatory day off for our Lead Devs, so that they will be REQUIRED to take a day off. (really Devs we love you, but you work too much, rest is important)
We onboarded a new part-time dev who has been working in the background for 4 weeks getting familiar with HIVE development, and will help increase the rate of releases + updates in the future.
We'll have more news about additional hires in Q1 of 2021, and are growing, step by step, with a strong foundation but, more so building momentum.
What's coming in the next 2 weeks
Targeted for Release/Updates by Dec. 30th, 2020
Fix Search / Hashtag Hyperlink feature.
Change post failure for low RC's to a more descriptive error message.
Add Comment (a.k.a. Buzz's) Viewing on D.Buzz
Enable "," and spacebar closing of tags.
Automatic Delegator for D.Buzz users who signed up for our website & are low on RC's.
Buzz widget (button) that can be embedded to other websites, similar to Twitter's Tweet button, that enables users from 3rd party websites to Buzz that site to D.Buzz
Link shortener using the D.Buzz domain.
8 Developing an in-house marketing team to help with the upcoming marketing push to start January 1, 2021.
(* Note : many of the features listed above are nearly completed, they were just delayed due to the complexity of the iPhone issue).
- What do you think of these updates and developments?
- Are you excited about them?
- How can we improve and be better?
Thank you for being with us on this journey, we have endless gratitude for all the support you have given.
Over and out.
D.Buzz is ...
Is a censorship-resistant short form microblogging platform that empowers you to share your thoughts in 280 characters or less.
Censorship resistant and built for the community with love.
We strive to have a fun and neutral stance on topics. If you have any concerns with the content, please contact @jacuzzi, who writes and generates the content for our articles, or the @dbuzz team for clarification.