Database of ad timestamps like sponsorblock only works if ads happens at the same timestamps (and are of equal length). This is not necessarily the case.
The only reliable way I can come up with is a database of ads to look for, but that can be huge to accommodate for all possible ads. There’s also risk of false positives (risk of skipping video when there are no ad).
I’m not sure if a sponsorblock like solution will work. Sponsorblock is entirely reliant on timestamps provided by users.
A similar solution for YouTube’s ads will only work if the ads always happen at the same timestamps and have the same length. This is not necessarily the case, as ads can happen at any point.
They don’t need to do any extra transcoding. It’s not that costly to stitch videos together. If done at specific strategic locations, it’s like copying a text file into another.
It’s maybe doable, but figuring out where ads start and end in a video file isn’t necessarily trivial. The app must know what to look for, and YouTube might try to obfuscate it to make it harder.
That’s the point. They want to stop people bypassing ads by using alternative front ends. If they succeed with server side ads, then it’s going to be difficult to block ads. Maybe not impossible, but difficult.
Bitcoin transactions are public. Anyone can view your transaction history if they know your wallet address. It’s not a good option for privacy.
Also, it’s not true that it hasn’t seen downtime. It has happened at least once in its early days due to a bug. Also, there has been many times where it taken more than an hour between blocks. This is more to its probabilistic nature.
And maybe withdrawing so late might not be as bad after all. Sure, it’s going to be tough for dems to rework their campaign, but it’s going to be tough for reps as well when their campaign revolved around Biden.
Even if a fix was discovered quickly it wouldn’t prevent the problem that it must be manually fixed on each computer. In this case a fix was discovered quickly even without access to source code.
Just having more eyes on the source code won’t do much. To discover errors like these the program must be properly tested on actual devices. This part obviously went wrong on Crowdstrike’s side. Making the code open source won’t necessarily fix this. People aren’t going to voluntarily try every cutting edge patch on their devices before it goes live.
I also doubt any of the forks would get much traction. IT departments aren’t going to jump to the next random fork, especially when the code has kernel access. If we can’t trust Crowdstrike, how can we trust new randos?
I doubt it. Few people are volunteering their time reading pull requests of random repos. It probably went fast from pull request to deployment, so there would be no time for anyone external to read.
The only thing open source would’ve done is to give us a faster explanation of why it happened after the fact.
I like when videos are as direct as this guy’s. Just straight to the point. No extra fluff, distracting skits or drama. It’s just him talking straight to the camera about things he’s passionate about.
I have a dislike for them. Especially in recent years. There was a time I thought they were the cool hip company with lots of cool innovations. When Google docs launched it was so revolutionary that two people could work with the same document at the same time.
Now I see them more for what they are: an advertisement provider. They’re only after our data. Once I realized that my dislike for them grew.
But my dislike for them hasn’t been enough to stop using their products. I’ve tried DDG a few times, but I’ve always been dissatisfied with their results.
I’m afraid this is what they’re going for.