991 karma · joined October 3, 2013
More generally, Brave's attitude towards Chromium changes has been "disable first, ask questions later", even when it hurts forward-looking developers and useful feature adoption [1]. In the case of the file system API, there's also a possible conflict of interest, given how they're pushing IPFS and the rest of the crypto web bullshit. My biggest gripe with them is that most of their development efforts go into developing the cryptocurrency features and they end up neglecting general browser usability and innovation.
Speaking of Twitch specifically, a lot of people are lured into streaming with the promise of earning money doing what they love. And a lot of them don't make it, despite streaming 8+ hour sessions most days of the week. The unfortunate reality is that success is not purely proportional to dedication, and it quickly leads to horrible problems like burnout and depression.
gjs -c "(() => print('hello'))()"The part that worries me the most is that no one outside of Apple can verify that the hash set they're pushing hasn't been tampered with (Section 4, Remark 5). This allows them for example to add leaked product image hashes to hunt down and prosecute people who share info about their products before release.
In fact, the system seems designed to be impossible to audit, with only a subset of the whole hash set being pushed to clients, so that researchers can't even tell when more hashes have been added. As a consequence of that design, they acknowledge that a "small number" of false negatives will be missed, and justify that with an argument that it improves performance (Section 2, Remark 3)
False positives on the other hand will be common (as detailed in Section 5, "Duplicate images") - simply copying a file on two client devices that don't share a cloud owner ID will count towards the threshold, and again fall back on "mechanisms outside of the cryptographic protocol".
And last but not least, let's spare a thought for the Apple employees that will be required to sift through potentially traumatizing imagery (assuming the company doesn't outsource that to a third party.)
It's already here to some extent with the obligation to provide a phone number, but unlike a phone you can't just change your legal identity if you need to. Determined bad actors on the other hand will have no trouble farming ID docs from disadvantaged people to assume their identity online, through coercion or social engineering.
And soon everything you do and say online will have immediate, real-world ramifications.
three.module.js:21344 Uncaught (in promise) TypeError: Cannot read property 'indexOf' of null
at new ch (three.module.js:21344)
at ht (three.module.js:24988)
at new gh (three.module.js:25021)
at m (CanvasSystem.js:30)
at S.addSystem (World.js:379)
at be (initialize.js:112)
at async onCreate (index.js:47)The issue is they're pushing unwanted software that displays ads on the desktop through a (possibly bogus) driver update that you can't really refuse without halting Windows Update altogether.