Forgot your password?
typodupeerror

Comment Re:Another cheap solution to traffic congestion (Score 2) 99

Bus-only lanes reduce capacity for cars, which makes cars travel slower

A statement can only be true if its contrapositive is also true. Does adding lanes for cars make them travel faster? Los Angeles built freeways for cars and widened them over and over again, but did it solve their traffic congestion? No, it didn't. The contrapositive of your statement is not true, and therefore your statement also is not true.

So you see, adding lanes does not make cars faster (at least not in an economically vibrant area), nor does removing lanes make cars slower. This defies common sense and that's why it's a paradox.

Comment Re:Shots Fired! (Score 1) 75

This discussion is about what Apple would need to do to satisfy people with privacy concerns when it comes to third-party replacements for Siri on devices that Apple makes. Arguing that you don't trust Apple because parts of the OS are closed source is irrelevant, because you won't ever trust their device in the first place (or any devices, in all likelihood).

That's why I don't trust them, or anyone. You especially cannot trust phones, since you don't get the code running on the baseband processor even in the best cases — they're not allowed to give it to you.

Ostensibly, Apple could open source the code running on their own baseband hardware (Apple C1). I'm pretty sure the hardware requires signed code for FCC compliance reasons, so you'd never be able to modify it, but as far as I know, nothing prevents them from making the code available.

Comment Re:Shots Fired! (Score 1) 75

Well, that rules out 99.9999% of all mobile phones for you, then, with a +/- .0001% margin of error. :-)

I don't "trust" any of these providers. I expect them to fuck me. I just don't get the option to use none of them if I want to participate in modern society.

Open source is not even slightly immune to those sorts of issues.

Which issues? Not being able to trust that the code doesn't do things which are intentionally malicious? It's as close as you can get. Literally all closed source software is less trustworthy.

You're missing my point. To the best of my knowledge, you can't buy a phone that has an entirely open source operating system now; the phone hardware vendors provide closed-source bits preinstalled, and nuking them is problematic at best. More importantly, even if that were not true, you still would not be able to buy an Apple iPhone or iPad with an OS that is pure open source, which makes your concern entirely irrelevant in this context.

This discussion is about what Apple would need to do to satisfy people with privacy concerns when it comes to third-party replacements for Siri on devices that Apple makes. Arguing that you don't trust Apple because parts of the OS are closed source is irrelevant, because you won't ever trust their device in the first place (or any devices, in all likelihood).

Either way, the automatic presumption is that if a consumer does not trust the device maker, that person will buy a device from some other manufacturer. So for the purposes of this discussion, the decision by the consumer to trust Apple is in the past. It was made when they bought the device with a preinstalled OS. Thus we can presume that the consumer in question therefore trusts Apple to a great extent.

What remains, then, is what Apple, as a presumptively trusted party, would have to do to continue to maintain that level of trust in their devices while allowing third parties to inject code that deeply integrates with every app on the system in a highly invasive way.

Comment Re:Shots Fired! (Score 1) 75

It's fundamentally impossible for an operating system to protect you from the manufacturer of that operating system. That trust is unavoidable.

Apple made their OS open, then closed portions of it, so you cannot trust them, just like all of the other closed source vendors. That doesn't mean no operating system is trustworthy, only that Apple is no more trustworthy than Microsoft.

Well, that rules out 99.9999% of all mobile phones for you, then, with a +/- .0001% margin of error. :-)

That's an arbitrary distinction, though. What percentage of even the most tech-savvy users would actually take the time to audit every source code change to every software update to their phone to make sure it doesn't do something questionable? How many people would be capable of doing it successfully? I'm thinking back to the obfuscated C contest, not to mention thousands of examples of just how easy is to introduce a vulnerability that will get missed by code reviewers for years.

Open source is not even slightly immune to those sorts of issues. It could reasonably be argued, at least on an epidemic level, that we're better off with a larger number of different OS vendors, so that compromising a single vendor will compromise a smaller percentage of devices, but other than the high level of platform divergence that open source tends to bring with it (which has negative consequences for security, too), Open Source really isn't a panacea in a world where vulnerability discoveries are weaponized almost overnight.

If anything, big companies at least have the resources to throw huge amounts of money at prevention, which is something that open source likely does not have.

Comment Re:Seattle, no business wants you. (Score 4, Insightful) 32

Being "pro-business" at all costs means being anti-resident, anti-environment, anti-worker, and anti-consumer.

Therefore, being pro-resident, pro-environment, pro-worker or pro-consumer might brand you as being anti-business.

There's a balance to be had among all of these things. Let's find that balance.

Comment Re:How? (Score 1) 120

So you're back to requiring individual apps to enable support, which is kind of my point. There's no easy universal way to stop kiddies doing things you don't want them to do.

Correct. There's absolutely no plausible way to do it at an OS level except *maybe* for the camera, and even that can likely be thwarted by recording a video that starts on something innocuous and ends on nudity, because by the time the monitoring algorithm notices the nudity, many frames would already have been sent to the recording app.

But what the device manufacturer can do is require that all apps submitted for app review must comply with those standards and use those tools to check for disallowed content, and block any apps that do not comply from being installed on a device that is owned by someone under 18 (or whatever age is specified by the law in question), including blocking side-loading. You'd still have a handful of parents who unlock the devices for development so that their kids can write apps, but all other young people's devices would presumably be locked down (assuming the parents don't or can't turn that off).

Comment Re:Shots Fired! (Score 1) 75

Creating an infrastructure for making that possible while protecting user privacy is genuinely hard.

What you're saying is that the infrastructure doesn't protect your privacy from Apple now.

It's fundamentally impossible for an operating system to protect you from the manufacturer of that operating system. That trust is unavoidable.

Comment Re:And as usual for every evil thing we suffer (Score 1) 166

It went from $4B to $120BN.

No, the Prop 1A voter guide gave an estimate of $45 billion in 2006 dollars, which is $71.9 billion in 2025 dollars.

The $126.2 billion is in year of expenditure dollars, most of which is still in the future, so let's call it $100 billion in 2025 dollars.

So in constant year dollars, the price went up from $71.9 billion to $100 billion. So there's a little room for improvement.

Slashdot Top Deals

There are running jobs. Why don't you go chase them?

Working...