> just three atoms tall, technically making them 2D rather than 3D objects
No. It makes them very short 3D objects unless they are either no atoms wide or no atoms deep.
2545 publicly visible posts • joined 7 May 2012
>accusing it of "intentional and systematic misuse and misappropriation of its users' property."
Surely intention is nearly impossible to prove in this case. Hopeless incompetency for sure. Negligence. Failing a duty of care. Failing to report such events to authorities (let's forget the question of which one for the moment). Lack of auditing. There would be all sorts of open and shut cases yet the plaintiff seems to be making it very hard on himself to score a victory.
IANAL etc...
>But you can make them think it's too much trouble and go after easier prey
As the joke/adage/saying goes in at least one variant.
Don't try to outrun the lion/bear/[any Australian animal except some of the sheep]. Try to outrun the guy behind you.
>"If you think passing a law making data localization a requirement in the EU or Brazil [...] stops the NSA from getting into those databases, think again."
That is excellent. hosting in the EU or Brazil is not going to make the job of our beloved acronyms any different so they are offering no opinion about where we host. Got it!
Unless the bricked phone also somehow permanently damages its battery and screen the bricked phone will just be ripped apart and sold as parts.
I'm all for providing users with methods to brick their own devices but this bill doesn't seem to have really thought through the problem.
> Network ain't gonna resize itself just when you pay.
Then perhaps it is best to not sell based on the maximum possible speed you might get in the middle of the night for 90 seconds and rather sell based on the range of speeds you can expect?
The problem these companies have (and I have no experience with Verizon but I doubt they are any better or worse than most) is that through the sales cycle they are quite happy for you to believe you will get 24Mb/s on your ADSL2 connection when they can't even saturate a link which is only running at 33% of that speed during peak times.
If you want to offer a 10Mb service, then you need to provision to deliver 10Mb. If you only provision for 4Mb on account that historical trends show that you can get away with it, then you better be good at JIT provisioning.
Nintendo may have missed a trick here. Consoles are effectively sold on the printer- ink / disposable razor business model. They lose money upfront and become profitable by taking a large licencing fee on each game and peripheral.
If Amazon play their cards right they could create a gaming ecosystem and using some sort of loss leader device and then get out of hardware side once a few other manufacturers are on board, or even do what Google do with nexus and keep the volumes low enough to not hurt profits and annoy partners but high enough to be able to set a benchmark.
Casual gaming has never been a bigger market but it is mostly now done with iPhones/pads and their android equivalents rather than Wii/ gameboy/ds or whatever they get named these days.
It's also possible to "hack" the brake lights so they don't come on when you slow down. You have to weigh up the probabilities against the consequences and decide whether the safety features made possible by short range v2v conversations which may be beneficial where something happens out of line of sight (like just beyond the crest of a hill or a blind corner)
IMHO, the responses to my comment have been a reaction to the collection of data. That is a fair enough reaction to have, but I don't think it addresses the challenge I put out there.
The argument that an ID is unnecessary is wrong. I am not saying that a persistent ID is mandatory, nor that that ID needs to be linked in any way to your identity, but if your car one moment receives a message that an oncoming car has veered into your lane, loses that signal as you go down a hill and then you get another message saying an oncoming car is not in your lane, is it the same car? Being able to trace and then forget other cars for the "session" is important even if the ID number is randomly generated at each engine startup.
These "listening posts" as argued are no more invasive than a suggestion that the state could put out cameras with numberplate recognition software that works out the vehicles speed (either by radar or by listening to these "anonymous" messages and then taking a picture). Both need to be regulated to ensure a good balance between privacy and safety.
I am simply pointing out that from a privacy perspective, your car is already traceable with a camera and the CPU power of a Pi using off the shelf software. How do you think Google maps blurs the plates if it can't locate them with very simplistic pattern recognition?
Or a 64 bit ID should be enough for a few million years of all cars switching IDs every second.
It is already mandated by law that all cars have number plates which can be used to track you. There are brake lights that show your intent to slow down. There are indicators on all non Audi cars that are legally mandated to indicate intended direction changes.
There is no premise of privacy with the sort of data needed by this system. As long as it goes peer to peer in a short range rather than over some cloud, what is the complaint?
Differentiate by CPU, memory, screen specs, battery life, camera and flash, waterproofing, sound quality, storage, SD, removable battery, quality, warranty, wireless charging, NFC, bluetooth features, biometrics, build materials, distribution channels, or do something really different like dual boot to sailfish or tizen or something, physical size or form factor or colour. All if all else fails then sell yours for less.
The current state of things is akin to each car maker deciding to ignore the steering wheel and pedals and invent their own.
Please Google let us selectively deny tokens that an app requests.
The app developer should have the ability to state whether a given token is mandatory or optional and a few lines to describe why they want it.
As for optional tokens, there are two ways this can be easily handled. The app developer could either receive a runtime exception when they make a call to a method where the token was denied or they could elect to receive fake data for things like contact lists, GPS coordinates or SMS messages. Then even lazy developers could mark most tokens optional without needing to make code changes.