In Japan, SoftBank's mobile network also went down for 4 hours .... allegedly due to Ericcson sfotware going titsup as well ...
(Caught this on NHK World news)
177 posts • joined 22 Oct 2007
Put nothing in "the cloud"
- that you don't have a certified, current and regularly checked, usable and updated (local) backup of.
- that is too important to lose (for whatever reason)
- that you must have access to at critical moments.
Because MS insists on shoveling features they haven't fully tested (if at all) at their hapless victims (otherwise known as "users") in a desperate bid to prove their OS is ready for primetime.
And rather than STOP and fix the mess they made last update (or any of the previous ones), they happily/blissfully move on to the new flavor of the day insisting that this time, they'll get it right!
They say insanity is doing the same thing over and over and expecting different results ... making the institutional mental health of the Microsoft edifice questionable at best, mythical at worst. Take your pick.
Because VueScan's business model relies on them supporting the hardware.
MS's business model relies on locking people in and then pumping out as many useless brittle features people didn't ask for and can't control, all the while only caring that that the customer's computer supports the downloading of the latest version, and the customer's wallet supports paying for it.
Interesting how the XB-70 Valkyrie has been completely forgotten.
This was a plane contemporary with (and similarly sized as) both Concorde and the Tu-144 ... yet was capable of cruising at Mach 3.
Only 2 prototypes were ever built, and the 1960's emphasis on ballistic missiles (plus a fatal midair crash on a photo op flight of all things) put an end to the program before it ever had the chance to fully develop.
AFAIK, the second prototype achieved Mach 3.4 on a test flight ...
both planes were turned over to NASA Dryden Flight Research Center where they conclusively proved that sonic booms and population centers were an incredibly poor mixture :D
http://xb70.interceptor.com/ for its intriguing story!
If the idea is to get these contraptions ready for actual real world use, wouldn't testing them under real world conditions make more sense ?
Which they just ran into. And complained bitterly about.
The Wright Brothers had brass balls of steel to venture into largely unknown territory with things nobody had even tried before. Electric and solar power hass been tried for the better part of 25-30 years and it still doesn't work (and if you believe it does, I'd gleefully remind you of South Australia's ability to keep the lights on), and barring a shift to an absolutist world government decreeing it the winner, it won't (something to do with lack of energy density, overly large dependency on 'just the right' environmental conditions etc)
But I admit, it makes a wonderful festival parade.
"Team Arrow founder Cameron Tuesley explained the conditions that made finishing so difficult this year, saying “we had 40 degree heat, tropical storms, major thunderstorms, severe cross winds, dust constantly, animals all over the road, major trucks, pretty much everything you can throw at something were thrown at us”."
In other words, they had all this icky nasty weather that normal vehicles drive through everyday ?
And that was a problem ?
*walks away laughing*
(Currently) content Nexus 6 owner here, which was my first smartphone ... and it looks like it's also my last one as well.
Smartphones are a great convenience, but if I have to chuck out my perfectly good servicable phone every 2-3 years to boost their device sales bottom line, I'd rather spend a few tenners on a shitty feature phone with only 2-3 years life expectancy.
I knew MS was good at shooting themselves in the foot, and getting (a lot) better at it ever since W10 ...
...but this isn't just "accidentally" shooting yourself in the foot anymore, this is more akin to pulling pins from hand grenades and intentionally dropping them at your feet!
I can't even think of a better way for MS to lose the desktop market advantage they had - this might end up driving adoption of thin clients (and face it, a console or phone/tablet is really a (moderately smart but still very dependent) thin client connecting to a server farm elsewhere) so very hard.
Because we don't need to use a smartphone running Goopple's OS to make a phone call - we just use them because they're convenient, plentiful and we don't really have an expectation of privacy or control over it - after all, the only real control you have on your phone is when you hang up (and remain connected to the network and be available) or turn it off and aren't - and remember you can pick up a cheapo feature phone and it'll connect to the network just fine, avoiding all the conveniences of data slurpage other than where you are (for obvious reasons) ... well for now at least. (I think I just heard a black helicopter)
With a computer it's different. We have expectation of privacy, being able to choose what we share, what we connect to and what we do; and an expectation of control: when we do our updates (if at all), what we install, what we keep, where we keep it and how.
MS just put a huge bomb under that with Win10, and given there's this really huge ruckus going on about privacy and exactly what control an end user has over that data he generates, that large corps profit from, resell and share (willingly or not) with whatever weird acronym agency just happens to be interested makes this a rather sticky point.
They have perfectly played the user inertia card (I honestly tried to get family/friends over on Openoffice but they all went back to MS' offering because reasons (school/work/buttons are different/don't want to learn) - whereas mentioned before, changing phones is a much more hassle-free experience.
says Marisa Rogers, the Windows and Devices group privacy officer.
"The Windows 10 Creators Update is a significant step forward, but by no means the end of our journey," she said.
...where the "step forward" is into the abyss Wile E. Coyote style, and the end of this journey is being of course, to be relegated to the history books as soon possible.
"The problem was two-fold. First, people weren't always marking sensitive documents as private and non-public"
So the default settings for your own documents are "visible to all and sundry" unless you go to the (likely well obfuscated) privacy settings to restrict who can find them ??!
I'm not sure there's a facepalm in this universe big enough.
I also wonder about the liability issues:
- Who is liable if data is lost/becomes unavailable
- Who is liable if (some of) this data turns out to be involved in criminal activity
- Who is liable if, god forbid, this turns into a data exfiltration method
- What's going to happen if this gets involved in a nation state secrets or "terrorist activity", and what implications does that have for the unknowing users storing bits and pieces of data, both within and outside said nation state ?
...and that's just off the top of my head.
Just so I understand:
Rather than download the app and run it local whenever you need it, you get to open a connection to a remote server in a jurisdiction not of your choice, with laws you might not agree to, to receive the data ... every time you need said application.
1) This might save you on wait time initially
2) This will not, in the end, save you on connection fees
3) This will remove control the user has over his own data (quelle surprise, this being google)
4) This puts more control at the remote endpoint (where/whover that is) to profile the user
5) And people think this is a great solution ?
Uhm, I have this wonderful bridge ...
...that the side with the simplest uniforms usually wins.
it could be suggested as a modern-day corollary that the side with the simplest servicable weapons has the better chance of victory too.
And since the only battle an F35 is likely to fight is the struggle to leave the ground - where the only clouds it is likeliest to see are composed of big data instead of big amounts of water vapor ... well ...
The best solution to the IoT pwnage problem is, of course, the humble hammer.
However, where to vigorously and repeatedly apply it is a point of debate, but here's a shortlist of targets to consider:
- the manufacturer, for baking fixed credentials
- the government, for twiddling thumbs
- the blokes running Mirai for obvious reasons
- the device class, for offering solutions to a problem nobody is having
- you, for falling for the IoT neofilia scam
Biting the hand that feeds IT © 1998–2019