It's hard to get that point because you're conflating two different stories.
Folks around here are generally uneasy about tracking in general too, but remove big brother monitoring from Safe Browsing and this story could still be the same: whole domain blacklisted by Google, only due to manual reporting instead.
"Oh, but a human reviewer would've known `*.statichost.eu` isn't managed by us"—not in a lot of cases, not really.
Sure, and sorry for being so unclear. The point of my post was meant to be a) Google has this enormous cannon, is this "right"? And b) they will use it to kill anything bigger than a mosquito.
But you're right, complaining about big tech surveillance didn't help with making that point at all.
> But you're right, complaining about big tech surveillance didn't help with making that point at all.
I disagree. Everyone with a brain is thinking it. Its important to address what your audience may be thinking especially given the other factors in this which I've mentioned in other responses related to gross negligence.
Technical capability exists to narrowly define blacklists, and they chose a gross negligence route (baby with bathwater), without providing notice.
I was wondering that too. It’s an impressive demo when used on devices with low latency audio drivers but I’m not convinced there’s any ability to detect drift beyond this. Might be interesting to have an option to use microphones to detect and calibrate this… …but then you have the same issue of an unknown delay on the microphone input too.
Even still, both repos had READMEs [1][2] clearly meant to be read by the public. The archival was only successful years ago, with a failed snapshot as far back as 2021 [3]. This really seems like they forgot it was ever public.
Now, this is only about it being a GitHub breach. Whether unlicensed (emenel/portfolio) or GPL (emenel/dust) code should be allowed in such datasets is a different matter.
That would be a most charitable interpretation. By that logic You and Florida Man: would also be it's 'best series' since they all clocked in higher than Shadow and Bone quite a few times.
If we honestly talking about their best performing properties we are talking about the likes of Squid Game, Stranger Things, Wednesday, Dahmer, Bridgerton, Money Heist, The Night Agent, The Queen's Gambit, Lupin and The Witcher S1.
Lupin and The Witcher S1 (and Wednesday to a lesser degree) were average adaptations of good stories. The only thing nice in the Witcher was the casting, and Lupin had great initial ideas (like the casting, too), but overall it was very average. Shadow and bones was an average adaptation of an average story.
Not to knock on Sunvox or NightRadio (both awesome!), but that effect only exists in the video. It doesn't happen when playing the demo song on the software, and they confirmed it was made with a video editor [1].
How does one move with the mouse? I could only find gestures for rotation and zoom; for movement I had to resort to manually entering coordinates in the settings.
This only happens in "proper" tables. When you add a formula to a table column, Excel will automatically convert it into a "calculated column," so overridden values will have a green mark denoting an "inconsistent formula."
It's still a pretty minor warning and it only requires two clicks to ignore.
> Xtekky initially told me that he hadn't decided whether to take the repo down or not. However, several hours after this story first published, we chatted again and he told me that he plans to keep the repo up and to tell OpenAI that, if they want it taken down, they should file a formal request with GitHub instead of with him.
> "I believe they contacted me before to pressurize me into deleting the repo myself," he said. "But the right way should be an actual official DMCA, through GitHub."
It shouldn't matter if it's a fast desktop or slow mobile (unless it's not keeping up, which is unlikely in these examples); what matters is the display rate on these devices. The demos feel very fast in a 250Hz monitor when compared to a 60Hz one.
That's right. These demos are, as they should be, using requestAnimationFrame [1]. The docs have "Warning: Be sure to always use the first argument (or some other method for getting the current time) to calculate how much the animation will progress in a frame, otherwise the animation will run faster on high refresh rate screens."
Though there are cases like iOS cross-origin frames where it's throttled to 30fps [2] for power-saving reasons.
Folks around here are generally uneasy about tracking in general too, but remove big brother monitoring from Safe Browsing and this story could still be the same: whole domain blacklisted by Google, only due to manual reporting instead.
"Oh, but a human reviewer would've known `*.statichost.eu` isn't managed by us"—not in a lot of cases, not really.