I've been using Firefox pretty much exclusively since its first release (I did a year or two on Opera about a decade ago), and I can't remember it failing to render any site at all. I do run across broken sites from time to time, but they always work once I dial back my extreme privacy settings.
According to the ruling, the exposure of your location history is the automatic price of conventional cell-phone usage—which, just as Carpenter noted, is a "pervasive and insistent part of daily life."
If we can't step out of our houses or drive to the doctor without that fact getting placed into a searchable database, then I'd argue that it qualifies as a "pervasive and insistent part of daily life."
> I don’t think a ruling about private records held by a private entity like google or a phone company naturally extends to surveillance of public places.
Even when the surveillance is being conducted by a private entity? A private entity that's selling access to its private records of the comings and goings of a sizeable chunk of the population to police who are buying specifically because it would be a 4th Amendment violation for them to collect the data themselves?
If it's reasonable for we consumers, who know that cell networks and phone makers are collecting our data, to expect privacy, then it's reasonable to extend that same expectation to operators of ALPR and related techs. There's no opt-out, after all. We can't reject the terms of service.
It's tricky because you have to chain multiple exploits, but yes. You can temporarily downgrade from RDP2 to RDP1 via glitching. At that point, you have to move directly into RDP1 techniques without causing a reset.
The protection levels are set in the RDP register. [listed out of order...] Level 0 = 0xAA, Level 2 = 0xCC, Level 1 = anything else. Flip just a single bit and you get out of RDP2.
The idea is that specifications are not copyrightable, but implementations are. So, the first team reverse engineers the work and writes a spec for the second team to work from. That way, you guarantee that the second implementation is free of copyrighted code.
Recently as in the last 8 years when they overhauled it. It really was slow as heck back in 2016, but the e10s effort really, really paid off in terms of performance.
It runs noticeably faster than chrome on my 12 year old laptop. Plus, it isn't riddled with invasive tracking garbage.
Yeah, but. The side-effect of catching criminals and protecting the children is that they also provide a searchable database of everyone's historical travel habits.
It's my opinion that our historical ideas of expectation of privacy when in public spaces are incompatible with the current state of surveillance technology. Sure, everyone should expect that they might be recognized by an acquaintance when out in public, but I don't think it follows that our entire past history should be available at any time in the future.
I'd like to read this list, but the color scheme is among the least accessible that I've ever come across. Dark, greyish-blue text with dark, bluish-grey highlighting over a dark grey background. Wow.
If any fledgling designers are here, then take note and add this to your list of examples to avoid.
I think that minimum redundancy is a wiser ethos. There are a couple of places where the weight penalty versus cost of failure makes the decision a no-brainer.
In my case, that means bringing aquatabs to back up my primary water treatment system and a second way to strike my stove. An extra 2 grams for aquatabs versus 4 weeks of greasy diarrhea? Check. Ten grams for a second mini bic or small fire steel versus cold soaking meals that I designed for cooking? Check.
But I do agree with you that bringing less in general frees you to move faster, go farther, and enjoy the journey even more.