The 'retirement' of Pope John Paul II actually made one of my favourite jokes obsolete.
Why does the Pope kiss the ground after each landing?
That's something only Alitalia customers understand.
47 publicly visible posts • joined 2 Dec 2009
If all they wanted to do is prevent phone theft for parts, Apple could just have extended the existing iCloud locking mechanism to a phone's individual parts.
iPhone with a new display from a locked phone (or better even, a phone reported as stolen) refuses to work.
iPhone with a new display from an UNlocked phone does some calibration thinggy and then works normally.
Takes one request to Apple's servers for the iPhone to know what it should do with its new donour organ. It could even display a prominent message along the lines of "this phone contains stolen replacement parts", which would be a way better deterrent to thieves than "TrueTone doesn't work, which you might or might not notice".
I'm aware there are some excuses about how Battery Health can't work without the battery's history stored in the donour phone, or TrueTone needs to be calibrated properly, but I call BS on all of them. All of those donour spare parts already have a chip on them that could/should have stored all relevant information ready for the new device to query.
Oh, I think they've learned. They've learned that inbetween two anti-trust injunctions, they can pretty much do whatever they want.
The investigation won't help much if it only concludes once the damage has been done. MS will pay a fine that's well worth it to them and change absolutely nothing.
Unless the fines start being so eye-wateringly steep that a conviction will have the shareholders howling and demanding the entire board's heads on spikes, nothing much will change.
Solaris had an interesting bug for many years. Most telnet clients support a command such as "telnet -l username" to supply the telnet daemon with a user name. The Solaris telnet daemon forwarded that argument to the login process unchecked. As a result, you could get root on any Solaris box by typing "telnet -l '-f root'" on the client, which on the server side would spawn a process "/bin/login -f root", which logged you in as root without any further checks.
Oh the fun we had when we were students.
I think Opel (pre-PSA) had a pretty good solution.
All expensive components in a car were "married" to each other and would not work outside that particular car.
As long as they were inside the car (and the car saw a valid car key), you could quite easily "divorce" them and then "marry" them to another car. Meaning that it was reasonably easy to sell/use your own car for spare parts, but thieves has to either steal your car keys (at which point it's pretty much game over anyway) or go through an authorised Opel dealer.
Apple could easily do something similar hidden behind a secret service menu or something.
> and, better still, feed them bogus data so they don't break
FWIW, Oppo phones offer this to some degree. You can set apps to be served an empty phone book, call log, message (SMS) list and "events" (whatever that last one does is unclear - suppress system broadcasts?). Not much but a start. If you know where to look, you can also manage some of the more obscure app permissions, such as an app gathering info on other installed apps. At the very least it's a step in the right direction.
There are also some Xposed-based solutions for rooted phones, but stability-wise they all seem to be perpetually stuck in alpha.
I still miss the original LBE Privacy Guard. I've never seen anything even remotely as powerful.
PE is also technically identical to neutral, though (in modern installations) for safety reasons has its own wire. E.g. an RCD needs to be able to distinguish between neutral and PE - there's no current supposed to go through PE at any time, while the current through L and N should be identical. If it's not, something's wrong.
In older TN-C installations, PE was just connected to N at the socket - at least in continental Europe; not sure about the UK. This had the interesting side effect of electrifying anybody who touched a device connected to that socket when there was a problem with the neutral line and the device was switched on.
As far as the electrons travelling through the wires are concerned, there's no real difference between the two wires.
In real life, one of those is connected to the ground and called 'neutral'. As long as you've got your feet on the ground (or thereabout), you're indirectly connected to it. That's why touching the other ('live') wire hurts - you're now connected to both.
Technically it would be safe to touch the 'live' wire while in free fall or otherwise disconnected from the 'neutral' wire. You still shouldn't try it though.
(This would be the same with DC, only you'd need to consider polarity instead of the phase.)
In a (relatively) modern TN-S system (separate neutral and PE), switching or connecting neutral and PE would immediately trip a breaker because of the current mismatch in line and neutral.
Whether the fuse would blow depends on the kind of fault.
I reckon the faulty printer in the story was connected to a TT system, which would have been common around that time. Switching neutral and PE can have quite funky effects on the voltage there, not to mention bugging the worms and moles.
I've bought the Reno2 some 8 days ago to replace my aging OnePlus 3T.
So far I'm very happy with it. It's posh, snappy and generally a pleasure to use.
It supports the latest iteration of VOOC (what OnePlus used to call Dash Charge). AFAICT the chargers are totally interchangeable between the phones, though Oppo's (newer) charger promises 20W of oomph instead of just 15W.
It also came with a screen protector pre-applied, which is a very good thing, and a really ugly case which I'm not using.
The selfie camera (I've heard it called 'shark fin' but will henceforth refer to it as 'pizza slice') works very well so far. I don't use it often though so don't mind the slight delay. The mechanism seems sturdy enough.
The pizza slice also looks much nicer than OnePlus's rectangular periscope thingy.
Pros:
* The camera is very good (though I might be biased as the 3T's camera is not much to write home about). I'm very impressed by its night mode.
* The on-screen fingerprint reader works very well and looks good, too.
* ColorOS is generally a nice thing. Coming from OnePlus's OxygenOS (which I love) it's not all that different. The notifications are a bit too iPhone-y for my tastes... and dragging a finger down on the start screen will bring up a search window instead of pulling down the notification area. The latter would be lovely for one-handed use on such a big screen.
* Built-in privacy tools. You can set data-grabbing apps to see an empty phonebook, an empty calendar etc. Unfortunately this does not work with system apps.
* Autostart can be disabled on a per-app basis.
* Secure environment for banking apps. Not sure how secure it really is, but at least the phone tells you that the app gets some extra protection.
* Protected apps that require an extra PIN (or fingerprint) to access. You can also hide the app icon, so that the app is only available by dialling a user-configurable phone number. I'm using this for my banking apps and the bloatware that can't be uninstalled, see below.
* The battery lasts forever.
Cons:
* There is some bloatware. Most can be uninstalled, though a couple apps remain.
* Most Google apps, especially Chrome and Maps, can neither be uninstalled nor disabled. I hate both. With the Reno2's very good privacy helpers, this would be the one reason for me to root the phone. Workaround: remove all app permissions, make them 'protected apps' (see above) and hide the icons.
* There's an app Called Phone Manager which is supposed to keep your phone in good shape. While this is a good idea in theory, in its current iteration it does this by repeatedly asking you to disable all background app and asking you to delete basically everything on the phone, including data you're still actively using. It also won't take no for an answer and keep bugging you on a daily basis. I ended up disabling the notifications altogether.
Unless it was somehow Sony's fault that an unauthorised third party got hold of the account, I don't see why they should be held responsible for the consequences. How can we ever expect people to stop giving out their passwords and credit card data to each and every phishing site if they never have to face the consequences of their actions?
I still think Sony are evil. I just don't think *everything* bad happening in this world is their fault.
Looking forward to the next shareholder party.
"Yes, I spent 19 billion of your money on WhatsApp. That's $45 per phonebook for data that we're not going to use."
It's like an 80's rock star saying he bought that suitcase of cocaine just to look at it.
What's the age of criminal responsibility in Finland anyway... IOW, how can you legally do this to a ten-year-old?
I mean, she didn't even succeed in downloading anything, and dad bought the song for her the day after, so clearly no damage has been done, thus there's no need for compensation. And criminal charges... pleease. She's a child FFS!
/mnt/sdcard and all its subdirectories on my Galaxy Nexus look like this -->
drwxrwxr-x root sdcard_rw 2012-02-21 sdcard
That means everybody can read stuff, but only apps belonging to the group sdcard_rw can write stuff.
That would also explain why the image viewer works, and why the corresponding Android permission says "change/delete" and not "read/change/delete".
So Android isn't lying to you, but you might still get the wrong impression. Hmmm. I for one always (wrongly) assumed that apps also need that permission to *read* the SD card.
A chmod doesn't work, looks like the 0775 is hardcoded into the FS driver. I wonder if there's any way to keep untrusted apps away from my files?
If you're not afraid of rooting your phone, there are two excellent third-party solutions to this problem.
The first one is to install CyanogenMod. Then when you go to Settings --> Apps --> Manage Apps (or wherever you can view an app's details), at the bottom of the screen where the app's permissions are listed, tapping on any permission will toggle it. This is what Google should have added to Android in the first place.
Downside: this requires a factory reset.
A more elegant solution is LBE Privacy Guard, a simple app that requires root privileges but can otherwise be installed just like any other app on top of your existing system. Its permission management is not that fine-grained, but it has one huge advantage over CM - instead of actually giving the app a slap on the wrist when it attempts to use a permission that has been revoked, it'll intercept the API call and feed it false information.
I've used both solutions (separately) for some time and prefer LBE Privacy Guard because it's more elegant: ...
An app that wants to use a revoked privilege on CM will get an "access denied" message. Some apps aren't designed to cope with this and will crash.
An app guarded by LBE PG on the other hand will simply see an empty phone book, an empty message list, a phone serial number consisting of all zeroes, etc. depending on the permissions you've revoked. It's tricked into believing it still has the revoked privilege but there's simply no data worth looting.
In addition to granting and revoking permissions, LBE PG can also be set to ask or alert you each time an app wants to use a certain privilege.
Paris, because she's been rooted countless times.
DDoS'ing *three* websites chock-full of people whose favourite pastime is taking out scammers? That's a bit like getting stung by a hornet and kicking the nest in revenge. It may have seemed like a smart idea at the time, but I'd be surprised if that guy could open any new fake Amazon website in the foreseeable future without half a dozen experienced site killers falling over each other to shut it down the moment it's online.
Have a pint or two on me, baiters and warners. You volunteer your time and money for a very noble cause.
CyanogenMod 7 lets you modify the permissions of installed apps. Just tap on a permission in the list to grant or revoke it.
If you don't want to re-flash your phone, there's an app called LBE Privacy Guard that offers the same functionality but will also let you set it up so it asks you for permission every time it detects a potentially unwanted action. This works really well. Requires a rooted phone though.
If your phone happens to be rooted, try LBE Privacy Guard. It runs in the background and lets you set permissions to grant/deny/prompt on a per-app basis. It also notifies you every time an untrusted app wants to use a permission you've blocked. I've been using it for 4 months and am very happy with it - no app crashes due to withdrawn permissions so far, and it allows me to install some useful apps that request a rather questionable set of permissions.
Paris, just because.
"But I also believe that it makes no sense to bring a class-action suit when the aggrieved parties know in advance that the bulk of any damages awarded (if any) will go to the trial lawyers"
I hope they get sh*tloads of cash from Dell. It's not like I'm a huge fan of lawyers, but to the beancounters at Dell the pain level is the same whether their money ends up in their customers' pockets or at some lawyer's Porsche dealer. If nothing else it might at least serve as a deterrent to other companies that think about saving money by selling dodgy kit.
The title says it all, really. Did contract work for lots of shops with Dell gear. Few of them had many happy users, and even fewer had many happy IT people. Regularly saw 'identical' models with totally different hardware inside, because Dell love to solder together whatever remaining stock they can buy cheaply at the time they build your computer. Makes image and driver management a real joy.
Paris, just because.
...and am still wondering what took me so long.
Stuff looks much nicer, there's a ton of free memory, Google spyware is only there if you choose to install it separately, and (subjectively speaking) stuff is much faster, too. Took me about three hours to install CM7, restore my data and reinstall the most important apps.
If you're planning to upgrade too:
* I've found it much easier to install ClockworkMod via Unrevoked (google it) than following the instructions on how to build a gold card though. It goes like this: Download Unrevoked, wait till it has automatically rooted your HTC, copy CM7 .zip file to SD card, reboot into recovery, reset to factory settings, click Apply Update, reboot.
* Check out MyPhoneExplorer if you want to back-up your data. It does everything HTC Sync does, except suck. (Not associated with it, just a very happy customer).
* The Google apps (Market, Gmail, ...) will need to be installed via recovery mode as well. It's on the CM7 download page, just remember to scroll down a bit.
Also, screw you, HTC.
I liked Dolphin Browser (even paid a couple quid for it), but for some reason it became increasingly frustrating to use on my HTC Desire. Maybe the bugs have been fixed in the meantime. If you're looking for an alternative to the stock Android browser, you might want to take Miren Browser for a spin - it has all the Dolphin goodness plus some unique features, and I find it to be much more responsive on my HTC Desire.