One thing that always leads to confusion is a situation like this - where a developer just disappears without a word.
It's usually considered common courtesy to not fork a project if someone just needs to take a break for a while, or for that person to delegate in their absence.
Here, the person behind the project simply stopped with no warning - and at least for a month or two I'm sure any potential replacements were nervous about stepping on this guy's toes.
The most likely part of a connector to wear out are the springs - which is why in the MicroUSB standard, the springs are in the plug (e.g. the cable) and not the socket.
One issue with this (and many other power meters) is - What is the burden voltage of the ammeter? e.g. how much voltage does it drop.
Meters can often have a burden voltage of 0.1-0.2 volts when measuring currents on the order of an ampere. This might not seem like much, but considering that the original (2012) Nexus 7 drops charge current by approximately 200 mA for every 0.1 volt drop below 5.0 volts - http://forum.xda-developers.com/showthread.php?t=2065404 - 0.2 volts can drop your power by 400 mA (around 2 watts) - Many initial characterizations of Nexus 7 charging severely underreported charging current because the meter's burden voltage caused the device to reduce charging current.
Also, most devices now charge well in excess of 5 watts - so a meter that only shows that you're in the 5-10W range but not where in that range you are isn't very useful.
Last but not least - Forcing a device to pull more than 500 mA from a laptop can damage the laptop. That's a blatent violation of the USB charging standard. Yes, some hosts now support higher charging currents AND the method for reporting this is standardized as part of the USB charging standard - but making a device assume it is always connected to a wall charger could do damage if you connect it to an SDP (Standard Downstream Port) instead of a CDP (Charging Downstream Port).
(Unfortunately, only the very latest devices can successfully detect a CDP...)
Based on that account, the change Tesla SHOULD be making is to be MUCH firmer about the warnings in the case of battery damage. The fire was not in any way sudden - the car was bitching at the driver for *5 minutes* before he pulled over, calmly collected his belongings, and walked away...
(Although, without possibly some extra integrity checking circuitry such as a wire mesh through the battery case, it might not be easy to distinguish battery puncture from other failure modes.)
Yeah. Sometimes projects can wind up in a nightmarish situation in terms of getting new contributors, because the bar to contribution is perceived to be high (even if it might not be).
I used to be a contributor to a fairly large open source project - Overall it was good, but the leads could be downright pricks. They would often trash talk potential contributors, even ones that did show potential. (Sadly, this particular area had a lot of "wannabes" out for glory too...) - While their smacktalk would keep the "wannabes" at bay, it also drove away some exceptional talent.
I was always frustrated by some of these "lone wolf" developers that weren't upstreaming, until myself and a few contributors had a massive disagreement with the project leadership regarding an attempt they made to obtain dual-license commercial rights to a contribution. We started working on founding our own project, and we've found that many of those who I originally (mistakenly) perceived as "lone wolves" and not contributing because something was wrong with them were actually not contributing because there were so many things wrong with our former project and we had been drinking the kool-aid. Quite a few of them have proven to be spectacularly talented and excellent team players.
In addition to this, if you recall some of the recent Lavabit disclosures, we know that large Internet companies have been forced to provide their private SSL certs via secret court orders.
If the NSA/GCHQ have a site's private certs, they can MITM you without you knowing.
Yup. GPU power these days isn't about final pixel fill rates, we've had more than enough for this for a while (although keep in mind that many GPUs render at 4x the screen resolution or more to support antialiasing) - it's about geometry and effects. Most of the focus on new GPU designs is in improving shader throughput.
Yeah, monitor resolutions aren't changing much - but more GPU horsepower means that you can render a given scene in far more detail.
Think of it this way - even GPUs from the early 2000s had no problem rendering Quake3 on a 1920x1200 screen. However, good luck rendering something as detailed as Crysis on GPU/CPU combos released even after five years of additional GPU development compared to things like a GeForce 2 or GeForce 3.
bzzt, wrong. What you describe is perfectly feasible and has been for over a year. Even Sony's last-generation Smartwatch did what you describe while remaining compatible with 22mm watch bands (I believe the Pebble also works with standard 22mm watch bands).
"I think right now, people would be happy with a watch which simply vibrates when the phone in their pocket or backpack gets a text or phone call." - Sony Smartwatch plus WatchIt! - I've been doing this since last October. My watch vibrates and shows the notification for any notification my device receives (except for ones I've filtered out in the WatchIt! app.)
The problem with the Gear is they threw in a ton of unnecessary hardware that drove up bulk and price, while still managing to offer LESS than what the Pebble or last year's Sony SmartWatch do.
What's hilarious is that everyone is tripping over themselves to develop an "awesome" SmartWatch, and still the best SWs on the market are some of the oldest ones (except for Sony's new SW2, which is just a minor tech refresh of the original SW - higher resolution display and a more robust charger connection) which have the most basic hardware on the watch itself - because they're primarily designed as a "second display" for the phone.
The thing is, some of the smartwatches out there (Pebble, Sony's Smartwatches, MetaWatch) are pretty much "dumb" displays for your phone with varying degrees of autonomy - but with most "standalone" functionality trending towards "traditional watch" and not "second smart device".
Most of these smartwatches, because they are "light" in standalone features, are also relatively small and free of bulk. Sony's Smartwatches can be used with a standard watch band, I think so can the Pebble?
The Galaxy Gear has a freaking camera and battery in the watchband and is huge overall. It's just going too far.
I really like the Sony Smartwatch I have (mine was given to me as a gift) and I'd buy the new Smartwatch 2 if I didn't have to remove it whenever I go to work (lots of restrictions on any form of radio transmitter for security reasons in a number of the locations I go frequently.) However the Omate TrueSmart and Galaxy Gear don't appeal to me AT ALL. The Gear is especially dysfunctional - it has tons of weight and bulk compared to other smartwatches, yet despite all of its "autonomy", it is heavily dependent on Samsung Touchwizz hacks in the phone it's communicating with and becomes useless without them. This is vastly different than Sony's products and (I believe) the Pebble, which work with ANY Android device that has Bluetooth and Play Store access.
Except that blimp hydrogen is at very low pressures.
Storing hydrogen at sufficient energy densities for a vehicle is MUCH harder - it's at very high pressures AND hydrogen is notorious for causing metal containers it is stored in to become brittle. There has been some progress in terms of storing it chemically in hydrides, but overall - to store enough hydrogen for a usable vehicle, you're going to have what amounts to a highly pressurized bomb.
Thing is: The virus doesn't directly cause much damage to the pancreas. The theory here is that it causes the immune system to start attacking the pancreas (maybe due to similar antigens between beta cells and the virus???)
Tuning the immune system to more aggressively attack the virus might instead cause Type I diabetes here...
Keep in mind that between some of the more recent Snowden disclosures, and some of the disclosures coming out of Lavabit's shutdown (I think it was Lavabit that was printing SSL private keys in 4-point text???), the NSA can easily MITM these streams without anyone noticing as they are forcing US-based companies to provide them with SSL private keys for just this purpose.
If the password were a salted hash there would at least be some level of protection here, although as long as Apple has a password reset mechanism and a way to recover "old" messages after a reset - it's nearly impossible for them to guarantee that someone who has legal power over Apple (such as the FISA courts) can't read messages.
Many engine fires have almost no involvement from the gasoline or the fuel system - they most commonly occur when an electrical problem interacts with a dirty engine (usually because an oil seal started failing).
Not entirely true. The P/Y code still offers improved accuracy compared to even a non-degraded C/A code due to it being transmitted at 10x the rate of the C/A code. It also allows for dual-frequency operation, permitting ionospheric delay to be corrected for. (There are tricks to using the P/Y code to obtain iono delay even without the decryption keys by cross-correlating the signals on each frequency, but these require a LOT of data collection and processing and I think the receiver has to be stationary.)
That said, modern civilian receivers do such a good job of processing the C/A code that they come close to matching many military receivers which are processing the P/Y code with far older hardware/software algorithms. Systems like WAAS can compensate for a large amount of ionospheric delay even without dual-frequency operation.
Upcoming GPS satellites will permit civilian dual-frequency operation.
Even before Obamacare, insurance premiums were skyrocketing.
My insurance premiums rose about 50% the year before Obama got elected (Company eliminated all choices for healthcare except the worst option) and my copays quadrupled.
I'm actually curious now as to what the exchanges have to offer.
I'd rather have a nuke plant a mile away than gas drilling operations commencing anywhere upstream on the Susquehanna, even if I pay more, because with gas I know I'll be paying longterm for the contamination. Nuclear's track record per unit of energy produced is stellar compared to the track record of constant failure and environmental contamination the gas drillers have established so far.
And go figure, you're posting this drivel on an article about a device specifically targeted at Type I (autoimmune) diabetics... A device which, among other benefits, will help a Type I diabetic manage weight better by enabling them to maintain tight bloodsugar control without excessive hypoglycemia incidents. (Common problem for a Type I - eat a meal, take insulin, and then exercise without properly reducing your mealtime insulin dose to compensate. End result - hypoglycemia which requires you to eat more. A CGMS makes it a lot easier to properly plan insulin deliveries without overcorrections/oscillations.)
Yup, which is why it looks like this particular new unit is only automated in terms of avoiding the most dangerous situation - hypoglycemia, and it probably only triggers when it detects a falling trend that is dangerously low. (e.g. alarm at 60 mg/dl and falling, shutdown at 50 and falling maybe? Although that might be too late, it's better than continuing injection.)
I've been a Type I for almost two decades (maybe two? I need to figure out how long ago eighth grade was...) - This unit addresses one of the primary reasons I have avoided pumps until now.
Interestingly enough, EZ-Pass devices installed in rental vehicles do EXACTLY this to allow the renter choice of whether to use EZ-Pass or normal tolls.
Slashdot Mirror
You didn't RTFA - this new "breakthrough" depends on the availability of brine that is significantly more concentrated than the ocean.
Basically this "breakthrough" provides zero benefit compared to existing technology when used for ocean water.
It requires saline that is MUCH more concentrated than seawater... So you need to somehow concentrate the saltwater before using it.
Although this might allow for some rather unconventional solar power projects - feeding brine from salt concentration ponds might be workable here.
One thing that always leads to confusion is a situation like this - where a developer just disappears without a word.
It's usually considered common courtesy to not fork a project if someone just needs to take a break for a while, or for that person to delegate in their absence.
Here, the person behind the project simply stopped with no warning - and at least for a month or two I'm sure any potential replacements were nervous about stepping on this guy's toes.
The most likely part of a connector to wear out are the springs - which is why in the MicroUSB standard, the springs are in the plug (e.g. the cable) and not the socket.
One issue with this (and many other power meters) is - What is the burden voltage of the ammeter? e.g. how much voltage does it drop.
Meters can often have a burden voltage of 0.1-0.2 volts when measuring currents on the order of an ampere. This might not seem like much, but considering that the original (2012) Nexus 7 drops charge current by approximately 200 mA for every 0.1 volt drop below 5.0 volts - http://forum.xda-developers.com/showthread.php?t=2065404 - 0.2 volts can drop your power by 400 mA (around 2 watts) - Many initial characterizations of Nexus 7 charging severely underreported charging current because the meter's burden voltage caused the device to reduce charging current.
Also, most devices now charge well in excess of 5 watts - so a meter that only shows that you're in the 5-10W range but not where in that range you are isn't very useful.
Last but not least - Forcing a device to pull more than 500 mA from a laptop can damage the laptop. That's a blatent violation of the USB charging standard. Yes, some hosts now support higher charging currents AND the method for reporting this is standardized as part of the USB charging standard - but making a device assume it is always connected to a wall charger could do damage if you connect it to an SDP (Standard Downstream Port) instead of a CDP (Charging Downstream Port).
(Unfortunately, only the very latest devices can successfully detect a CDP...)
Based on that account, the change Tesla SHOULD be making is to be MUCH firmer about the warnings in the case of battery damage. The fire was not in any way sudden - the car was bitching at the driver for *5 minutes* before he pulled over, calmly collected his belongings, and walked away...
(Although, without possibly some extra integrity checking circuitry such as a wire mesh through the battery case, it might not be easy to distinguish battery puncture from other failure modes.)
Yeah. Sometimes projects can wind up in a nightmarish situation in terms of getting new contributors, because the bar to contribution is perceived to be high (even if it might not be).
I used to be a contributor to a fairly large open source project - Overall it was good, but the leads could be downright pricks. They would often trash talk potential contributors, even ones that did show potential. (Sadly, this particular area had a lot of "wannabes" out for glory too...) - While their smacktalk would keep the "wannabes" at bay, it also drove away some exceptional talent.
I was always frustrated by some of these "lone wolf" developers that weren't upstreaming, until myself and a few contributors had a massive disagreement with the project leadership regarding an attempt they made to obtain dual-license commercial rights to a contribution. We started working on founding our own project, and we've found that many of those who I originally (mistakenly) perceived as "lone wolves" and not contributing because something was wrong with them were actually not contributing because there were so many things wrong with our former project and we had been drinking the kool-aid. Quite a few of them have proven to be spectacularly talented and excellent team players.
In addition to this, if you recall some of the recent Lavabit disclosures, we know that large Internet companies have been forced to provide their private SSL certs via secret court orders.
If the NSA/GCHQ have a site's private certs, they can MITM you without you knowing.
Yup. GPU power these days isn't about final pixel fill rates, we've had more than enough for this for a while (although keep in mind that many GPUs render at 4x the screen resolution or more to support antialiasing) - it's about geometry and effects. Most of the focus on new GPU designs is in improving shader throughput.
Yeah, monitor resolutions aren't changing much - but more GPU horsepower means that you can render a given scene in far more detail.
Think of it this way - even GPUs from the early 2000s had no problem rendering Quake3 on a 1920x1200 screen. However, good luck rendering something as detailed as Crysis on GPU/CPU combos released even after five years of additional GPU development compared to things like a GeForce 2 or GeForce 3.
bzzt, wrong. What you describe is perfectly feasible and has been for over a year. Even Sony's last-generation Smartwatch did what you describe while remaining compatible with 22mm watch bands (I believe the Pebble also works with standard 22mm watch bands).
"I think right now, people would be happy with a watch which simply vibrates when the phone in their pocket or backpack gets a text or phone call." - Sony Smartwatch plus WatchIt! - I've been doing this since last October. My watch vibrates and shows the notification for any notification my device receives (except for ones I've filtered out in the WatchIt! app.)
The problem with the Gear is they threw in a ton of unnecessary hardware that drove up bulk and price, while still managing to offer LESS than what the Pebble or last year's Sony SmartWatch do.
What's hilarious is that everyone is tripping over themselves to develop an "awesome" SmartWatch, and still the best SWs on the market are some of the oldest ones (except for Sony's new SW2, which is just a minor tech refresh of the original SW - higher resolution display and a more robust charger connection) which have the most basic hardware on the watch itself - because they're primarily designed as a "second display" for the phone.
The thing is, some of the smartwatches out there (Pebble, Sony's Smartwatches, MetaWatch) are pretty much "dumb" displays for your phone with varying degrees of autonomy - but with most "standalone" functionality trending towards "traditional watch" and not "second smart device".
Most of these smartwatches, because they are "light" in standalone features, are also relatively small and free of bulk. Sony's Smartwatches can be used with a standard watch band, I think so can the Pebble?
The Galaxy Gear has a freaking camera and battery in the watchband and is huge overall. It's just going too far.
I really like the Sony Smartwatch I have (mine was given to me as a gift) and I'd buy the new Smartwatch 2 if I didn't have to remove it whenever I go to work (lots of restrictions on any form of radio transmitter for security reasons in a number of the locations I go frequently.) However the Omate TrueSmart and Galaxy Gear don't appeal to me AT ALL. The Gear is especially dysfunctional - it has tons of weight and bulk compared to other smartwatches, yet despite all of its "autonomy", it is heavily dependent on Samsung Touchwizz hacks in the phone it's communicating with and becomes useless without them. This is vastly different than Sony's products and (I believe) the Pebble, which work with ANY Android device that has Bluetooth and Play Store access.
Except that blimp hydrogen is at very low pressures.
Storing hydrogen at sufficient energy densities for a vehicle is MUCH harder - it's at very high pressures AND hydrogen is notorious for causing metal containers it is stored in to become brittle. There has been some progress in terms of storing it chemically in hydrides, but overall - to store enough hydrogen for a usable vehicle, you're going to have what amounts to a highly pressurized bomb.
Thing is: The virus doesn't directly cause much damage to the pancreas. The theory here is that it causes the immune system to start attacking the pancreas (maybe due to similar antigens between beta cells and the virus???)
Tuning the immune system to more aggressively attack the virus might instead cause Type I diabetes here...
Keep in mind that between some of the more recent Snowden disclosures, and some of the disclosures coming out of Lavabit's shutdown (I think it was Lavabit that was printing SSL private keys in 4-point text???), the NSA can easily MITM these streams without anyone noticing as they are forcing US-based companies to provide them with SSL private keys for just this purpose.
If the password were a salted hash there would at least be some level of protection here, although as long as Apple has a password reset mechanism and a way to recover "old" messages after a reset - it's nearly impossible for them to guarantee that someone who has legal power over Apple (such as the FISA courts) can't read messages.
Yeah. Many aircraft use beryllium parts because it's lightweight.
You do NOT want to be anywhere near a fire that involves beryllium...
Many engine fires have almost no involvement from the gasoline or the fuel system - they most commonly occur when an electrical problem interacts with a dirty engine (usually because an oil seal started failing).
"But why ARE we paying for France to buy drones?"
Most likely (this is how FMS works) - France paid the DoD, then the DoD paid a domestic contractor.
So they're not financially helping France here - they're being a middleman and almost surely taking a cut.
Not entirely true. The P/Y code still offers improved accuracy compared to even a non-degraded C/A code due to it being transmitted at 10x the rate of the C/A code. It also allows for dual-frequency operation, permitting ionospheric delay to be corrected for. (There are tricks to using the P/Y code to obtain iono delay even without the decryption keys by cross-correlating the signals on each frequency, but these require a LOT of data collection and processing and I think the receiver has to be stationary.)
That said, modern civilian receivers do such a good job of processing the C/A code that they come close to matching many military receivers which are processing the P/Y code with far older hardware/software algorithms. Systems like WAAS can compensate for a large amount of ionospheric delay even without dual-frequency operation.
Upcoming GPS satellites will permit civilian dual-frequency operation.
Actually, Romney already did what you're suggesting. It worked well in Massachusetts.
Yes, that's right - Obamacare was based on Romneycare.
Even before Obamacare, insurance premiums were skyrocketing.
My insurance premiums rose about 50% the year before Obama got elected (Company eliminated all choices for healthcare except the worst option) and my copays quadrupled.
I'm actually curious now as to what the exchanges have to offer.
Yup. I live in upstate New York.
I'd rather have a nuke plant a mile away than gas drilling operations commencing anywhere upstream on the Susquehanna, even if I pay more, because with gas I know I'll be paying longterm for the contamination. Nuclear's track record per unit of energy produced is stellar compared to the track record of constant failure and environmental contamination the gas drillers have established so far.
And go figure, you're posting this drivel on an article about a device specifically targeted at Type I (autoimmune) diabetics... A device which, among other benefits, will help a Type I diabetic manage weight better by enabling them to maintain tight bloodsugar control without excessive hypoglycemia incidents. (Common problem for a Type I - eat a meal, take insulin, and then exercise without properly reducing your mealtime insulin dose to compensate. End result - hypoglycemia which requires you to eat more. A CGMS makes it a lot easier to properly plan insulin deliveries without overcorrections/oscillations.)
Yup, which is why it looks like this particular new unit is only automated in terms of avoiding the most dangerous situation - hypoglycemia, and it probably only triggers when it detects a falling trend that is dangerously low. (e.g. alarm at 60 mg/dl and falling, shutdown at 50 and falling maybe? Although that might be too late, it's better than continuing injection.)
I've been a Type I for almost two decades (maybe two? I need to figure out how long ago eighth grade was...) - This unit addresses one of the primary reasons I have avoided pumps until now.
Wasn't there a terrorist attack elsewhere in Africa a few months ago where the people involved were tweeting about it?
May have been the same organization - I think it was an attack in Mogadishu?
Interestingly enough, EZ-Pass devices installed in rental vehicles do EXACTLY this to allow the renter choice of whether to use EZ-Pass or normal tolls.