Group items tagged

Stack was upset that §1706 did precisely what it was designed to do: Deprive him of the chance to exploit independent contractor status to avoid paying taxes through non-filing or through the understatement of income, overstatement of deductions, and avoidance of income tax withholding. In spite of the overwhelming advantages attendant to employee status, Joe Stack desperately wanted to be treated as an independent contractor for one simple reason: It would have made his tax protesting easier.4 Footnotes: ¹  We have met many taxpayers who worked as independent contractors for years without so much as a peep of protest until they realized, ex post facto, that it might have better for them to have been treated as employees. In our experience, workers tend to be content with their independent contractor status until one of the following happens: They get fired or quit They get hurt on the job They get sued for something they did while on the job They need a bank loan (and employment verification)  ²  If Stack had been an independent contractor and was subsequently “fired” by his principal, my hunch is it would have taken him less time to file a claim for unemployment compensation than it takes Apolo Ohno to finish short track. ³  Indeed, §1706 was included in TRA ‘86 because the CBO had estimated that the government was losing up to 30% of taxes because independent contractors were either not reporting all of their income on their tax returns or were claiming fraudulent or questionable deductions against that income. 4   Like all tax protestors, Stack knew that once the IRS had collected his taxes through payroll withholding it would never give it back to him based on previously refuted tax protestor arguments. Consequently, his only chance of avoiding taxes was to control his own tax payments and then use his frivolous arguments to evade or at least defer paying taxes.

"I like to say I gave up an eight-minute commute for an eight-hour commute," he says wearily, running a hand though salt-and-pepper hair as he watches his two sons play basketball for the first time this season. After the aging General Motors plant where he worked for 23 years was idled about a year ago, Hanley faced a Hobson's choice: Stay with his family and search for an autoworker's salary ($28 an hour) in a county where more than 40 percent of its manufacturing jobs disappeared from 2006 to 2009. Or hang on to his GM paycheck and health insurance and follow the job, no matter where it leads. In his case, it led to Fairfax, Kan., the same place his brother and two brothers-in-law — also GM workers, and now his roommates — landed. For others, it has been Indiana or Texas. The long commute is not just a story of hard times, tough choices and a shrinking American auto industry. It's also a case study of what happens when an aging industrial town loses an anchor, when workers too old to start over and too young to retire are caught in a squeeze and when economic survival means one family, but two far-flung ZIP codes.

The CNCI consists of a number of mutually reinforcing initiatives with the following major goals designed to help secure the United States in cyberspace: To establish a front line of defense against today’s immediate threats by creating or enhancing shared situational awareness of network vulnerabilities, threats, and events within the Federal Government—and ultimately with state, local, and tribal governments and private sector partners—and the ability to act quickly to reduce our current vulnerabilities and prevent intrusions. To defend against the full spectrum of threats by enhancing U.S. counterintelligence capabilities and increasing the security of the supply chain for key information technologies. To strengthen the future cybersecurity environment by expanding cyber education; coordinating and redirecting research and development efforts across the Federal Government; and working to define and develop strategies to deter hostile or malicious activity in cyberspace.

University of Edinburgh law lecturer Andres Guadamuz wrote a blog entry this week highlighting some particularly troubling aspects of the IIPA's 301 recommendations. The organization has condemned Indonesia and several other countries for encouraging government adoption of open source software. According to the IIPA, official government endorsements of open source software create "trade barriers" and restrict "equitable market access" for software companies. The profound absurdity of this accusation is exacerbated by the fact that Indonesia's move towards open source software was almost entirely motivated by a desire to eliminate the use of pirated software within the government IT infrastructure. It's important to understand that Indonesia has not mandated the adoption of open source software or barred government agencies from purchasing proprietary commercial software. The Indonesian government issued a statement in 2009 informing municipal governments that they had to stop using pirated software. The statement said that government agencies must either purchase legally licensed commercial software or switch to free and open source alternatives in order to comply with copyright law. This attempt by Indonesia to promote legal software procurement processes by endorsing the viability of open source software has apparently angered the IIPA. In its 301 recommendations for Indonesia, the IIPA demands that the government rescind its 2009 statement. According to the IIPA, Indonesia's policy "weakens the software industry and undermines its long-term competitiveness" because open source software "encourages a mindset that does not give due consideration to the value to intellectual creations [and] fails to build respect for intellectual property rights." The number of ways in which the IIPA's statements regarding open source software are egregiously misleading and dishonest are too numerous to count. The IIPA seems to have completely missed the fact that there is a very robust ecosystem of commercial software vendors in the open source software market and that open source software is at the heart of some of the most popular consumer electronics products that are sold in the United States. It has clearly become an important part of the US software economy and increasingly serves as an enabler of innovation and technological progress. In light of the profitability of Red Hat and other open source leaders, it seems absurd to contend that open source software adoption will weaken the software industry or reduce its competitiveness. In fact, the emergence of open source software has contributed to creating a more competitive landscape in the software industry by offering alternative business models that enable smaller companies to gain traction against the dominant incumbent players. The IIPA's position is profoundly hypocritical, because many parts of the US government, including the Department of Defense, have issued their own memos endorsing open source software adoption. The IIPA's disingenuous move to equate open source software with piracy reeks of desperation. The BSA and other IIPA members are likely losing sleep over open source software because that development model and approach to licensing will empower developing countries to build their own domestic IT industries, eliminating the need for them to tithe to American software giants. It's another failing of the 301 review, which Big Content wants used to coerce other countries into adopting ever-more-stringent copyright laws.