The question is, how badly do they want to catch it?
If it's something only a small fraction of the customers actually bother to do, it doesn't dig into their profits too much.
It effectively acts as another form of market segementation. There is a mostly fixed cost for flying an airplane; the marginal cost per passenger is relatively low. So ideally, you would have a paying passenger in every seat. Some passengers are more price sensitive than others, so you want to have the less price-sensitive passengers pay as much as possible, while still providing ways for the more price sensitive passengers to get fill up seats that are still available after that.
People who are willing to go to the trouble of doing this will happen, but you're still making money off of filling seats with paying customers, they're just acting as slightly more price sensitive passengers.
The airlines fluctuate rates for just this reason; they want people to be able to buy tickets at different prices, so price sensitive passengers can go to a little more trouble to book earlier or take bigger risks by flying standby or waiting for the price to go down if it's not appropriate, while less price sensitive passengers will just buy the ticket whenever convenient.
If this were being seriously abused a lot of the time, or there were automated systems which booked trips like this for you, I could see the airlines doing something about it, but if it's just a few people going out of their way to get a slightly better price, it's probably just considered to be part of the whole ticket pricing game.
> If this were being seriously abused a lot of the time, or there were automated systems which booked trips like this for you, I could see the airlines doing something about it, but if it's just a few people going out of their way to get a slightly better price, it's probably just considered to be part of the whole ticket pricing game.
This is pretty much how it's gone so far - sites that have offered anything even resembling an automated service to do bookings like this (and similar other tricks) have been aggressively fought by the airlines legally.[0]
There are also a very small handful of stories per year about some frequent flier getting caught abusing these sorts of fares habitually and getting a trip canceled and/or banned from the airline.
As far as I know my airline flags all sorts of trips like this - but doesn't do anything about it unless it becomes obviously gamed. For example I fly between two cities frequently for week long+ periods, but may need to go home for a weekend during a 2 week stay now and then. I know my airline flags that, but haven't had a problem since it only happens a few times a year out of dozens of total trips.
Event driven programming has been the norm for GUI systems as long as they have existed. I think that the heritage came from Simula in the 1960s, which influenced SmallTalk in the 1970s, which was a major influence for most object-oriented languages and GUI systems since then.
Erlang and JavaScript come much much later on in the evolution of programming languages; Erlang originated in the late 1980s, and JavaScript in 1995.
There were multiple failures here. Let's not put all of the blame on the victim.
This particular location has the sidewalk end on one side, and there is a paved section in the median which looks like it is intended for crossing. There is a small sign that indicates that you should not cross here.
From the video, we can see that while there were street lights on the road, the area in which the apparent crossing existed was completely dark. A pedestrian may not have been able to see the sign indicating that you shouldn't cross here; or even if she did, there are so many roads that are built in pedestrian unfriendly ways that sometimes you just have to cross at unmarked crossings to avoid having to go substantially out of your way.
Additionally, the video shows that the driver was distracted immediately before the crash. While the dash cam video seems to indicate that you can't see the pedestrian until it was probably already too late, human eyes are a lot more sensitive over a greater dynamic range than most video cameras, so there's a good chance that if the driver were paying attention, she would have seen the pedestrian before the car did.
The thing about safety systems and standards are that there should be some redundancy in them. People make mistakes, so you shouldn't have to rely on every actor acting perfectly to remain safe. In this case, there was a failure on many parts leading to a tragedy.
It's definitely worth investigating whether Uber had done enough to ensure that operators will be staying alert during the entire test, and whether Uber had done enough testing before being on open roads of small, possibly moving obstacles on dark parts of the road, like pedestrians, deer, and so on.
I'd also put a good amount of blame on whatever department designed that portion of road and sidewalk.
This is just one quick thing I found on Google Scholar.
Given that this CGM can also act as a regular fingerprick blood glucose monitor during that 12 hour overlap, I think the FDA likely wanted to err on the safer side of using well known and well tested methods for monitoring to avoid any unexpected issues. Is there sufficient evidence of the benefit of CGM over fingerprick tests to believe that this caution could cause actual harm?
> Is there sufficient evidence of the benefit of CGM over fingerprick tests to believe that this caution could cause actual harm?
This is a question you could only ask if you were looking only at the data without understanding the problem at hand.
To answer your question: as a user I'm not sweating Zone B. That doesn't even register as a problem. Zone C is the only zone I care about, and Zone C situations can happen quite easily with fingersticks too. The entire game is imprecise -- every single day I make decisions based on incomplete data. You're going to have a very hard time convincing me that 11 hours of moderately imprecise data is more dangerous than having 11 hours of no data.
You are on HN, and likely reasonably technically inclined. You would probably pay attention to instructions that indicate that it might not be accurate during the first 12 hours of use. You would know to be a bit skeptical of readings that show hypoglycemia during that time, and might either do a fingerstick to check or just ignore it.
There are many users who would not. They might make a rash decision based on that data. If the data is in Zone B a larger percentage of the time in testing, in much wider general use there will likely be cases that weren't caught in clinical trials in which it could land in Zone C.
During this 12 hour calibration window, you can still use fingersticks, which you have to do for calibration purposes with other CGMs anyhow. And it likely would be a fairly minor change for them to support doubling up on sensors, so that you could overlap them in order to avoid the 12 hour window; but that change would require further testing and approval, so for now the 12 hour calibration window is left in. It was only fairly recently approved with this 12 hour calibration window, so I wouldn't be surprised if the company is working on support for pairing two sensors to one device to support doubling up like this.
> During this 12 hour calibration window, you can still use fingersticks, which you have to do for calibration purposes with other CGMs anyhow.
Those aren't comparable situations. With my Dexcom I test in the early afternoon and before bed and that gives me 24 hours worth of extremely reliable information.
Here's a hypothetical: let's say you test and your blood sugar is 150 mg/dl. What does that tell you? Almost nothing. Maybe your sugar was 200mg/dl 15 minutes ago and you're dropping like a rock or it was 100mg/dl 15 minutes ago and you're spiking. Maybe you've been at 150mg/dl for the last two hours. You can't really tell, so you test again in 15 minutes. Let's say it's 100mg/dl -- looks like it is dropping, unless your last reading was on the high side and this one on the low meaning nothing's really changed. So you test again in another 15m and maybe you can start putting together a picture of what's actually happening.
This is a terrible process and only works if you're sitting at home doing nothing. What if you're stuck in traffic or on a crowded subway car? In a meeting at work? At the gym? On a date? In a movie theater? It can become overwhelming quickly and that's when mistakes happen. And remember this is all compounded by your body's biology: you have to think about the food you ate, how much insulin you took and when you took it, when the last time you exercised was, how much stress you're under, etc, etc, etc.
And keep in mind fingersticks don't perform that much better than CGMs. They're still susceptible to error (https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3317395/) and much more susceptible to human error. Failing to wash your hands properly, not drying your hands properly, not letting the alcohol dry completely after a swab, or leaving your strips in a hot car can all cause your readings to be wildly incorrect.
Another thing to note is even if your Libre is off by a huge amount (say 50mg/dl) the trend will still be accurate. Meaning if your blood sugar is constant over an hour the Libre will give you a reading that's also constant. This is extremely important because I'm much more likely to take action on trends (e.g. rising/falling blood sugars) than on individual data points.
You said this in the other thread:
> I would think that 12 hours of having to use a fingerstick during calibration would be preferable to twice a day fingersticks.
I will tell you it is definitively not. Currently Dexcom takes two hours to calibrate and those are the longest two hours of my week. The ability to schedule those two fingersticks is much preferable to 12 hours of radio silence.
> You are on HN, and likely reasonably technically inclined.
Sure. I'm a "good diabetic" but that's the nature of the beast for a disease who's only treatment is constant vigilance. There's a reason why I've never gone into a hypoglycemic coma yet know people my age who are already struggling with neuropathy. The lowest common denominator here is extremely low, and if an error margin of 30mg/dl or a single false reading is going to cause you serious problems you have much greater issues with your diabetes management than your CGM.
Fair enough. You obviously have a lot more skin in this game than I do, I have just done a bit of quick Google Scholar research to see why the FDA might have made the decision that it did, and I'm less familiar with how much the trend vs. the point accuracy is important.
But what it comes down to is, there was something about the accuracy during the first 12 hours that gave the FDA cause for concern. Whether the FDA is overly cautious or not is an open question; I do know that in the US we get worse health outcomes for more money than most other developed countries. How much of that is due to our terrible system for paying for health care, which is privatized but with enough regulatory capture and inefficiency to drive prices way up, and how much of that is due to higher costs and lower access to medication and devices not being available due to excessively stringent regulations from the FDA would be something interesting to study.
I think that the FDA could probably loosen up its regulatory process just a little bit and provide a net benefit. Not sure with how much there is wrong with health policy in the US, and partisan politics around it, that's very likely, however. It would be interesting to see if there have been any studies done on this.
Agreed. 20% margin of error isn't really that relevant to me either.
I don't really care that much if I'm 70mg/dl or 100mg/dl if the line is horizontal. Both values are, roughly, in the "OK Zone" that I just don't care about better precision.
Even if I'm going low, the difference between 50 or 70 isn't nearly as relevant as the rate of change. If I'm going down, but the slope is gentle enough, I know I probably don't need much to get back to normal, while if it's steep going down, I probably need to eat something regardless if I'm 50 or 70, or 80.
> It's the exact same hardware with artificial restrictions added to the software for unclear reasons.
Well, a quick search of Google Scholar turns up at least one citation in which the Freestyle Libre CGM was significantly less accurate in the first day of use than in later days, indicating that it needed more time for proper calibration:
I expect that the differences are based on some actual findings, not just "unclear reasons," but you may have to do some research to find out.
The FDA is notoriously cautious, possibly somewhat excessively so, but there is some good reason for that caution; medication and medical devices can have unexpected behavior and side effects and it can take a lot of long term study to find them. One example of the caution working out well is the Thalidomide case, which was approved in many other jurisdictions but not in the US, and which had significant side effects on fetuses.
What's unclear is not the data but the decisions they made based on the data. Why is that first-day margin of error acceptable for European diabetics but not American ones?
Anecdotally, as a diabetic, the margin of error in that paper is much less scary than going 12 hours without a CGM. Poor data is much better than no data, especially if I know the data is going to be a little questionable the first day. I was completely ready to switch from Dexcom to the Libre until they announced that restriction.
> Why is that first-day margin of error acceptable for European diabetics but not American ones?
Because the FDA is very conservative, in part because that conservatism prevented the thalidomide incident back in the day.
When it comes to novel treatments, or monitoring devices, we don't know what we don't know. The FDA errs on the side of well-tested treatments and devices.
Extra inaccuracy during the first day could lead people to make mistakes that could prove dangerous or fatal. You don't have no data during the first 12 hours, you just have to fall back to the fingerstick method, which the FreeStyle Libre still supports.
It's possible that as more data is gathered in Europe and the US, it could be found that this extra inaccuracy is not harmful, and the European version approved in the US. Or it could be that the company is able to improve the device to improve accuracy in the first 12 hours, and get a new version approved.
It seems to me that other CGMs like the Dexcom require fingerstick calibration at lest twice a day, so I would think that 12 hours of having to use a fingerstick during calibration would be preferable to twice a day fingersticks.
> What's unclear is not the data but the decisions they made based on the data. Why is that first-day margin of error acceptable for European diabetics but not American ones?
The decisions were being made by different people. It's not like the FDA decided that Americans require a 12-hour window but Europeans only need 1. The FDA is just more cautious.
I wasn't being literal. The point is the FDA is overly cautious to the point that they're harming the health of patients. Slight deviations between the US and EU are understandable, 10x is questionable.
I'm sure there are people who would say that European regulators are being permissive to the point that they're harming the health of patients. A lot of women in the US could have benefited from thalidomide while it was being used in Europe, but the FDA was too cautious to allow it.
People will benefit from those extra 11 hours, but they'll also be hurt by the lower accuracy. It's completely reasonable for different people to weigh these costs and benefits differently.
> People will benefit from those extra 11 hours, but they'll also be hurt by the lower accuracy
11 hours without a CGM is a much greater risk than marginally lower accuracy. As a potential user of this system I've been unable to locate research to convince me otherwise.
The definition of manslaughter varies between states, and I am not a lawyer, but in general, criminal manslaughter charges only apply if there is an element of extreme negligence or doing something unlawful (like driving in an illegal manner) and causing a death.
For instance, there are accidents that cause deaths all the time; but they would only be prosecuted as manslaughter if someone were doing something considered inherently unsafe and unlawful.
If you run a red light, and kill someone in the process, it's possible you could be prosecuted for manslaughter, though even then you might not be if there could have been extenuating circumstances (sun in your eyes, etc).
In this case, there would only be a chance of a manslaughter charge if Uber were somehow being particularly negligent. In this case, it sounds like there was a human operator in the car, though the car was in autonomous mode. It's possible that the operator wasn't paying the attention that he or she should have been, or it's possible that even the human operator didn't see the pedestrian in time. It mentions that the pedestrian was crossing outside of any crosswalk, so it's possible that this was a tragic accident of them trying to cross a street with traffic without having been sufficiently careful.
On the other hand, it mentions a bicycle, but also says the victim was walking, which I find odd:
"Elaine Herzberg, 49, was walking outside the crosswalk on a four-lane
road in the Phoenix suburb of Tempe about 10 p.m. MST Sunday (0400 GMT
Monday) when she was struck by the Uber vehicle, police said."
Local television footage of the scene showed a crumpled bike and a Volvo
XC90 SUV with a smashed-in front. It was unknown whether Herzberg was on
foot or on a bike.
Anyhow, it is relatively uncommon for drivers to be charged with manslaughter in this country; they generally have to be doing something quite egregious, like driving drunk or driving at 90 in a 30 mph zone. Most of the time, the response to people being killed in traffic accidents is just that accidents happen.
Unless the operator was being particularly negligent, or there was some serious and known problem with the self driving car but it was put on the road anyhow, I doubt any manslaughter charges will be filed.
Remember, Arizona has explicitly been encouraging the testing of self-driving cars, so I expect that testing a self driving car, with an operator to take over in cases which it can't handle, would not be considered unlawful or extremely negligent. Maybe what the operator was doing could be, but we'd need more information before it would be possible to tell.
> On the other hand, he was a traitor, and he betrayed the trust of a true hero
I don't know. I have a hard time with calling Chelsea Manning a true hero. While some of the information that she leaked was useful in exposing war crimes, there was a lot more that wasn't particularly relevant exposing military abuses, but was used by enemies to track down and kill those who were collaborating with the US.
> in order to put more unaccountable government power in the hands of people like Donald Trump
I'm not sure how what Adrian Lamo did would have given more power to Donald Trump. In fact, it's Wikileaks that ultimately wound up being critical in the election of Donald Trump; by dumping a lot of not particularly noteworthy private campaign emails, but which could be picked through and made to extend some controversies and conspiracy theories around Hillary Clinton, it was one of the key factors in getting Donald Trump elected.
While there has been some good, newsworthy information released on Wikileaks, it seems to have been corrupted by Russian influence, has a lot of alt-right tendencies including antisemitism (https://theintercept.com/2018/02/14/julian-assange-wikileaks... ); I think that overall, it has become a net negative on the world.
From what I can tell, Chelsea Manning meant well, did some good, but also did a lot of damage, including substantially raising Wikiseaks' profile. I think that whether to report the conversation with Manning to the authorities was likely a difficult one, but the concern about leaking significant amounts of non-newsworthy but potentially quite dangerous information was well founded.