In theory this was nice, but having actually dealt with it in production IE had all sorts of weird bugs with it. Mixing JScript & VBScript (much less PerlScript!) in ASP was even worse, the order of execution of the different language blocks was not specified and could change in a point release or even between installations. In practice both in the browser and on the server Microsoft's multiple language support wasn't really suited to mixing them.
It doesn't, we didn't call them trolls on Usenet as a positive thing. The first trolls were still assholes and existed mainly to disrupt conversation and try to start fights between each other. If the height of your personal accomplishments was starting a vicious flamewar you were just a jerk. Hacker on the other hand did not involve the current negative connotations.
I was shocked to learn that Isaac Asimov died from complications of AIDS acquired via transfusion, but his doctors insisted on keeping it a secret from the public.
Re: join via web, in my experience if you reject the download a few times it'll pop up the link. Clearly a dark pattern attempting to force you to install their insecure and frankly kind of crappy software, but apparently one they're aware of problems with. They just don't care.
They've completely eliminated the visual signal for which tabs are in which container if you're using their own recommended Multi-Account Containers addon. Now you have to click (and load) a tab just to figure out what it belongs to. This is sort of bizarre after all the effort they've put into encouraging people to use containers. Did they just forget it existed?
The issue for heat deaths like the current situation is not just the average increase, it's the _extreme_ temperatures that are killing and they're increasing much faster than the average and occurring much more often. Take a look at any of the analyses of the last big PNW heat dome versus climate change or just skim through this piece from a subject expert:
https://www.nytimes.com/2021/06/29/opinion/heat-dome-climate...
"Heat waves now occur three times as often as they did in the 1960s — on average at least six times a year in the United States in the 2010s. Record-breaking hot months are occurring five times more often than would be expected without global warming. And heat waves have become larger, affecting 25 percent more land area in the Northern Hemisphere than they did in 1980; including ocean areas, heat waves grew 50 percent."
Sooner or later the copyright enforcement companies will find a judge whose willing to rule that since Apple has the capability they have to use it even though this system is aimed at still images only, no sound or video. Then Apple will end up fighting it for years if they're lucky and it doesn't get a quick trip up to Supreme Court that's drastically Hollywood-friendly. The legal difference between mandating that a company create a brand new scanning capability and "just apply" one they already have is significant.
The difference is that Apple has built the infrastructure for _global_, continuous image scanning. No need to hack individual phones or know who your targets are, all you have to do is get some images added to list. If you think the Chinese (or most likely American) government wouldn't love to be able to find out everyone who had copies of certain images, say from protests or inside camps, you're far too optimistic.
This is Apple creating a mechanism for worldwide surveillance and declaring they'd never compromise because they're good people who we can trust. Note that they're not making any actual promises that might land them in court if the system is abuses, they're just repeating that they're good people who'd never cooperate with authoritarian regimes.
It's worse than that. They don't even need to release a different hash list for you, all they need to do is add a few images they know you'll probably have (say from your Facebook or Instagram posts) to the regular DB to meet the match threshold. The people running the database aren't going to be continually going back through old images to double-check they're actually CSAM/theoretically CSAM-related.
The part about "without requiring physical access to the target host" would seem to imply that they only need access to a machine on their end for some attacks.
Is The Register (a UK news outlet) not mentioning the involvement of a UK minor in the death for legal reasons? Obviously there's a limit on details they can give about him, but according to other stories he's the one who made the actual call and is getting off without consequences.
> However, Tesla was founded in 2003, 18 years ago. It’s an enormous company with over 70,000 employees, making ~$10 billion in revenue every quarter, and it’s even part of the S&P 500. It’s not a “startup” anymore. It doesn’t get to use that excuse when it does stupid stuff like this. It needs to grow up and stop lying to its customers. And we’re getting tired of having to say this.
Is it actually still maintained? It's been nine months since the last update and Github's for network for uMatrix shows several forks updating more recently than that.
In fact there are still places teaching abstinence-only education and I'm pretty sure that trying to keep the existence of LGBTQ people from being mentioned is not a huge step forward.
I believe the question was about the mechanism by which you viewing the ad is reported to Brave, not how the ad display was implemented. (A weird interpretation of "reported".)
> HTML filtering is the ability to filter the response body of HTML documents before it is parsed by the browser.
> For example, this allows the removal of specific tags in HTML documents before they are parsed and executed by the browser, something not possible in a reliable manner in other browsers. This feature requires the webRequest.filterResponseData() API, currently only available in Firefox.
https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...
I'm going to trust Gorhill on this one. If a significant feature _does not exist_ in Epic then the only way that it couldn't hurt performance is if it was somehow useless. I suspect the Epic people (accidentally?) didn't measure that aspect.
At that point can they really be considered purely code contracts anymore? If their execution requires a trusted third party some of the rhetoric goes out the window.
Generally when you're talking about cryptography you don't want to make assumptions that rely on reality working out in the way that's most convenient for you. Presuming that quantum computing can't be any kind of threat is a pretty risky gamble.
"During my time at Facebook, I heard reports of autolikers using compromised accounts to seize ownership of prominent pages" sounds exactly like a compromised account being abused.