That was also my first thought, before I read TFA. Searching on 'safe' in it I find these quotes, and it's not all the hits:
Gathering enough batteries is only the first step to building a DIY powerwall. Every cell then has to be tested—not all are safe enough to be used, several hobbyists told me. Lithium-ion batteries have a limited lifespan: Some laptop batteries harvested end up having too little capacity to be used.
Most hobbyists I spoke to said they don't keep their powerwalls inside their homes for safety reasons or to comply with local regulations.
One of the most frequent topics that came up in my conversations with powerwall makers was safety. Fusing together hundreds of recycled lithium-ion batteries is dangerous, and could cause a fire if done incorrectly.
On the DIYpowerwalls forum, there are dozens of threads dedicated to preventing these massive, homemade electronic devices from catching ablaze. YouTube too is littered with videos warning powerwall builders that their projects are unsafe.
DIY powerwall makers often aren't engineers or electricians. Most, including the most popular—like Jehu Garcia—lack formal training altogether. But they remain mostly unfazed by safety concerns, and said that more recently, makers have pushed each other to engineer more safeguards into their rigs.
So, there is definitely some caution here, and awareness that such pre-used batteries may not be useful enough due to low charge levels.
The real problem here is that the design of the item in question is not for it to be enhanced by things such as internet connectivity, but instead to rely on it (I'm making some assumptions here about Sonos devices specifically as I've never owned one, nor seen one in person).
This is connected to the huge issue with Internet Of Things devices. Far too many manufacturers are designing and building them to rely on functionality, like an internet connection, that should instead only be used to enhance their functionality if it's available.
In both cases the basic functionality should continue even if it's on a desert island powered by a solar panel, far from any network connectivity. If there's a mobile/whatever app to control it then this should continue to support older versions of the API for basic control, even if in the future you can't use such to connect it to a different device, start using it to receive podcasts, or whatever other enhanced functionality a company like Sonos might come up with.
Of course it might be the case that un-supported devices then have security holes and other bugs that were fixed in later revisions of the software/firmware that the owner opted out of. The owner made that choice, so they get to live with the consequences.
And ideally all devices would be using open APIs, if not source, so that third parties could provide the support if the original manufacturer chose to no longer do so.
I came to the comments section to suggest that perhaps the phone companies in question should be doing exactly what you outline Verizon initially did. You'd have thought that after the 2nd time they'd have marked the account as "receiving active attempts to compromise" and gone the long route around (letters to your home or you visiting a store if needs be) to verify the request to activate a different phone on the account.
But apparently if you try enough times you eventually hit a monkey (they're no doubt paid peanuts) who will ignore proper procedure and just do whatever the bad guys want.
As pointed out, in a somewhat tongue in cheek manner, in the source of the the URL, it's possible these GPUs have had non-standard firmware flashed, been OC'd like crazy and otherwise treated in a manner meaning you'd want them to be priced well under MSRP to risk buying one for any purpose. As it is, there may be more of them on the second-hand market now, but they're still being offered at above MSRP.
It's also how I follow many webcomics, some blogs, pre-announced downtime from my ISP (PlusNet), some gaming news sites, and many other things.
I use a local Tiny-Tiny RSS instance to do this (it's what I switched to when Google pulled the plug on Reader).
I also went to the trouble of writing a scraper for Frontier Developments' Forums developer accounts activity so I could have an RSS feed with just the developer posts in it. Many other people make use of that as well.
I hate finding a new site or blog that looks interesting only to find it has no, or only a broken, RSS feed.
From the description the method is detecting which part of the screen you tap on. Thus if you use PIN keypad layout scrambling, such as in LineageOS they still won't know which digit you were tapping each time.
You're aware that the "ctrl-C in bash" functionality that's affected will be "send SIGINT to process", i.e. default kill the current foreground process? It has, as you point out, nothing to do with copy in a "then paste it" sense.
Part of the issue was that one version of 'smart quotes' is only valid in specific windows character sets. Hence the brokenness when it goes through any system using a different character set/locale.
And unless care is taken you end up with sites claiming to be iso-8859-1 or similar in their headers but also including UTF-8 or the windows charset stuff and it just looks horrible with junk where the 'smart quotes' should be.
But he later clarified his comments. “It’s not fair to say ‘stable’. I am not saying she is fine, or not fine,” he told Reuters by telephone. “She is in the ICU.” But in a subsequent interview he said many details about her condition or what caused the medical emergency are unknown.
The loss of the infrastructure, especially the build servers and distribution network, is going to hurt them badly.
Agreed. I tried, and failed, to find anything OTHER than that github account yesterday. No social media accounts, no new blog, no website. I only hope that this is because they're not "ready" yet, and the announcement yesterday was rushed due to pending loss of access to the old site(s).
"developed an annoying permanent yaw to the left, for which calibration has not worked to solve or alleviate"
I had exactly the same fault on my first Saitek X55. After some back and forth I got it replaced under warranty. A few months later that replacement had all the stick buttons stop working unless I twisted it 1/3 left or right. The initial attempt to solve that was a replacement stick handle (it's designed to be removed so you can change the re-centering spring, they supply 4 different ones). THAT handle had the same twist/rudder off-centre issue.
So they replaced the entire thing with an X56, which is mostly an X55 still, just a couple of new analogue thumbsticks replacing the old throttle mouse and one of the stick buttons (although that stick is also clickable as a button still).
I'm not confident, should I actually use it, that the X56 will have no issues before the 2 year warranty period is up.
In other words, I don't think Logitech can actually make the product quality worse.
Someone would have had to have made the choice to have such a long path. I'm pretty sure I don't get anywhere near it. Even one of the longer paths inside my %LOCALAPPDATA% is still under 100 characters. Sure, it's something anyone enabling this will have to be aware of.
As you can see, Microsoft is making this change not only to Win32 software but also to Windows Store applications, as they’re playing an essential role for the future of Windows. Application manifests, which are mostly resources included in every executable file for compatibility reasons, will require apps to add a mention of this new policy, thus making sure that they support a path longer than 260 characters.
This means that unless it’s specified, the change won’t be supported, so apps will need to be updated by developers to benefit from this new behavior.
So, no, this shouldn't cause an issue unless a developer is stupid enough to put the required manifest information in without actually ensuring the code can handle the longer paths/filenames.
Less has always been used in English with counting nouns. Indeed, the application of the distinction between less and fewer as a rule is a phenomenon originating in the 18th century.
So, for over 200 years now then, I think that makes it current usage.
I don't think any alien race is going to succeed in entangling all the particles in the Solar System, but even if they do they won't stay entangled for very long. Remember that a lot of the challenges to making viable quantum computers are preventing the entangled particles from interacting with anything else. If they do they're then no longer entangled.
Someone more able to work in the detail of QM should comment.
Off the top of my head: I guess this is saying that if when they measure in this manner the result comes out in a certain way they know the photon still has an un-collapsed wave function? Presumably if it had a definite state it would be either vertically or horizontally polarised ? I'm still not sure that the wave function of the 'second' particle will actually show locally as having collapsed just because the 'first' particle was measured. It's just that when you perform a full measurement you'll get the complementary value.
As you say... where's the experiment to test this? I'm spouting "currently accepted theory in layman's terms", and it's possible that will be proven incorrect.
Slashdot Mirror
You'd think any business subscriber would also have the sense to subscribe to, and use, at least two such services....
That was also my first thought, before I read TFA. Searching on 'safe' in it I find these quotes, and it's not all the hits:
So, there is definitely some caution here, and awareness that such pre-used batteries may not be useful enough due to low charge levels.
The real problem here is that the design of the item in question is not for it to be enhanced by things such as internet connectivity, but instead to rely on it (I'm making some assumptions here about Sonos devices specifically as I've never owned one, nor seen one in person).
This is connected to the huge issue with Internet Of Things devices. Far too many manufacturers are designing and building them to rely on functionality, like an internet connection, that should instead only be used to enhance their functionality if it's available.
In both cases the basic functionality should continue even if it's on a desert island powered by a solar panel, far from any network connectivity. If there's a mobile/whatever app to control it then this should continue to support older versions of the API for basic control, even if in the future you can't use such to connect it to a different device, start using it to receive podcasts, or whatever other enhanced functionality a company like Sonos might come up with.
Of course it might be the case that un-supported devices then have security holes and other bugs that were fixed in later revisions of the software/firmware that the owner opted out of. The owner made that choice, so they get to live with the consequences.
And ideally all devices would be using open APIs, if not source, so that third parties could provide the support if the original manufacturer chose to no longer do so.
I came to the comments section to suggest that perhaps the phone companies in question should be doing exactly what you outline Verizon initially did. You'd have thought that after the 2nd time they'd have marked the account as "receiving active attempts to compromise" and gone the long route around (letters to your home or you visiting a store if needs be) to verify the request to activate a different phone on the account.
But apparently if you try enough times you eventually hit a monkey (they're no doubt paid peanuts) who will ignore proper procedure and just do whatever the bad guys want.
*sigh*
As pointed out, in a somewhat tongue in cheek manner, in the source of the the URL, it's possible these GPUs have had non-standard firmware flashed, been OC'd like crazy and otherwise treated in a manner meaning you'd want them to be priced well under MSRP to risk buying one for any purpose. As it is, there may be more of them on the second-hand market now, but they're still being offered at above MSRP.
It seemed strange to read this /. story given I'd read the following earlier in the day: https://www.overclock3d.net/ne...
I've read TFA and I can't see where it even says the employees earn more. The closest is this quote:
Seconded, it's a fun mix of police procedural, sci-fi/fantasy arc and a wonderful sense of humour.
For one thing it's how I brows /. stories.
It's also how I follow many webcomics, some blogs, pre-announced downtime from my ISP (PlusNet), some gaming news sites, and many other things.
I use a local Tiny-Tiny RSS instance to do this (it's what I switched to when Google pulled the plug on Reader).
I also went to the trouble of writing a scraper for Frontier Developments' Forums developer accounts activity so I could have an RSS feed with just the developer posts in it. Many other people make use of that as well.
I hate finding a new site or blog that looks interesting only to find it has no, or only a broken, RSS feed.
The ZX81 was my first computer as well, bought 2nd hand with the RAM pack, in March 1982. A strip of Blu-Tac was the solution to RAM pack wobble.
I then moved onto a ZX Spectrum 48k that Xmas, and a string of other computers since.
From the description the method is detecting which part of the screen you tap on. Thus if you use PIN keypad layout scrambling, such as in LineageOS they still won't know which digit you were tapping each time.
Look at a QWERTY keyboard, shift each of those letters one to their left.
You're aware that the "ctrl-C in bash" functionality that's affected will be "send SIGINT to process", i.e. default kill the current foreground process? It has, as you point out, nothing to do with copy in a "then paste it" sense.
Part of the issue was that one version of 'smart quotes' is only valid in specific windows character sets. Hence the brokenness when it goes through any system using a different character set/locale.
And unless care is taken you end up with sites claiming to be iso-8859-1 or similar in their headers but also including UTF-8 or the windows charset stuff and it just looks horrible with junk where the 'smart quotes' should be.
In fact there's now a tweet:
I was looking for an update yesterday and found https://www.theguardian.com/cu...
From her brother:
The loss of the infrastructure, especially the build servers and distribution network, is going to hurt them badly.
Agreed. I tried, and failed, to find anything OTHER than that github account yesterday. No social media accounts, no new blog, no website. I only hope that this is because they're not "ready" yet, and the announcement yesterday was rushed due to pending loss of access to the old site(s).
So not 100% dead, just not using the CyanogenMod brand any more because it's become tainted.
I'd be more comfortable with 2/3rds or more. 51/49 isn't a very clear majority. Why, yes, I voted for the UK to Remain in the EU, why do you ask ?
I had exactly the same fault on my first Saitek X55. After some back and forth I got it replaced under warranty. A few months later that replacement had all the stick buttons stop working unless I twisted it 1/3 left or right. The initial attempt to solve that was a replacement stick handle (it's designed to be removed so you can change the re-centering spring, they supply 4 different ones). THAT handle had the same twist/rudder off-centre issue.
So they replaced the entire thing with an X56, which is mostly an X55 still, just a couple of new analogue thumbsticks replacing the old throttle mouse and one of the stick buttons (although that stick is also clickable as a button still).
I'm not confident, should I actually use it, that the X56 will have no issues before the 2 year warranty period is up.
In other words, I don't think Logitech can actually make the product quality worse.
Someone would have had to have made the choice to have such a long path. I'm pretty sure I don't get anywhere near it. Even one of the longer paths inside my %LOCALAPPDATA% is still under 100 characters. Sure, it's something anyone enabling this will have to be aware of.
From TFA:
So, no, this shouldn't cause an issue unless a developer is stupid enough to put the required manifest information in without actually ensuring the code can handle the longer paths/filenames.
Less has always been used in English with counting nouns. Indeed, the application of the distinction between less and fewer as a rule is a phenomenon originating in the 18th century.
So, for over 200 years now then, I think that makes it current usage.
I don't think any alien race is going to succeed in entangling all the particles in the Solar System, but even if they do they won't stay entangled for very long. Remember that a lot of the challenges to making viable quantum computers are preventing the entangled particles from interacting with anything else. If they do they're then no longer entangled.
Someone more able to work in the detail of QM should comment.
Off the top of my head: I guess this is saying that if when they measure in this manner the result comes out in a certain way they know the photon still has an un-collapsed wave function? Presumably if it had a definite state it would be either vertically or horizontally polarised ? I'm still not sure that the wave function of the 'second' particle will actually show locally as having collapsed just because the 'first' particle was measured. It's just that when you perform a full measurement you'll get the complementary value.
As you say... where's the experiment to test this? I'm spouting "currently accepted theory in layman's terms", and it's possible that will be proven incorrect.