Some of you might already know this, but I’ve also been sharing these updates on YouTube. I see it as a smart way to both keep the Hive community in the loop and give the wider world a glimpse into what’s actually happening here on Hive — beyond the usual noise.
If you want to help me grow my (still very humble) YouTube account, the mirror is here:
Thanks to reports from a few of you, I’ve identified and fixed some additional edge cases. The Encoder code has been updated accordingly.
I’m currently running the new version on my own encoder. So far, so good — but since there was a bit of refactoring involved, I’m giving it some time to make sure nothing unexpectedly topples over (hence the Jenga reference).
Once I’m confident everything is stable, I’ll give the green light for everyone to do a git pull.
This one is done — or at least, I think it is.
I’ve been running tests, and within a day or two I’ll point the Snapie Encoder to start working with it directly. After that, we’ll gradually transition more encoders to use it, and by extension, the Hot Node.
Eddie has already set up an additional pull zone for the Hot Node, so from the player’s perspective, the switch in video hosting should be completely transparent — no speed regressions, no funny business.
This is also shaping up nicely. I’ll report more on it in the coming days, but in theory, Hot Nodes — just like Encoders — can be run by community members.
The main requirements are:
-Fast internet
-A public IP
The Traffic Director will handle load balancing, so even smaller nodes with limited storage should still be able to contribute meaningfully without getting overwhelmed.
Once I’m fully comfortable with the testing, I’ll publish a dedicated post explaining how to set one up. I’ll also provide scripts to make installation as painless as possible.
Much love ❤️
– MenO
▶️ 3Speak
