![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
The problem with (good) hashes is that when you change the input even slightly (maybe a different compression algorithm is used), the hash changes drastically
The problem with (good) hashes is that when you change the input even slightly (maybe a different compression algorithm is used), the hash changes drastically
It’s fixed because we said so!
Same… dreaming about calculating limits and integrals is pretty exhausting. Playing minecraft in your dreams is more fun :D
To be honest, some of the solutions were quite good. But I still don’t recommend it. Toilet debugging is better :D
I’m probably not a lucid dreamer, but at times when I write code all day long I may also dream about it at night. Sometimes, I would wake up in the middle of the night and write an “amazing solution” down so I can implement it the next day. Not surprisingly, most of the “amazing solutions” are total nonsense.
Edit: If this happens to you, it’s probably a sign that you code way too much. I know it might be difficult, but try to relax more please.
“Why are you making mistakes? Just don’t make them!” - my German teacher
Like… yeah, thanks, that’s very helpful! Why didn’t I think of that?!
I think that downsizing the scene to like 8x8 pixels (so basically taking the average color of multiple sections of the scene) would mostly work. In order to be undetected, the ad would have to match (at least be close to) the average color of each section, which would be difficult in my opinion: you would need to alter each ad for each video timestamp individually.