Building in the Quiet

I’ve gone a little quiet this week on this blog of mine, but I promise you it’s for good reasons. The team and I have been hard at work, and I’m sure most of you will welcome the updates we’re about to release with open arms.

The truth is, if you had told me months ago — when I began helping Hive account@eddiespino with Hive account@threespeak — that we’d be here today, I wouldn’t have believed you. As a matter of fact, sometimes it still doesn’t feel real to me.

On top of the work we’re doing for Hive account@threespeak, my older brother and I are also cooking up something pretty awesome. I won’t say too much for now, but it might be enough to say this is the hardest project I’ve ever tried to tackle — and it might be the same for him. The amount of complexity, the edge cases, and just the sheer number of things to consider feels overwhelming at times. It requires me to take steps back — way back — just to make sure I don’t lose sight of the big picture.

At any rate, I hope that soon my brother will join me on a call — maybe a Sunday with the boys — and we can present what we’ve been building. I’ve said countless times at this point that Hive is not only blogs. That was just the use case that started the show. This technology can be leveraged to build almost anything that exists on Web2, and I hope our work helps convince you that this is true.

I’m doing my best to curate Hive account@snapie snaps. I want to remind all my snaperino friends that it’s precisely when prices are this low that accumulating stake becomes the easiest. And I can promise this: as long as I see people being genuine with their snaps, their shorts, and their comments, I’ll be supporting them in return.

On the development front, I shared a few days ago that I changed the algorithm of the Encoder Gateway. Ideally, this will bring a more decentralized ecosystem to 3Speak — and that is awesome. Exciting. Yet yesterday I began thinking about how challenging all these changes have been. It’s not easy to coordinate with everyone when a code update needs to happen, so I had an idea.

Today, while squashing some bugs on the Encoder Gateway, I also began implementing a versioning system. The idea is that Encoders will now get notified — right on their dashboards — when new updates are available and/or required. This way, I don’t have to tag people or send direct messages about changes.

I don’t expect much more to change regarding the Encoder’s core code… but then again, I’ve said that before.

And here we are.

MenO