Decentralized Videos - Finding the Sweet Spot
This blog might be a little too techie for some, but I want to write these ideas down anyway—if for no one else, then at least for myself. I’m still trying to figure out the right tune-up for 3Speak’s infrastructure.
On one hand, it makes perfect sense to prioritize hot videos—the ones living inside that seven-day window. But I keep wondering if maybe they should stay hot a little longer.
Ideally, once I finish making the Hotnode service easy to use—plug-and-play, even—other members of the community would start running them. If that happens, we’d end up with a hefty decentralized buffer between the hot nodes hosting new videos and the cold storage we call the Supernode.
The more hot nodes that exist, the smaller each one can be. Smaller nodes are faster nodes. That logic holds… provided those nodes are set up with proper peering and can communicate directly with the main hot node that actually delivers videos to users.
And this is where I start feeling torn...
I could use clusters, but that adds complexity and makes installation harder for the average user. That’s friction, and friction kills adoption.
Another unresolved decision is whether hot nodes should be able to connect directly to the traffic director. Right now, the only living hot node is in constant communication—but setting that up required my direct involvement. In a perfect world, a community hot node would simply perform a handshake with the traffic director, present its health endpoint and upload path, and immediately get to work.
But that opens a whole can of worms.
A bad actor could spin up a hot node, accept uploads, and then quietly delete them. If this happens before the videos are migrated to cold storage, that content is gone. Forever. That’s real damage, not theoretical damage.
So it makes sense to vet the nodes that are allowed to host videos—even if they only hold them for seven days or so. But this is the crux of the problem: vetting introduces centralization.
One idea I’ve been considering is forcing community hot nodes to migrate content immediately. In theory, that would prevent premature deletions. In practice… a determined bad actor could still do harm if they really wanted to.
If you’re wondering why I keep thinking about bad actors, it’s probably because you haven’t looked closely at the muted accounts in the comment sections lately.
So, for now, we compromise.
There’s still a discovery phase ahead. I suspect the correct parameters for hot nodes will reveal themselves over time, through usage and iteration. But at least for now, all hot nodes will need to be approved by us.
Not because we want centralization—
but because losing videos is worse.
MenO
We should call Dhf Dirty Hive Fund 😂😂😂😂😂😂😂😂😂😂☝🏾☝🏾☝🏾
Then we have Posh Proof Of Scam On Hive 😂
Then we have Buildawhale farm 😂😂😂
And much more 😂😂😂😂😂
Hello everyone good morning good afternoon good evening where are you are around the world 🌎 🌎 🌍
As many people have seen I've been called a spammer on Hive for sharing the truth about my situation
They can call me a spammer and downvote me as much as they like it changes nothing I bring you the truth take a look at everything I've shared and I've still got a whole lot more
So to you seriously stupid people just leave me alone and now you will need to bring my rep back as acidyo decided to take it away with the help of blocktrades delegations 🤔
Hive is dying and if nothing changes it won't just be dieing it will be dead 😂
Feel free to use anything i share in this post
@crimsonclad please do your job 🙏🏾
https://hive.blog/hive-135178/@crimsonclad/re-kgakakillerg-sxllhv
https://hive.blog/hive-148441/@hivewatchers/svftu9
https://hive.blog/hive-148441/@hivewatchers/svdjjz
https://hive.blog/hive-176853/@steevc/re-kgakakillerg-syyy4x
https://hive.blog/dev/@howo/re-kgakakillerg-szhax7
https://hive.blog/hive/@steevc/follow-friday-respect
https://hive.blog/hive-127022/@shmoogleosukami/re-kgakakillerg-t0hcxc
It's unbelievable that they downvoted this Goodbye Auntie R.I.P 🙏🏾
Comments being downvoted by blocktrades https://hive.blog/hive-170744/@kgakakillerg/t0ns3b
https://hive.blog/hive-127466/@steevc/re-blocktrades-t0kint
https://hive.blog/hive-127466/@blocktrades/t0lq41
https://hive.blog/hive/@ureka.stats/the-untrending-report-hive-downvote-analysis-2025-06-29-20250629143829
https://hive.blog/hive-127466/@kgakakillerg/t0m1vn
https://hive.blog/hive-108278/@kgakakillerg/t0rfo8
https://hive.blog/hive-127466/@kgakakillerg/t0vcl7
Stop farming Hive https://hive.blog/burnpost/@buildawhale/re-1756307402814502169-20250827t151240z
😂😂😂😂😂
📊 The Untrending Report - Hive Downvote Analysis - 2025-09-07
RE: Understanding Pointers in C Programming
Please Peakd, allow me to completely block spammers (Would you ever vote for this?) thanks for exposing yourself more @makerhacks
Please go through it all instead of calling it spam 😂😂😂😂🤣🤣🤣🤣🤣🤣🤣
https://blurt.blog/hive/@candy49/5slvnx-taskmaster4450-is-being-downvoted-on-hive-by-you-know-who
🚨🚨🚨🚨🚨🚨🚨🙄🙄🙄🙄🚨🚨🚨🚨
https://hive.blog/hive-108278/@kgakakillerg/themarkymark
https://hive.blog/hive-178138/@thefed/t6q9kb 🙄🙄🙄🙄🙄🙄🙄🚨🚨🚨🚨🚨🚨🚨🚨🙄🙄🙄🙄🙄
https://hive.blog/music/@geneeverett33/11-25-25-three-tune-tuesday-picking-tunes-from-the-punk-band-the-descendents-1982-1997-era
🚨🚨🚨🙄🙄🙄🙄🙄🙄🙄🚨🚨🚨🚨🚨
https://hive.blog/dmania/@steemcleaners/ps46kb
https://hive.blog/hive-124838/@fjworld/re-peaksnaps-t7161i
🚨🚨🚨🚨🙄🙄🙄🙄🙄🙄🙄🙄🙄🚨🚨🚨🚨
https://blurt.blog/blurt-131902/@condividisulweb/3w94e8-hive-manipulation-censorship-and-suspicious-funds-the-hidden-truth
🚨🚨🚨🚨🙄🙄🙄🙄🚨🚨🚨
https://hive.blog/hive/@kgakakillerg/i-ve-been-put-on-two-blacklists
Thank you for reading and viewing this post
To all the downvoters on Hive When the downvotes stop 🛑 and my rep is back I stop sharing the truth 🙏🏾
An interesting conundrum ! I've got a thought, but I'll add my normal caveat that I'm not a coder, so I'm thinking of this from a logic and business structure perspective.
Would it be possible for several (or even many) nodes to hold new videos in hot storage, with one being selected at random to be the primary that actually displays it. Possibly rotated over time to spread the load (and any potential reward payments issued).
Then, there could be communication between nodes just confirming which videos each had, which could act as an audit trail to spot if a bad actor has deleted a video without authorisation. Each hot node could then be set to send a video to cold storage if it hadn't received any views (or viewer numbers over a set threshold) for 7 days. This means that the number of nodes containing a video would diminish over time, but could allow a more popular video to be available for longer.
When sending a video to storage, the cold storage supernode would confirm receipt (and check file size to ensure it's got the complete video), sending the info to all the hot nodes with that video to confirm the total number now "in the wild", again acting as an audit trail. I don't know if it would be possible to build in some kind of "fingerprint check" to ensure the validity of the video received, but at the very least if the cold storage was receiving multiple copies of the same video over time, it would be able to compare them and keep the one most likely to be accurate (possibly using audit trail scores over time to determine which hot nodes are seen as most reliable.
Writing it down makes it seem far more complex than it was when the idea popped into my head, and I appreciate it creates quite a lot of back and forth communication and verification. But maybe in the mess I've just made you might find an idea that can actually be coded in a realistic way !
I like the way you think... this is complex, but its very good!
Thank you ! Not bad when you consider that the only code I've ever written in my life was a little bit back in 1981, in Basic using a Sinclair ZX-81 😁
https://x.com/i/status/2020579060058087836
#hive #posh