Ignoring the implied hype in TFA, they quote the original blog post: "This means that a device with a corrupt boot image or verified partition will not boot or will boot in a limited capacity with user consent." (line breaks added for clarity).
Are U.S. regulators really actively investigating 25,000 Tesla Model S cars? Are they making appointments with the owners and checking under the hood or something?
As I said in the last thread on FireFox... extensions are the only things that keep me using it. If they break extensions, I'll have no reason left to avoid switching.
(Hint to Mozilla: don't break extensions!)
If I could only reliably stop Chrome extensions from auto-updating, I'd have made the switch already. Basically, a dumb forced feature on Google's part is what is helping to keep me using FireFox.
I still feel like the EV needs another 20 years or so.
After 2 years and 20K miles in an EV, I will never again have my daily drive be an ICEV.
Forget the lack of tailpipe emissions. Forget the "clean/green" vehicle (mine is 90% charged from solar). Forget even the complete lack of engine noise and rumble.
Just focus on the 100% torque when you press the accelerator. That silent "whoosh" as you pull away and leave the other cars behind in their exhaust fumes.
I don't think there are many LEAFs that "have barely any degradation" after 150k miles. The original battery chemistry in the 2011 and 2012 models (when it was first introduced) have had terrible battery capacity losses, especially in hot climates. It's reported all over at MNL. A typical one: http://mynissanleaf.com/viewto... Many folks with LEAFs that are 4+ years old have been getting warranty replacements of the battery pack.
(In fact, I don't think there are that many LEAFs at 150k miles total yet)
What's the standard for replacing EV batteries?
In the LEAF community, there isn't a standard. You only replace it if the cost of a new pack ($6K) is worth what it adds to the range of your vehicle. Alternately, if it hasn't lived up to the guarantees under the warranty, and you can get a replacement for free. Nissan's warranty is it will hold more than 8 of 12 capacity bars (as shown on the dash); that's not 66%, since the as people have discovered over time the bars are not completely linear. Hence the subject of the above linked post: the owner wants to know when he'll lose the 4th bar in order to qualify for a warranty replacement.
Not all older LEAFs are fairing so badly. My LEAF is down to 94% capacity after 2 years and 20K miles in New England weather. This is with the 2013 battery pack which has (overall) held up better than the 2011/2012s.
That said, a used LEAF with 30% capacity loss is still a car that can travel 50+ miles one-way, which is more than enough for many commutes. This is why used LEAFs selling for $9K are a bargain.
This "research" is overblown hyperbole based upon tricking the user into falling for a phishing attack or by installing malware. But this big news because this shows that IOT is unsafe!
Now excuse me, I have email from PayPal telling me to update my account, so I have to go click the link they conveniently sent me.
When I read the headline, I was immediately concerned that they might be using an external algorithm! What a disaster that would be! I was relieved to see that the editor pointed out that they are using an internal algorithm. Whew!
My next worry was.... what if they only used one WiFi channel and one sensor!? That would be horrendous! But then I read TFA and saw a quote from CEO Franky Zapata saying "And inside the remote we have three different Wi-Fi channels, plus we have three sensors". Whew! Another design botch happily missed.
They'd release the details on the bug 20 days *after* the patches had been released. Saying that they'll release the details on April 12 on the same day patches will be available is bogus.
The fact that they made not just a catchy name but also a logo leads me to agree they are attention whores.
It's fine to make your project use externally written libraries and depend upon. I do it all the time. I import those modules I need and *have* a copy of them. They can go away in the rest of the world and *my* project won't ever fall over.
The problem here is the NPM model of "don't keep it local, always go back to the remote repository". That's just wrong.
Slashdot Mirror
Would have been funny if that were a Galaxy Note 7 inside the pouch. The Galaxy 7 is just fine.
All of you unhappy Yahoo email users should cancel your accounts and ask for a full refund.
Mod Funny +1.
I used to make tons of money, but then my company switched from paying me with rolls of pennies to checks.
No, they should work in parallel. That way the best design wins, or at least there is an alternative. It is a win-win.
I think you missed the sarcasm.
Ignoring the implied hype in TFA, they quote the original blog post:
"This means that a device with a corrupt boot image or verified partition will not boot
or
will boot in a limited capacity with user consent."
(line breaks added for clarity).
And you test your backup parachute, too.
Yes, 7/13 would have worked much better.
But you can tell someone just didn't get it anymore when they increased the price from $79 to $99 ... rather than $97 which would have fit better.
Are U.S. regulators really actively investigating 25,000 Tesla Model S cars? Are they making appointments with the owners and checking under the hood or something?
This isn't good.
(as I said above, not breaking extensions is the only reason I stay with FireFox)
As I said in the last thread on FireFox... extensions are the only things that keep me using it. If they break extensions, I'll have no reason left to avoid switching.
(Hint to Mozilla: don't break extensions!)
If I could only reliably stop Chrome extensions from auto-updating, I'd have made the switch already. Basically, a dumb forced feature on Google's part is what is helping to keep me using FireFox.
When they break my add-ons the last reason I still use FireFox will evaporate.
(If I could easily disable the auto-update of all Chrome extensions, I'd already be done with FireFox)
I still feel like the EV needs another 20 years or so.
After 2 years and 20K miles in an EV, I will never again have my daily drive be an ICEV.
Forget the lack of tailpipe emissions.
Forget the "clean/green" vehicle (mine is 90% charged from solar).
Forget even the complete lack of engine noise and rumble.
Just focus on the 100% torque when you press the accelerator. That silent "whoosh" as you pull away and leave the other cars behind in their exhaust fumes.
EVs are just more fun to drive.
I don't think there are many LEAFs that "have barely any degradation" after 150k miles. The original battery chemistry in the 2011 and 2012 models (when it was first introduced) have had terrible battery capacity losses, especially in hot climates. It's reported all over at MNL. A typical one: http://mynissanleaf.com/viewto... Many folks with LEAFs that are 4+ years old have been getting warranty replacements of the battery pack.
(In fact, I don't think there are that many LEAFs at 150k miles total yet)
What's the standard for replacing EV batteries?
In the LEAF community, there isn't a standard. You only replace it if the cost of a new pack ($6K) is worth what it adds to the range of your vehicle. Alternately, if it hasn't lived up to the guarantees under the warranty, and you can get a replacement for free. Nissan's warranty is it will hold more than 8 of 12 capacity bars (as shown on the dash); that's not 66%, since the as people have discovered over time the bars are not completely linear. Hence the subject of the above linked post: the owner wants to know when he'll lose the 4th bar in order to qualify for a warranty replacement.
Not all older LEAFs are fairing so badly. My LEAF is down to 94% capacity after 2 years and 20K miles in New England weather. This is with the 2013 battery pack which has (overall) held up better than the 2011/2012s.
That said, a used LEAF with 30% capacity loss is still a car that can travel 50+ miles one-way, which is more than enough for many commutes. This is why used LEAFs selling for $9K are a bargain.
"to trade digital currency ether on its bitcoin exchange"
Is this currency in the ether?
This "research" is overblown hyperbole based upon tricking the user into falling for a phishing attack or by installing malware. But this big news because this shows that IOT is unsafe!
Now excuse me, I have email from PayPal telling me to update my account, so I have to go click the link they conveniently sent me.
Click on the Support FAQ link and get a 404: https://flow.microsoft.com/en-...
Try signing up with gmail: "You entered a personal email address. Please enter your work or school email address to continue."
I know people who use gmail for their work address. Hmmmph.
When I read the headline, I was immediately concerned that they might be using an external algorithm! What a disaster that would be! I was relieved to see that the editor pointed out that they are using an internal algorithm. Whew!
My next worry was .... what if they only used one WiFi channel and one sensor!? That would be horrendous! But then I read TFA and saw a quote from CEO Franky Zapata saying "And inside the remote we have three different Wi-Fi channels, plus we have three sensors". Whew! Another design botch happily missed.
Just one question...
What the bloody hell is IFTTT?
Did you try to look it up? This is "news for nerds," after all.
They'd release the details on the bug 20 days *after* the patches had been released. Saying that they'll release the details on April 12 on the same day patches will be available is bogus. The fact that they made not just a catchy name but also a logo leads me to agree they are attention whores.
It's fine to make your project use externally written libraries and depend upon. I do it all the time. I import those modules I need and *have* a copy of them. They can go away in the rest of the world and *my* project won't ever fall over.
The problem here is the NPM model of "don't keep it local, always go back to the remote repository". That's just wrong.
Agreed! :(
But they are taking away yet another advantage of soylentnews.org.
Since you are an AC, you don't have a password to descrypt.
Alsop's "open letter" is from Sep 30, 2015. The order cancellation happened now?