Returns while the device is under warranty?
Returns while the device is under warranty?
is that it only applies if there is full employment in both countries and zero cost to labor mobility...
"The higher price received for each country's comparative advantage good would lead each country to specialize in that good. To accomplish this, labor would have to move from the comparative disadvantaged industry into the comparative advantage industry. This means that one industry goes out of business in each country. However, because the model assumes full employment and costless mobility of labor, all of these workers are immediately gainfully employed in the other industry."
While of course what you say is true as far as it goes (money can be spent either on repairs or on new stuff), here is a way the broken window fallacy can itself be a fallacy.
If almost all the currency in a society is hoarded by the wealthiest 1% (like kept in the "Casino Economy") and the 1% control the government so it refuses to directly print more currency according to the needs of the 99%, then the economy for the 99% functions as if there were a depression due to insufficient currency in the economy of real goods and services.
The health of an economy for most people (as well as the political health of a democracy) is not just how much currency there is, or how fast it moves, but how broadly the currency is distributed. Many average economic indicators may not reflect this economic depression for the 99% due to currency unavailability -- in the same way that if Bill Gates stepped into a homeless shelter by accident, everyone in the building would on average be a millionaire.
For more on the "Casino Economy" or "Gambling Economy" of abstract finance see the section of Money as Debt II starting around here: https://www.youtube.com/watch?...
In such a circumstance (which is close to the economy we have now), if a window breaks that a wealthy person or the government wants to fix, then some of the hoarded and speculated cash from the Casino economy may be leaked into the real economy of the 99%. This would temporarily alleviate a tiny bit of the ongoing defacto economic depression until the money is sucked back into the ever expanding Casino economy again via interest on debt or other forms of rent-seeking. Someone breaking a to-be-replaced window of a wealthy person or government in such a situation is then engaging in an indirect form of theft. WWII was another example that led to increased government spending and progressive taxation in the USA, although to great human suffering across the globe in other ways.
To be clear, breaking a window that needs to be repaired by the 99% does not have this currency redistribution effect since no additional currency will be moved from the casino economy to the real economy. Then we are just left with the fallacy in its standard form -- not the fallacy in the limiting case of concentrated hoarded wealth.
Of course, in practice, things getting broken only gives excuses for future crackdowns on "terrorists" and the diversion of what little cash is left circulating in the real economy for the 99% into new taxes for a larger security apparatus to protect the windows of the 1%, so ultimately the path of breaking windows is likely self-defeating.
Better options include alternative currencies, local exchange trading systems (LETS), an improved gift economy like via free software and shared knowledge like with Slashdot, improved local subsistence production like via 3D printing or home gardening robots like Farmbot, better democratic processes leading to better government planning, and political change towards a basic income (with the BI funded by progressive taxation and rents on resource extraction or government-granted monopolies like broadcast spectrum use). I discuss those and more options here:
James P. Hogan's comments from: https://web.archive.org/web/20...
An Earth set well into the next century is going through one of its periodical crises politically, and it looks as if this time they might really press the button for the Big One. If it happens, the only chance for our species to survive would be by preserving a sliver of itself elsewhere, which in practical terms means another star, since nothing closer is readily habitable. There isn't time to organize a manned expedition of such scope from scratch. However, a robot exploratory vessel is under construction to make the first crossing to the Centauri system, and it with a crash program it would be possible to modify the designs to carry sets of human genetic data coded electronically. Additionally, a complement of incubator/nanny/tutor robots can be included, able to convert the electronic data back into chemistry and raise/educate the ensuing offspring while others prepare surface habitats and supporting infrastructure, when a habitable world is discovered. By the time we meet the "Chironians," their culture is into its fifth generation.
In the meantime, Earth went through a dodgy period, but managed in the end to muddle through. The fun begins when a generation ship housing a population of thousands arrives to "reclaim" the colony on behalf of the repressive, authoritarian regime that emerged following the crisis period. The Mayflower II brings with it all the tried and tested apparatus for bringing a recalcitrant population to heel: authority, with its power structure and symbolism, to impress; commercial institutions with the promise of wealth and possessions, to tempt and ensnare; a religious presence, to awe and instill duty and obedience; and if all else fails, armed military force to compel. But what happens when these methods encounter a population that has never been conditioned to respond?
The book has an interesting corollary. Around about the mid eighties, I received a letter notifying me that the story had been serialized in an underground Polish s.f. magazine. They hadn't exactly "stolen" it, the publishers explained, but had credited zlotys to an account in my name there, so if I ever decided to take a holiday in Poland the expenses would be covered (there was no exchange mechanism with Western currencies at that time). Then the story started surfacing in other countries of Eastern Europe, by all accounts to an enthusiastic reception. What they liked there, apparently, was the updated "Ghandiesque" formula on how bring down an oppressive regime when it's got all the guns. And a couple of years later, they were all doing it!
So I claim the credit. Forget all the tales you hear about the contradictions of Marxist economics, truth getting past the Iron Curtain via satellites and the Internet, Reagan's Star Wars program, and so on.
In 1989, after communist rule and the Wall came tumbling down, the annual European s.f. convention was held at Krakow in southern Poland, and I was invited as one of the Western guests. On the way home, I spent a few days in Warsaw and at last was able to meet the people who had published that original magazine. "Well, fine," I told them. "Finally, I can draw out all that money that you stashed away for me back in '85. One of the remarked-too hastily--that "It was worth something when we put it in the bank." (There had been two years of ruinous inflation following the outgoing regime's policy of sabotaging everything in order to be able to prove that the new ideas wouldn't work.) I said, resignedly, "Okay. How much are we talking about?" The one with a calculator tapped away for a few seconds, looked embarrassed, and announced, "Eight dollars and forty-three cents." So after the U.S. had spent trillions on its B-52s, Trident submarines, NSA, CIA, and the rest--all of it.
"This approximately 60 page document is a ramble about ways to ensure the CIA (as well as other big organizations) remains (or becomes) accountable to human needs and the needs of healthy, prosperous, joyful, secure, educated communities. The primarily suggestion is to encourage a paradigm shift away from scarcity thinking & competition thinking towards abundance thinking & cooperation thinking within the CIA and other organizations. I suggest that shift could be encouraged in part by providing publicly accessible free "intelligence" tools and other publicly accessible free information that all people (including in the CIA and elsewhere) can, if they want, use to better connect the dots about global issues and see those issues from multiple perspectives, to provide a better context for providing broad policy advice. It links that effort to bigger efforts to transform our global society into a place that works well for (almost) everyone that millions of people are engaged in. A central Haudenosaunee story-related theme is the transformation of Tadodaho through the efforts of the Peacemaker from someone who was evil and hurtful to someone who was good and helpful.
... fully funded by Congress, I have ZERO sympathy for politicians getting hacked.
Only circumstantial evidence. Hackers who work for an intelligence service are never going to get caught, much less extradited. Of course, the same can be said of ANY elite hacker.
IMHO, it's not the Russians. They are widely suspected of getting Hillary's emails by monitoring the original "Guccifer". If so, they would want Hillary as POTUS because they could easily control her via blackmail. Hell, they don't even need the actual emails. The mere threat should be enough.
>Messaging encryption, widely used by Islamist extremists to plan attacks
Air, food and water, widely used by Islamist extremists to power their brains! When, oh when will politicians stop being so lackadaisical?!
Once this camera technology makes it to the porn industry, they will use it to shoot people's moons.
This will no doubt be the rising tide that lifts all boats, from a "lighting people's undersides" perspective.
Security and open source
"System security should not depend on the secrecy of the implementation or its components."
-- Guide to General Server Security, National Institute of Standards and Technology
A codebase is a terrible secret.
Because a codebase is so large, it cannot easily be changed. Furthermore, it must be known, or at least knowable, to the large number of people who work on it, so it cannot be kept secret very easily. This is represented at the bottom of figures two and three. Therefore "security through obscurity" is a terrible idea when it comes to a codebase. In most cases your system will consist of code which you reuse as well as code that your write yourself. Therefore both of these types of code should be open.
Of course, your system will have secrets in most cases -- keys, passwords, and the like -- but you should assume they have been discovered and change them often. We call these secrets a "red thread", because, like a red thread in a white handkerchief, they should be as vivid and thin as possible. By making them thin, such as a single password, you make them very easy to change and keep secret. Although these secrets are tiny, they must be managed carefully and conscientiously. We believe this concept is so important that we have placed it on our reusable version of the Wardley-Duncan map linked to above.
There are risks of defects and complexity associated with using open source modules indiscriminately. There are also security vulnerabilities to any system, either through negligence or by the intention of a bad actor. The key to preventing this is code review.
You must make sure that each component you use is code reviewed. In practice this means either that you must use very popular projects whose code is looked at by a large number of people on a regular basis, or you must use small projects which your team can code review itself. In practice, the criteria for making this decision for reused components is similar to the rules of thumb that we have already laid down for managing risk.However, you may need to adjust these rules of thumb based on how often you plan to update the component.
For example, a small component which is very stable need not be updated at all. If it is small and you can code review it or pay a team to code review it, then you may use it. On the other hand if the project has frequent updates, your team will have to decide how to manage these updates. A large project may have both stable and experimental branches. In general your team will want to update as frequently as the major number of the branch. If the project is very active and many people are looking at it, this does not represent a security risk. If however a project is changing rapidly and producing many releases and your team does not have the resources to ensure that each new release is code reviewed and you do not trust the community to do so, then you probably should not use that component.
With an open source component, it is at least possible to understand how much code review it is receiving.We know of no way to do this for closed source code kept as a secret.A firm which is asked to maintain the security of the code that it has written is placed in a conflict of interest. It isn't in its short-term interest to spend resources on this code review, and it is not in its short-term interest to admit defects.
Security of your own code
Make all your code open and examinable from the start. Moreover, it is best to encourage as many people to look at it, because the more people who seriously review the code the more likely a security flaw is to be found. Programmers will code more securely when their code is in the public's eye from the beginning.
Code that you write or contract to have written should be open source from the start, because it relieves you of the terrible risk and burden of maintaining the secrecy of the codebase. This means not only that it is published under an open source license as explained in our open source policy, but that it is published in a modern source code control system.
So protesters are criminals now?
As a US taxpayer, I helped pay for this. Where is the source code so I can learn from it or make it better/different? NASA and other US government agencies have a long track record of paying a lot for programs made by third-parties that are not made available under FLOSS licenses.
... Apple didn't combine their stale hardware with an unfortunate tendency to orphan it. The biggest risk seems to be video GPU chipsets. http://www.cultofmac.com/14695... [cultofmac.com]
Truly a Hero! I owe him a great deal!
I got my real start in Computers and Programming due to Logo. I was lucky enough to get a high school co-op placement at Ottawa's Carleton Board of Education's Computer Pilot Project, the Computer P.L.A.C.E. where I got to play with a Terrapin floor turtle, and ended up having to hack it's code fix it's programming to make it draw square "squares". I taught computer programming using LOGO, both Terrapin and Apple versions, to some of the very same high school teachers who had told me that I couldn't do programming because my math wasn't good enough. It also enabled me to get a summer job teaching at a computer day camp, and thus my career in computers was launched!
This Samhain, Seymour Papert, you will remembered among the honoured ancestors of my craft! Hail and Farewell!
C Code. C Code Run. Run, Code, RUN! PLEASE!!!!