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.
No, that's not dumb at all. Inputs are filthy and sensors fail. If you're not comparing all available sensor data to confirm your understanding of reality, then a single sensor failure could... oh I dunno... cause your 737 MAX to divebomb.
The F-35 could compare weight on wheels to airspeed as a simple sanity check.
> When I tell people I work on authentication software, I nearly always hear some version of the same story: I hate multifactor authentication. No, really. People hate this stuff.
I hate all of the half-cooked non-TOTP MFA methods that I'm forced to use. Just let me use my freaking authenticator app. If you believe that your users prefer (or maybe it's just you?) more databroker-friendly methods, then fine, but please at least provide TOTP as an option.
If I were responsible for a mechanical doping program, then I'd install the motors for the leadout and mountain domestique riders and leave the team leader clean. Who cares if they pay the weight penalty after peeling off if it means that they can provide extra support for those critical minutes?
Among the additional information Kochava collects and sells are non-anonymized individual home addresses, phone numbers, email addresses, gender, age, ethnicity, yearly income, “economic stability,” marital status, education level, political affiliation and “interests and behaviors,” compiling and selling dossiers on individuals marketed as offering a “360-degree perspective,” the FTC said.
...
According to the FTC, Kochava’s data can identify women who visit reproductive clinics by name and address along with, for example, when they visit particular buildings, their names, email and home addresses, number of children, race and app usage.
...
Kochava marketing materials tell customers it offers “rich geo data spanning billions of devices globally” and that its location data feed “delivers raw latitude/longitude data with volumes around 94B+ geo-transactions per month, 125 million monthly active users, and 35 million daily active users, on average observing more than 90 daily transactions per device.”
...
The complaint also alleges that the company has lax procedures for determining who it is selling data to, saying purchasers are allowed to use a generic personal email address, label an alleged company as “self” and explain they plan to use the data for “business.”
I think the incongruity that the original commenter was pointing out is that Wildberger critiqued radicals by saying that they're imprecise approximations that rely on the problematic concept of infinity.
So setting aside the new method's practical implications, replacing an infinitely accurate approximation with a different infinitely accurate approximation doesn't feel any different.