At least blame the right faceless government agency. Inflation money hasn’t been actually printed on paper since perhaps before Jimmy Carter. The Federal Reserve just shifts the bits a couple of spots towards MSB on various too big to fail entities’ bank account records. Same effect, just less of that messy ink to deal with...
There’s a very simple fix for this and other “seize your refund” enforcement issues like Obamacare fines.
Ensure your withholding amounts are set as low as statutorily permissible. Squirrel away sufficient cash to be able to pay any additional amounts owed. On April 15th, you send the government a check for the difference, having kept any interest earned throughout the year. Much better than having let the government keep your money interest free all year, then maybe not even give it back to you because they decide they don’t have to.
then I’m VERY sure that you had a LOT of other security flaws unpatched on your servers.
Transaction malleability is a lot different than having an unpatched OpenSSL on your server or something. Security bugs in unpatched software are a thing that are well-understood by sysadmins and security researchers. Weaknesses in the cryptography underlying Bitcoin are truly understood by perhaps a handful of people on the Earth at this time. It would be nice to presume that an organization positioning itself as an exchange for Bitcoin would have that expertise on staff, but you can’t meaningfully compare the two things. Additionally, this isn’t an unpatched security flaw where upgrading to Bitcoin 1.1 would have fixed the issue. It’s a weakness inherent to the Bitcoin protocol which may or may not be able to be repaired without invaliding all existing BTC transactions.
The research in TFA seems to confirm the existing belief that this attack is very unlikely to pull off in the real world, therefore the severity of it seems low.
there are SURE to be a LOT more hidden flaws bleeding bitcoins like crazy
Really? Please do share your cryptography credentials that qualify you to analyze the Bitcoin protocol and arrive at this certainty. Unless you’re prepared to present “a meaningful interpretive dance that compares and contrasts cache-based timing, and other side channel attacks and their countermeasures,” (http://www.moserware.com/2009/09/stick-figure-guide-to-advanced.html), I rather doubt you’ve got the background to comment meaningful on undiscovered weaknesses in the Bitcoin protocol.
You don’t seem to understand the purpose of Bitcoin, or what a Ponzi scheme is...
... Or what money is. Fiat currency has no value other than to 1) Pay your taxes, and 2) Conduct business with others who mutually agree that said currency has an effective value. Within about 15 miles of me, there’s at least one pizza joint and one car dealer that will accept Bitcoin in exchange for their products.
No argument that BTC is less widely accepted than most other currencies, but don’t conflate wide acceptance of a currency with it having an intrinsic value. At the end of the day, one dollar bill is worth exactly what I can exchange it for, no more (with the possible exception of it having some *limited* intrinsic value in terms of heating/energy should it prove more valuable to simply set fire to it rather than exchange it for some other fuel source). I could if I so wished exchange BTC for pizza or a car, so that’s value in my book.
Granted, BTC’s volatility in terms of value makes it a risky choice as “money,” but it isn’t worthless.
you lose your right to claim to be pro free speech after advocating a boycott
This is so utterly false, I don’t even know where to start. Eich had every right to speak in support of Prop 8 or anything else he might like to, but I also have the right to express my distaste of his bigoted ideas by withholding my support of any organization which he runs.
I’ll defend to the death his right to *say* whatever he likes, but there’s no reason in the world I need to do business with someone whose views I consider to make them a reprehensible human being. The idea that not giving someone your money is equivalent to silencing their right to free speech strikes me as an incredible sense of entitlement. There’s nothing about the right to free speech that entitles you to say anything you want without consequences of having said it. Freedom of speech means the government can’t silence you, but that protection begins and ends with the *government*. How any individual chooses to interact with you as a result of *your* free speech is as much a matter of *their* free speech as you being free to say it in the first place.
There’s nothing about supporting free speech that requires me to also support every person who speaks an opinion I disagree with. By your logic, I should vote for a politician whose views I disagree with because if I voted against him, I’d be infringing on his right to free speech. That’s preposterous and misguided and flat out foolish.
Calling support for a multimeter? What planet are you from? Short of it breaking and needing a replacement under warranty, you plug it in, spin the dial to the mode you want, and away you go.
Do people call Sears for tech support on a Craftsman wrench? I’ll grant a multimeter is *slightly* more complicated of a tool, but really only slightly to someone who’s the least bit experienced in that area of tech. I think I got my first MM when I was six years old. Took Dad about 10 minutes to show me how to measure voltage and resistance, and that was when you had to set the range yourself.
As someone who doesn’t root my iPhone and would prefer nobody else do so, there is a key advantage to me to Apple’s preventing downgrades of the iOS version on a device. If an old release contains a security flaw that would allow access to secured data on the device which a newly patched version would prevent, allowing an install of the older version would allow an attacker to downgrade, exploit the bug, and extract data from my device. Jailbreaking a device amounts to removing all effective protections in terms of access security that the device may provide for data stored on it. Many (but certainly not all) jailbreaks exploited vulnerabilities at an OS-software level, and patching those vulnerabilities made it impossible to jailbreak an updated device. That doesn’t apply to the devices that had exploitable vulnerabilities in the ROM boot block of course; and that was an issue on several of the devices.
Ensuring that older vulnerable versions cannot be installed on my device is a security feature to me. It’s also a limitation of my freedom, and it makes the device less “mine.” Looking at the alternatives and what I *personally* want to do with (and want done to) my iDevice, I’ve decided this is a better option for me. I’m not prevented from using the device in the manner for which it was marketed, and potentially some would-be attackers are thwarted from extracting data from my device. Certainly there’s more that I could potentially do with the device in terms of home-rolled firmware, but I’m at the point where I really and truly don’t want to “hack” on my cell phone with all the potential issues that come with that (battery drain, instability, insecurity, etc.). I want to pull my iPhone out of my pocket and make a phone call. Apple’s update policy doesn’t prevent that, and their QA is reasonably good in terms of the battery drain and related issues being a relative minority of their users. I’m willing to take the risk of updating.
In a perfect world, boot loader security might be accomplished with a key that’s under my control rather than under Apple’s. Maybe a card / USB stick in the box with the private key for the boot loader and a “lose this at your peril” warning. The device could take official Apple updates without the key (better if that was a configurable option), or take any software with the key. Of course the support nightmare that would ensue would be insane, and Apple would never do it as it’s a definite UX detraction for any but the most geeky of buyers.
RMS’ great vision of full control of all of our hardware is a nice one, but in the mean time I’m content to enter compromises with companies that have reasonable histories of “not being evil” in the areas which directly effect me. I’m good with Apple and how they handle their iThing’s. Sure that could change, and I keep my data off-device in formats that would allow me to convert and go elsewhere if need be. Beyond that, I’m not going to lose sleep over the fact that I’m stuck with one-way upgrades of iOS. It’s one of those arguments that I can agree with ideologically, but in terms of practicality and getting things done, it doesn’t negatively effect me.
Upgrading is always an option. They’ve just decided that the (odds X cost) of potential security issues from not upgrading is lower than the cost of upgrading all of the apps and systems.
Were I an IT-type person in such a company, I’d want hardcopy signed by C-level management expressing it in those exact terms. Something to the effect of, “We acknowledge that there are significant known vulnerabilities in our operating system and browser, that there is a significant likelihood of additional vulnerabilities, particular after the vendor’s end-of-life for patches. We nonetheless choose to run this vulnerable platform in lieu of incurring the costs to upgrade. We acknowledge that IT has made us aware of these risks and absolve IT of any responsibility for security incidents which occur as a result of this choice.”
Good luck getting that of course, but I’d be looking for a new job either way...
In my experience, when I need That Part on a Sunday afternoon, I’m not likely to get it from Radio Shack either. There are times I’d be willing to pay the retail price premium to get what I need. It’s a moot point when they don’t even stock basic discreet components or plugs half the time.
Why do you assume governments want to discredit Bitcoin?
An “anonymous” currency that actually carries a permanent record of every transaction ever conducted in it? Sounds like a law enforcement wet dream. I wonder if they’ll consider it worth the work* and the wider understanding of BTC’s true “anonymous” nature to work backwards and de-anonymize many of the BTC wallet ID’s used to make Silk Road purchases. I’d be shocked if most buyers took the necessary steps to make their wallet ID’s completely untraceable to them.
* And it’s only “work,” assuming that the nature of NSA’s various data capture and analysis programs haven’t been watching the blockchain from day one and correlating & de-anonymizing every wallet ID as they went. Wouldn’t really take that much given the scope of the data capture they seem to have. All it takes is one browser submit of your wallet ID through the same browser or even IP that your Amazon or Google or whatever cookie has been seen from, and they have a name to go with the ID.
it’s provided by payments the banks make to be FDIC insured.
This is true only so long as the Office of Thrift Supervision does its job effectively, and in recent history it’s been doing a piss poor job. OTS is supposed to seize a failing bank prior to the value of its assets dropping below the sum of FDIC insured deposits. The sale of the bank and its assets (loans it owns essentially), whole or in pieces to other banks should equal or exceed the amount of insured funds, and depositors are made whole without tax payers taking a bath. Usually the obligation of the deposits is assumed by the purchasing banks, so any eventual withdrawals come from the new bank’s assets.
The problem is when OTS waits too long, and a failing bank has slipped past the point where it has the assets to cover its deposits. In that case, any bank purchasing the assets and liabilities would insist on either a discount on the price (to offset the value of the deposits they would eventually have to pay back) or outright cash as part of the transaction to ensure they’re not taking a loss in the transaction. At that point, the money comes from the FDIC fund to make up the difference. FDIC is “insurance” in the sense that banks pay into it, but it’s backed by the full faith and credit of the United States of America. That means if the fund comes up short, every penny past that point comes directly out of the tax payers.
The FDIC insurance fund is maintained at a very low percentage of the overall deposits at risk. I think the requirement was raised to 1.35% in 2010, but that target isn’t required to be reached until 2020. The number of banks that failed as a result of various sub-prime related issues put a strain on the fund because OTS consistently waited until the banks were deeply in the red before acting. My cynical self says they were playing the “wait & hope” game, hoping the banks managed to ride it out without going under so they wouldn’t need to close them. Didn’t work out so well for a lot of banks.
So it’s true that FDIC insurance isn’t provided by the government, at least up to the point the insurance fund holds. Pat that point, any shortfalls are paid for by the government, IE You.
If there’s any suit available to this actress, it’s against the producer/director/etc. of the film for misrepresentation. There’s no conceivable way this should be a copyright case. There’s no way that anyone who was paid for appearing in it by the eventual rights holder (producer/etc.) should retain any right to issue take down demands contrary to the will of the actual owner of the copyright.
Short of a contract that stated she retained any rights (doubtful), then I can’t see how this was anything other than work for hire with associated assignment of copyright.
Susan Sarandon supposedly hated Rocky Horror and regretted ever appearing in it. Shall we tear down all the copies of that?
If nothing else, judges in cases like this should take to heart that once something is published on the Internet, it’s forever. I know no judge wants to hear, “You don’t have the power to do that, your Honor,” but the fact of the matter is there’s no way to ever remove something like this from public view.
If you knew with complete assurance that the first crew would be lost if they attempted to land without repair, then it would likely be worth the risk to a second crew to mount a rescue.
If on the other hand, there’s only some chance that the first crew would be lost attempting to land, then working that risk into the risk to the second crew is reasonable. IE if there’s a 10% chance that there might have been trouble landing (and it sounds like the foam strikes leading up to Columbia’s trouble were in fact common, so could be considered low-risk) then it’s not unreasonable to decide that the risk of the second crew is an unreasonable risk. Consider also that the risk to this second crew for an accelerated launch process would likely have been FAR greater than a “normal” shuttle launch (assuming it can be said there’s anything “normal” about strapping a bomb to your ass and fleeing the planet...)
If there’s a very high chance of failure of the original crew’s landing, then the additional risk might be worth it. If not, then you really are doubling down and risking losing two crews. It’s entirely plausible that due to the corners cut for an accelerated launch Atlantis could have exploded during launch, leaving Columbia to still take their chances landing with a damaged wing.
Armchair quarterbacking is easy. Saying they should have risked a second crew *now*, knowing that it’s an impossibility and that your assertion that the risk is reasonable will never be tested is also easy. Being left to make that call in the moment, knowing that you could be sending a second shuttle crew to their deaths trying to help another crew that might not even need the help the first place. Little bit harder to live with that one...
The loss of the Columbia crew is a tragedy, but looking back based on this report, it doesn’t seem like the way it was handled was unreasonable.
people move to the outskirts of a city so their kids don’t have to fear getting mugged
Citation needed... Cost issues are certainly valid, but I’d have little safety concern working and allowing my child to grow up in New York City as an example. I’m sure there are cities in the US I wouldn’t say that for, and I suspect there are cities that I’d feel even safer than NYC, but there’s no reason you need to move out to the suburbs to be “safe”.
Safety is relative anyways. If in fact your odds of getting mugged in the suburbs are lower than in the city, that’s nice, but your odds of dying in a hurtling fireball of a car wreck on the way to/from work are immensely higher. Pick your poison...
Eschewing useful tools out of fear of being a “bad” programmer makes you a bad programmer.
It doesn’t matter how deep your knowledge of the language or environment is. A well configured IDE will allow you to complete your job more quickly. It makes research navigating around a codebase much more straight forward. There’s no reason to do textual searches in a simple text editor when an IDE can parse the language and show you actual references to a symbol, not just things that happen to be named similarly.
All of the “uber” programmers I’ve known who avoid IDE’s are universally less effective than even mediocre programmers who use tools to make their jobs easier. The type of programmer who avoids tools out of the belief that doing it “by hand” is better generally waste more time tweaking their environment, going on architecture astronaut treks, and generally doing everything they can that isn’t actually writing code that gets the job at hand done.
Car analogy: You can change a tire with a wrench, and maybe a long piece of pipe to use for leverage. Or you can use a pneumatic impact driver and get the job done quicker, with less damage to the bolts, and put back together tighter (less chance of bolts loosening, tires rolling down the road without you). Any mechanic who tried to hold themselves up as a hero for doing it the hard way would be laughed out of the shop (and probably out of a job).
Be a Software Simian. Not using tools just makes you a dumb code monkey.
It’s true Apple drops new iOS major versions for older devices. They’re usually pretty good about it, but as an owner of the original iPad, I’d say they do occasionally cut devices off a bit prematurely...
That said, Apple has in the past issued patch releases of older iOS major versions to fix security issues on devices that couldn’t take the latest major iOS version.
If my memory serves, iOS 3.1.3 was a case of that where the original iPhone (2G) wouldn’t get iOS 4 but they did back port security fixes for it.
Really? Let us know how that works out... Maybe you should read that big agreement you have to click “Agree” to when you activate a phone. All liability for software bugs, known or unknown is disclaimed.
You have zero chance of seeing a penny from any such attempt.
I do have a right to be sure vehicles have a minimum safety standard.
This seems easy to fix. Most (all?) states have some sort of annual safety inspection requirement for keeping a car on the road. Generally these safety checks include connecting to the car computer’s diagnostic port to read emissions related information to ensure the car complies with the pollution requirements that applied to its model year.
Add as a requirement of those checks that plugging into the computer also checks software versions and compare that against a list of updates the respective manufacture has deemed critical for continued safety. A passing safety inspection requires that the car’s systems be up to date with all critical software updates.
Flash is native executable code. It’s not encumbered by any sandboxing function in the browser. That’s by design.
Browser plugins are intended to be allowed unfettered access to the system so that they can accomplish tasks not normally possible within a browser. The only sandbox provided by most browsers relates specifically to JavaScript, and as far as I can tell, this is unrelated to JavaScript at all.
It’s possible that an OS level sandbox beyond the browser (like OS X AppSandbox, Linux AppArmor, SELinux, etc.) might be able to contain an exploit within Flash, limiting it to a user account or a directory; but that would take some careful crafting in terms of OS sandbox configuration. None of the major platforms are configured to do anything close to my knowledge.
tl;dr: Your sandbox can’t help you here. Update Flash or you’re toast.
Slashdot Mirror
At least blame the right faceless government agency. Inflation money hasn’t been actually printed on paper since perhaps before Jimmy Carter. The Federal Reserve just shifts the bits a couple of spots towards MSB on various too big to fail entities’ bank account records. Same effect, just less of that messy ink to deal with...
There’s a very simple fix for this and other “seize your refund” enforcement issues like Obamacare fines.
Ensure your withholding amounts are set as low as statutorily permissible. Squirrel away sufficient cash to be able to pay any additional amounts owed. On April 15th, you send the government a check for the difference, having kept any interest earned throughout the year. Much better than having let the government keep your money interest free all year, then maybe not even give it back to you because they decide they don’t have to.
Transaction malleability is a lot different than having an unpatched OpenSSL on your server or something. Security bugs in unpatched software are a thing that are well-understood by sysadmins and security researchers. Weaknesses in the cryptography underlying Bitcoin are truly understood by perhaps a handful of people on the Earth at this time. It would be nice to presume that an organization positioning itself as an exchange for Bitcoin would have that expertise on staff, but you can’t meaningfully compare the two things. Additionally, this isn’t an unpatched security flaw where upgrading to Bitcoin 1.1 would have fixed the issue. It’s a weakness inherent to the Bitcoin protocol which may or may not be able to be repaired without invaliding all existing BTC transactions.
The research in TFA seems to confirm the existing belief that this attack is very unlikely to pull off in the real world, therefore the severity of it seems low.
Really? Please do share your cryptography credentials that qualify you to analyze the Bitcoin protocol and arrive at this certainty. Unless you’re prepared to present “a meaningful interpretive dance that compares and contrasts cache-based timing, and other side channel attacks and their countermeasures,” (http://www.moserware.com/2009/09/stick-figure-guide-to-advanced.html), I rather doubt you’ve got the background to comment meaningful on undiscovered weaknesses in the Bitcoin protocol.
No argument that BTC is less widely accepted than most other currencies, but don’t conflate wide acceptance of a currency with it having an intrinsic value. At the end of the day, one dollar bill is worth exactly what I can exchange it for, no more (with the possible exception of it having some *limited* intrinsic value in terms of heating/energy should it prove more valuable to simply set fire to it rather than exchange it for some other fuel source). I could if I so wished exchange BTC for pizza or a car, so that’s value in my book.
Granted, BTC’s volatility in terms of value makes it a risky choice as “money,” but it isn’t worthless.
You presume much. Just because I suppose gay marriage doesn’t mean I voted for Obama.
I’ve never been a fan of voting for the “lesser” evil.
This is so utterly false, I don’t even know where to start. Eich had every right to speak in support of Prop 8 or anything else he might like to, but I also have the right to express my distaste of his bigoted ideas by withholding my support of any organization which he runs.
I’ll defend to the death his right to *say* whatever he likes, but there’s no reason in the world I need to do business with someone whose views I consider to make them a reprehensible human being. The idea that not giving someone your money is equivalent to silencing their right to free speech strikes me as an incredible sense of entitlement. There’s nothing about the right to free speech that entitles you to say anything you want without consequences of having said it. Freedom of speech means the government can’t silence you, but that protection begins and ends with the *government*. How any individual chooses to interact with you as a result of *your* free speech is as much a matter of *their* free speech as you being free to say it in the first place.
There’s nothing about supporting free speech that requires me to also support every person who speaks an opinion I disagree with. By your logic, I should vote for a politician whose views I disagree with because if I voted against him, I’d be infringing on his right to free speech. That’s preposterous and misguided and flat out foolish.
Calling support for a multimeter? What planet are you from? Short of it breaking and needing a replacement under warranty, you plug it in, spin the dial to the mode you want, and away you go.
Do people call Sears for tech support on a Craftsman wrench? I’ll grant a multimeter is *slightly* more complicated of a tool, but really only slightly to someone who’s the least bit experienced in that area of tech. I think I got my first MM when I was six years old. Took Dad about 10 minutes to show me how to measure voltage and resistance, and that was when you had to set the range yourself.
As someone who doesn’t root my iPhone and would prefer nobody else do so, there is a key advantage to me to Apple’s preventing downgrades of the iOS version on a device. If an old release contains a security flaw that would allow access to secured data on the device which a newly patched version would prevent, allowing an install of the older version would allow an attacker to downgrade, exploit the bug, and extract data from my device. Jailbreaking a device amounts to removing all effective protections in terms of access security that the device may provide for data stored on it. Many (but certainly not all) jailbreaks exploited vulnerabilities at an OS-software level, and patching those vulnerabilities made it impossible to jailbreak an updated device. That doesn’t apply to the devices that had exploitable vulnerabilities in the ROM boot block of course; and that was an issue on several of the devices.
Ensuring that older vulnerable versions cannot be installed on my device is a security feature to me. It’s also a limitation of my freedom, and it makes the device less “mine.” Looking at the alternatives and what I *personally* want to do with (and want done to) my iDevice, I’ve decided this is a better option for me. I’m not prevented from using the device in the manner for which it was marketed, and potentially some would-be attackers are thwarted from extracting data from my device. Certainly there’s more that I could potentially do with the device in terms of home-rolled firmware, but I’m at the point where I really and truly don’t want to “hack” on my cell phone with all the potential issues that come with that (battery drain, instability, insecurity, etc.). I want to pull my iPhone out of my pocket and make a phone call. Apple’s update policy doesn’t prevent that, and their QA is reasonably good in terms of the battery drain and related issues being a relative minority of their users. I’m willing to take the risk of updating.
In a perfect world, boot loader security might be accomplished with a key that’s under my control rather than under Apple’s. Maybe a card / USB stick in the box with the private key for the boot loader and a “lose this at your peril” warning. The device could take official Apple updates without the key (better if that was a configurable option), or take any software with the key. Of course the support nightmare that would ensue would be insane, and Apple would never do it as it’s a definite UX detraction for any but the most geeky of buyers.
RMS’ great vision of full control of all of our hardware is a nice one, but in the mean time I’m content to enter compromises with companies that have reasonable histories of “not being evil” in the areas which directly effect me. I’m good with Apple and how they handle their iThing’s. Sure that could change, and I keep my data off-device in formats that would allow me to convert and go elsewhere if need be. Beyond that, I’m not going to lose sleep over the fact that I’m stuck with one-way upgrades of iOS. It’s one of those arguments that I can agree with ideologically, but in terms of practicality and getting things done, it doesn’t negatively effect me.
Upgrading is always an option. They’ve just decided that the (odds X cost) of potential security issues from not upgrading is lower than the cost of upgrading all of the apps and systems.
Were I an IT-type person in such a company, I’d want hardcopy signed by C-level management expressing it in those exact terms. Something to the effect of, “We acknowledge that there are significant known vulnerabilities in our operating system and browser, that there is a significant likelihood of additional vulnerabilities, particular after the vendor’s end-of-life for patches. We nonetheless choose to run this vulnerable platform in lieu of incurring the costs to upgrade. We acknowledge that IT has made us aware of these risks and absolve IT of any responsibility for security incidents which occur as a result of this choice.”
Good luck getting that of course, but I’d be looking for a new job either way...
I prefer a little oxygen in my cables when I’m watching movies. The actors’ faces get this weird blue tint without it.
In my experience, when I need That Part on a Sunday afternoon, I’m not likely to get it from Radio Shack either. There are times I’d be willing to pay the retail price premium to get what I need. It’s a moot point when they don’t even stock basic discreet components or plugs half the time.
Why do you assume governments want to discredit Bitcoin?
An “anonymous” currency that actually carries a permanent record of every transaction ever conducted in it? Sounds like a law enforcement wet dream. I wonder if they’ll consider it worth the work* and the wider understanding of BTC’s true “anonymous” nature to work backwards and de-anonymize many of the BTC wallet ID’s used to make Silk Road purchases. I’d be shocked if most buyers took the necessary steps to make their wallet ID’s completely untraceable to them.
* And it’s only “work,” assuming that the nature of NSA’s various data capture and analysis programs haven’t been watching the blockchain from day one and correlating & de-anonymizing every wallet ID as they went. Wouldn’t really take that much given the scope of the data capture they seem to have. All it takes is one browser submit of your wallet ID through the same browser or even IP that your Amazon or Google or whatever cookie has been seen from, and they have a name to go with the ID.
This is true only so long as the Office of Thrift Supervision does its job effectively, and in recent history it’s been doing a piss poor job. OTS is supposed to seize a failing bank prior to the value of its assets dropping below the sum of FDIC insured deposits. The sale of the bank and its assets (loans it owns essentially), whole or in pieces to other banks should equal or exceed the amount of insured funds, and depositors are made whole without tax payers taking a bath. Usually the obligation of the deposits is assumed by the purchasing banks, so any eventual withdrawals come from the new bank’s assets.
The problem is when OTS waits too long, and a failing bank has slipped past the point where it has the assets to cover its deposits. In that case, any bank purchasing the assets and liabilities would insist on either a discount on the price (to offset the value of the deposits they would eventually have to pay back) or outright cash as part of the transaction to ensure they’re not taking a loss in the transaction. At that point, the money comes from the FDIC fund to make up the difference. FDIC is “insurance” in the sense that banks pay into it, but it’s backed by the full faith and credit of the United States of America. That means if the fund comes up short, every penny past that point comes directly out of the tax payers.
The FDIC insurance fund is maintained at a very low percentage of the overall deposits at risk. I think the requirement was raised to 1.35% in 2010, but that target isn’t required to be reached until 2020. The number of banks that failed as a result of various sub-prime related issues put a strain on the fund because OTS consistently waited until the banks were deeply in the red before acting. My cynical self says they were playing the “wait & hope” game, hoping the banks managed to ride it out without going under so they wouldn’t need to close them. Didn’t work out so well for a lot of banks.
At least as of 2010, the FDIC fund was in pretty bad shape as a result: http://www.zerohedge.com/artic...
So it’s true that FDIC insurance isn’t provided by the government, at least up to the point the insurance fund holds. Pat that point, any shortfalls are paid for by the government, IE You.
I misread:
And the first thing to pop into my head was why in Finagle’s name would anyone torrent Windows 8? Talk about a waste of bandwidth...
Sorry... What I intended to say was, "If there's any *reasonable* suit with the slightest chance of surviving appeal outside the Ninth Circus..."
If there’s any suit available to this actress, it’s against the producer/director/etc. of the film for misrepresentation. There’s no conceivable way this should be a copyright case. There’s no way that anyone who was paid for appearing in it by the eventual rights holder (producer/etc.) should retain any right to issue take down demands contrary to the will of the actual owner of the copyright.
Short of a contract that stated she retained any rights (doubtful), then I can’t see how this was anything other than work for hire with associated assignment of copyright.
Susan Sarandon supposedly hated Rocky Horror and regretted ever appearing in it. Shall we tear down all the copies of that?
If nothing else, judges in cases like this should take to heart that once something is published on the Internet, it’s forever. I know no judge wants to hear, “You don’t have the power to do that, your Honor,” but the fact of the matter is there’s no way to ever remove something like this from public view.
See also: Star Wars Christmas Special...
If you knew with complete assurance that the first crew would be lost if they attempted to land without repair, then it would likely be worth the risk to a second crew to mount a rescue.
If on the other hand, there’s only some chance that the first crew would be lost attempting to land, then working that risk into the risk to the second crew is reasonable. IE if there’s a 10% chance that there might have been trouble landing (and it sounds like the foam strikes leading up to Columbia’s trouble were in fact common, so could be considered low-risk) then it’s not unreasonable to decide that the risk of the second crew is an unreasonable risk. Consider also that the risk to this second crew for an accelerated launch process would likely have been FAR greater than a “normal” shuttle launch (assuming it can be said there’s anything “normal” about strapping a bomb to your ass and fleeing the planet...)
If there’s a very high chance of failure of the original crew’s landing, then the additional risk might be worth it. If not, then you really are doubling down and risking losing two crews. It’s entirely plausible that due to the corners cut for an accelerated launch Atlantis could have exploded during launch, leaving Columbia to still take their chances landing with a damaged wing.
Armchair quarterbacking is easy. Saying they should have risked a second crew *now*, knowing that it’s an impossibility and that your assertion that the risk is reasonable will never be tested is also easy. Being left to make that call in the moment, knowing that you could be sending a second shuttle crew to their deaths trying to help another crew that might not even need the help the first place. Little bit harder to live with that one...
The loss of the Columbia crew is a tragedy, but looking back based on this report, it doesn’t seem like the way it was handled was unreasonable.
You know you can say, “No, thanks,” when they ask for your phone number, and they’ll still sell you your batteries, right?
Citation needed... Cost issues are certainly valid, but I’d have little safety concern working and allowing my child to grow up in New York City as an example. I’m sure there are cities in the US I wouldn’t say that for, and I suspect there are cities that I’d feel even safer than NYC, but there’s no reason you need to move out to the suburbs to be “safe”.
Safety is relative anyways. If in fact your odds of getting mugged in the suburbs are lower than in the city, that’s nice, but your odds of dying in a hurtling fireball of a car wreck on the way to/from work are immensely higher. Pick your poison...
Eschewing useful tools out of fear of being a “bad” programmer makes you a bad programmer.
It doesn’t matter how deep your knowledge of the language or environment is. A well configured IDE will allow you to complete your job more quickly. It makes research navigating around a codebase much more straight forward. There’s no reason to do textual searches in a simple text editor when an IDE can parse the language and show you actual references to a symbol, not just things that happen to be named similarly.
All of the “uber” programmers I’ve known who avoid IDE’s are universally less effective than even mediocre programmers who use tools to make their jobs easier. The type of programmer who avoids tools out of the belief that doing it “by hand” is better generally waste more time tweaking their environment, going on architecture astronaut treks, and generally doing everything they can that isn’t actually writing code that gets the job at hand done.
Car analogy: You can change a tire with a wrench, and maybe a long piece of pipe to use for leverage. Or you can use a pneumatic impact driver and get the job done quicker, with less damage to the bolts, and put back together tighter (less chance of bolts loosening, tires rolling down the road without you). Any mechanic who tried to hold themselves up as a hero for doing it the hard way would be laughed out of the shop (and probably out of a job).
Be a Software Simian. Not using tools just makes you a dumb code monkey.
It’s true Apple drops new iOS major versions for older devices. They’re usually pretty good about it, but as an owner of the original iPad, I’d say they do occasionally cut devices off a bit prematurely...
That said, Apple has in the past issued patch releases of older iOS major versions to fix security issues on devices that couldn’t take the latest major iOS version.
If my memory serves, iOS 3.1.3 was a case of that where the original iPhone (2G) wouldn’t get iOS 4 but they did back port security fixes for it.
Really? Let us know how that works out... Maybe you should read that big agreement you have to click “Agree” to when you activate a phone. All liability for software bugs, known or unknown is disclaimed.
You have zero chance of seeing a penny from any such attempt.
This seems easy to fix. Most (all?) states have some sort of annual safety inspection requirement for keeping a car on the road. Generally these safety checks include connecting to the car computer’s diagnostic port to read emissions related information to ensure the car complies with the pollution requirements that applied to its model year.
Add as a requirement of those checks that plugging into the computer also checks software versions and compare that against a list of updates the respective manufacture has deemed critical for continued safety. A passing safety inspection requires that the car’s systems be up to date with all critical software updates.
Flash is native executable code. It’s not encumbered by any sandboxing function in the browser. That’s by design.
Browser plugins are intended to be allowed unfettered access to the system so that they can accomplish tasks not normally possible within a browser. The only sandbox provided by most browsers relates specifically to JavaScript, and as far as I can tell, this is unrelated to JavaScript at all.
It’s possible that an OS level sandbox beyond the browser (like OS X AppSandbox, Linux AppArmor, SELinux, etc.) might be able to contain an exploit within Flash, limiting it to a user account or a directory; but that would take some careful crafting in terms of OS sandbox configuration. None of the major platforms are configured to do anything close to my knowledge.
tl;dr: Your sandbox can’t help you here. Update Flash or you’re toast.