I agree that more granular permissions is better (in terms of dictating which sites an extension has access to) but I think the main problem as I understand it is that this is an entirely seperate issue from the one that nukes uBO.
V3 introduces a hard limit on the total number network filters an extension is allowed to set and it's a laughably low number. Far below what uBO uses even on a barebones, default setup
Prior to my discovery that fandom was bad and a lot of wikis were moving away, I was following so many instances of out dated info in games I was playing due to not realizing that the wiki was no longer maintained since the active contributors had moved elsewhere and updates/patches to the game had rendered the info moot.
The websites I've seen (and was referencing in the Gist) basically do this. But it's a very simple anti-debugger technique that uses an IIFE containing a `while` loop with a `debugger;` statement in every iteration. You can circumvent it by opening DevTools on another website and toggling it to "skip all breakpoints."
I'm sure there are more advanced anti-debugger techniques with different denial-of-service vectors. And I'm sure that the attack surface for actual exploits (beyond just DOS) is also greater than browsing a website without DevTools open. But it's not like browser vendors grant super-permissions to websites when the user has DevTools open; any exploit would depend on a high severity vulnerability.
I do agree that it's probably smart to browse sketchy websites in an isolated browser, and ideally one inside a VM.
If we find out in the next 12 months that OpenAI has been storing requests from Apple/Siri AND Apple doesn't come down on them with a 10 ton lawyer hammer, I'll pay you $500.
And I can almost guarentee you it will magically all turn itself back on/reinstall itself eventually after the OS force updates/reboots itself in the not too distant future.
> Wasn't the Moskva spotted by a drone before missile deployment?
Drones were speculated to have been involved but it was said they were used to distract the ship's defense system as the missiles were in the air, not in the initial spotting/targeting. Although I suppose they could've pretty easily done both.
- solid integration with macOS Calendar app (shows all your events and has a "+" option to create new ones)
- can also display a time clock along with the date and also has fully customizable datetime patterns meaning you fully replace the system date/time. I especially love doing this and now being able to just click on the date time in the menubar and see a calendar popup (instead of datetime settings which I never need quick access to) similar to the Windows clock
I can't find the source but in some of the communication Selig released between him and Reddit a few days ago, Reddit themselves confirmed that their pricing is based on lost oppurtunity cost per user, not just expenses
I think GP's point is that the amount of the settlement is not enough given the total number of users involved, rather than the class action itself is insignificant.
In my opinion, in these type of cases, the amount should be directly correlated to how much revenue the company generated from the sale of the data. If the sale of my data is deemed illegal/unethical/etc, then I should reap all financial benefits plus damages.
What's stopping FB from just continuing this practice and just upping their costs to their customers to include this added "cost" of doing business?
It's a good point. More hyperscale excesses would be redressed if we calculated on the greater of damages or profits.
My understanding of the current model is that if {profit} - {legal fees} > {calculated damages settlement}, there's zero incentive not to break the law.
Generally, class actions can include changes in behavior as part of the settlement. Class actions also pave the way for bigger class actions if the behavior isn’t changed, especially since they often negotiated by claiming to have already spent resources fixing the issue and their claims and the settlement have to pass judicial approval.
V3 introduces a hard limit on the total number network filters an extension is allowed to set and it's a laughably low number. Far below what uBO uses even on a barebones, default setup