The bigger problem is the really poor security options available on Android apps with somewhat ridiculously broad security rights. Most apps will ask to read phone identity simply because the need to be able to identify the device on which the app is installed, but the security grant for phone identity gives a whole crapload more than that. Manage accounts is another good one where in order for an app to actually store its own accounts it needs access to all the accounts.
Add to that the fact that Google themselves have been constantly trying to take over your SMS with bloody Hangouts and it's not really that surprising that folks don't really understand the permissions they are granting.
The point is that health information needs to be available to the people who actually need it. In every jurisdiction I have ever worked in your privacy comes second to the doctor, the nurse, catering staff's ability to not kill you. In most places you'll actually have a consent form which will allow them to share this information with additional third parties, but the number of people they don't need that consent for is actually fairly high.
For one, obviously your health insurance company also needs all your medical information, or at least all the medical information you expect them to pay for and they will share that information with whoever they share it with based on the agreement you have with them, which will in all likelihood be any number of people.
The government gets at least deidentified data for the purposes of hospital resourcing and health analysis(that is to say they may not know you went in for a procedure, but they know someone did). If the government is either your hospital provider(public hospital) or your health insurer(public health care) they obviously get significantly more than this as they get the information that those two roles would require.
Law enforcement is slightly more questionable, but its one of those situations where it starts legitimately. As an example, it makes sense that if you are arrested and have a mental illness or other significant impairment that the police who have arrested you are aware of that information so that they can take appropriate steps to ensure that you have the support you need so that your rights are not violated. The difficulty of course is that for a number of reasons which we won't get into here, the police cannot always be trusted to have your best interests at heart.
Your health information is private, but not exactly in the sense that most people believe. In theory we would only share information with the people who need that information when they need that information, but there's really no practical way to make that happen and in general the health care industry tends to be biased towards choices which involve patients not dying as opposed to ones which necessarily fully respect their rights. This is why if you don't have a legally implemented living will or the doctor is not aware of your living will they will resuscitate you against your wishes.
I hate to break it to you, but your health care data isn't anywhere near as private as you think it is.
That's not to say that it's being shared improperly or that it's particularly insecure, merely the fact that the number of people who have perfectly legitimate access to your health care information. We all treat health information like it's some sort of deep dark secret, but all the legislation is quite sensibly based around allowing medical professionals to actually do their jobs. Then of course the people who pay your bills need to know what you were treated for so your insurance company knows. Depending on what you were treated for the state or federal government may or may not be notified and the information they are provided with may or may not be deidentified(for whatever that's worth). You might even see law enforcement or social services notified under certain circumstances, all perfectly legally and perfectly legitimately.
Given that there are about a thousand different mechanisms available to keep you warm which are more energy efficient than an incandescent bulb all of which you can actually turn off when summer comes round, get stuffed.
There are two pieces to the level of punishment a person receives, severity and the number of offenses.
In this case even if you believe what he did was minor, he's done it a crap load of times. If I punch someone in the face I should obviously get a lesser degree of punishment than if I murder someone, but what if I punch 10 people in the face, 100, 1000? If you gave this guy a day for every image on his site it adds up to over 27 years.
I'm fortunately on the coding side these days so I don't have to re-certify all that much anymore, but that also gives me a certain amount of perspective on the impact of change. Even assuming that the information in the issue tracker is complete, which it almost certainly isn't, you're just fooling yourself. The folks who wrote the code don't really understand all the implications of the changes they made and the details in the issue tracker aren't anywhere close. The only thing a change log will ever do is tell you that it will definitely break.
Even if you had full source code and the change sets you wouldn't be able to guarantee no breaking changes. Either something is mission critical in which case it needs to be re-certified or it's not and it probably doesn't.
It's not atrocious, but hardware support for H.264 is ubiquitous. Even the shittiest mobile devices have had it built in for years. You'd be hard pressed to justify a switch even if VP9 was 6.2% better, let alone 6.2% worse.
It might be inflexible design, but it works really really well. A general purpose chip like the one you propose would be several orders of magnitude more expensive, use significantly more power and would probably still deliver inferior results.
The OP's problem is that the developers aren't really part of the IT department. If he had 5 support staff available he'd be over staffed, but that's not what he's got. Having developers do basic support basically shatters their productivity to the extent that the 4 guys they have working in that department are probably actually accomplishing less than 50% of the workload they should be able to manage. The current mess is a lose lose situation.
In actuality 5 people is a very large IT department for an organisation your size. The problem is that you don't actually have 5 people in your IT department. You have 4 people doing LoB development and you doing IT.
It's a classic mistake one my employer also makes but Developers are not, properly speaking, part of the IT department. You hire them for a different reason, you expect different skill sets, and the high interrupt nature of regular support work basically kills their productivity. Claiming they're part of the IT department is like saying that Finance is IT because they're pretty good with excel.
Now the reality may be that when you take all the support crap they're not properly qualified to do away from the developers that you actually find out you need fewer of them, but that's a completely separate issue.
The kinetic energy doesn't disappear, but neither do your steering or brakes, you'll probably lose power steering which is inconvenient and may lose ABS which could also be, but compared to spike strips or running them off the road, it's pretty safe.
Theoretically you shouldn't be so close to the car in front of you that you'd plow into them even if they slammed on the breaks, let alone just lost power, but of course the world is full of tail gating idiots.
That'd be a pretty impressive feat, hitting something as small as a car and only that car with any kind of radio signal let alone this specific frequency from even LEO would be damned difficult if not impossible.If the NSA really wanted to do this for some reason they'd be better off mandating that cars have a remote stop system built into them. Making something that works in a range of a matter of meters work at a range of several miles is not a trivial engineering problem.
It sort of depends what it's used for. Deploying it willy nilly is probably a bad idea, but when compared to spike strips and other mechanisms currently used to stop cars whose drivers don't want to stop them it seems dramatically safer for both the driver and more importantly everyone else around them.
When they toss the first couple jackasses who do it as a joke into federal PMITA prison for the rest of their lives the joke will wear pretty thin. It's not even a case where it'd be a disproportionate response, anyone actually doing this for the lulz needs to be off the street for a long time.
4 train lines and a whole bunch of buses, plus the ferry, and a few other things all operated by different private companies, we have zones as well. Not saying it isn't simpler, but Perth did the whole thing in a year when Sydney gave up, and Victoria seems to have had a bit of a fiasco. The smartrider is one card and it just works, even handles the free transit zones in the CBD, kind of neat really. There are a few nice things about WA, even if the rest of the country forgets we exist sometimes.
Slashdot Mirror
The bigger problem is the really poor security options available on Android apps with somewhat ridiculously broad security rights. Most apps will ask to read phone identity simply because the need to be able to identify the device on which the app is installed, but the security grant for phone identity gives a whole crapload more than that. Manage accounts is another good one where in order for an app to actually store its own accounts it needs access to all the accounts.
Add to that the fact that Google themselves have been constantly trying to take over your SMS with bloody Hangouts and it's not really that surprising that folks don't really understand the permissions they are granting.
The point is that health information needs to be available to the people who actually need it. In every jurisdiction I have ever worked in your privacy comes second to the doctor, the nurse, catering staff's ability to not kill you. In most places you'll actually have a consent form which will allow them to share this information with additional third parties, but the number of people they don't need that consent for is actually fairly high.
For one, obviously your health insurance company also needs all your medical information, or at least all the medical information you expect them to pay for and they will share that information with whoever they share it with based on the agreement you have with them, which will in all likelihood be any number of people.
The government gets at least deidentified data for the purposes of hospital resourcing and health analysis(that is to say they may not know you went in for a procedure, but they know someone did). If the government is either your hospital provider(public hospital) or your health insurer(public health care) they obviously get significantly more than this as they get the information that those two roles would require.
Law enforcement is slightly more questionable, but its one of those situations where it starts legitimately. As an example, it makes sense that if you are arrested and have a mental illness or other significant impairment that the police who have arrested you are aware of that information so that they can take appropriate steps to ensure that you have the support you need so that your rights are not violated. The difficulty of course is that for a number of reasons which we won't get into here, the police cannot always be trusted to have your best interests at heart.
Your health information is private, but not exactly in the sense that most people believe. In theory we would only share information with the people who need that information when they need that information, but there's really no practical way to make that happen and in general the health care industry tends to be biased towards choices which involve patients not dying as opposed to ones which necessarily fully respect their rights. This is why if you don't have a legally implemented living will or the doctor is not aware of your living will they will resuscitate you against your wishes.
I hate to break it to you, but your health care data isn't anywhere near as private as you think it is.
That's not to say that it's being shared improperly or that it's particularly insecure, merely the fact that the number of people who have perfectly legitimate access to your health care information. We all treat health information like it's some sort of deep dark secret, but all the legislation is quite sensibly based around allowing medical professionals to actually do their jobs. Then of course the people who pay your bills need to know what you were treated for so your insurance company knows. Depending on what you were treated for the state or federal government may or may not be notified and the information they are provided with may or may not be deidentified(for whatever that's worth). You might even see law enforcement or social services notified under certain circumstances, all perfectly legally and perfectly legitimately.
Given that there are about a thousand different mechanisms available to keep you warm which are more energy efficient than an incandescent bulb all of which you can actually turn off when summer comes round, get stuffed.
There are two pieces to the level of punishment a person receives, severity and the number of offenses.
In this case even if you believe what he did was minor, he's done it a crap load of times. If I punch someone in the face I should obviously get a lesser degree of punishment than if I murder someone, but what if I punch 10 people in the face, 100, 1000? If you gave this guy a day for every image on his site it adds up to over 27 years.
I'm fortunately on the coding side these days so I don't have to re-certify all that much anymore, but that also gives me a certain amount of perspective on the impact of change. Even assuming that the information in the issue tracker is complete, which it almost certainly isn't, you're just fooling yourself. The folks who wrote the code don't really understand all the implications of the changes they made and the details in the issue tracker aren't anywhere close. The only thing a change log will ever do is tell you that it will definitely break.
Your compliance process is wildly optimistic.
Even if you had full source code and the change sets you wouldn't be able to guarantee no breaking changes. Either something is mission critical in which case it needs to be re-certified or it's not and it probably doesn't.
It's not atrocious, but hardware support for H.264 is ubiquitous. Even the shittiest mobile devices have had it built in for years. You'd be hard pressed to justify a switch even if VP9 was 6.2% better, let alone 6.2% worse.
It might be inflexible design, but it works really really well. A general purpose chip like the one you propose would be several orders of magnitude more expensive, use significantly more power and would probably still deliver inferior results.
Nope, this stuff is spying, this is regular old SIGINT, not metadata collection. You know how you can tell, there's a crap tonne of evidence.
The OP's problem is that the developers aren't really part of the IT department. If he had 5 support staff available he'd be over staffed, but that's not what he's got. Having developers do basic support basically shatters their productivity to the extent that the 4 guys they have working in that department are probably actually accomplishing less than 50% of the workload they should be able to manage. The current mess is a lose lose situation.
In actuality 5 people is a very large IT department for an organisation your size. The problem is that you don't actually have 5 people in your IT department. You have 4 people doing LoB development and you doing IT.
It's a classic mistake one my employer also makes but Developers are not, properly speaking, part of the IT department. You hire them for a different reason, you expect different skill sets, and the high interrupt nature of regular support work basically kills their productivity. Claiming they're part of the IT department is like saying that Finance is IT because they're pretty good with excel.
Now the reality may be that when you take all the support crap they're not properly qualified to do away from the developers that you actually find out you need fewer of them, but that's a completely separate issue.
There are, but there's always a risk of this sort of thing, as has been pointed out delivery drivers aren't immune from theft either.
The kinetic energy doesn't disappear, but neither do your steering or brakes, you'll probably lose power steering which is inconvenient and may lose ABS which could also be, but compared to spike strips or running them off the road, it's pretty safe.
If you're fleeing the police when they use it, your lawsuit will be laughed out of court.
Laser, yes, though with current technology it'd have to be pretty damned big to get enough power to do any damage, radio nope.
Theoretically you shouldn't be so close to the car in front of you that you'd plow into them even if they slammed on the breaks, let alone just lost power, but of course the world is full of tail gating idiots.
Safe is a relative term, compare this to spike strips.
That'd be a pretty impressive feat, hitting something as small as a car and only that car with any kind of radio signal let alone this specific frequency from even LEO would be damned difficult if not impossible.If the NSA really wanted to do this for some reason they'd be better off mandating that cars have a remote stop system built into them. Making something that works in a range of a matter of meters work at a range of several miles is not a trivial engineering problem.
It sort of depends what it's used for. Deploying it willy nilly is probably a bad idea, but when compared to spike strips and other mechanisms currently used to stop cars whose drivers don't want to stop them it seems dramatically safer for both the driver and more importantly everyone else around them.
When they toss the first couple jackasses who do it as a joke into federal PMITA prison for the rest of their lives the joke will wear pretty thin. It's not even a case where it'd be a disproportionate response, anyone actually doing this for the lulz needs to be off the street for a long time.
4 train lines and a whole bunch of buses, plus the ferry, and a few other things all operated by different private companies, we have zones as well. Not saying it isn't simpler, but Perth did the whole thing in a year when Sydney gave up, and Victoria seems to have had a bit of a fiasco. The smartrider is one card and it just works, even handles the free transit zones in the CBD, kind of neat really. There are a few nice things about WA, even if the rest of the country forgets we exist sometimes.
It's how you guys implement stuff over east. The WA equivalent of MyKi actually works.
Moved down in 2004 and they were talking about the imminent shut off then.
Google Glass's resolution is not anywhere near high enough for diagnostic imaging, doing this sort of crap would be illegal in most countries.