Group items tagged

For most of the last 1,500 years, the river supported a sustainable salmon economy. Salmon were at the heart of all the Klamath’s tribal cultures, and Indians were careful not to over-harvest them. Each summer, the lower Klamath’s Yurok and Hoopa tribes blocked the upstream paths of spawning salmon with barriers; then, after ten days of fishing, they removed the barriers, allowing upstream tribes to take their share. As the salmon completed their lifecycle, dying in the waters where they’d been spawned, they enriched the watershed with nutrients ingested during years in the ocean. Among the beneficiaries were at least 22 species of mammals and birds that eat salmon. Even the salmon carcasses that bears left behind on the riverbanks fertilized trees that provided shade along the river’s banks, cooling its waters so that the next generation of vulnerable juvenile salmon could survive. “We tried to go to court, to go through the political process, but it didn’t work. …The big issues were still out there, and we still had to resolve them.” Salmon’s biological family may have started in the age of dinosaurs a hundred million years ago. They’ve survived through heat waves and droughts, in rivers of varying flow, temperature, and nutrient load – but they were as ill-prepared for Europeans’ arrival as the Indians themselves. Gold miners who showed up in the mid-nineteenth century washed entire hillsides into the river with high-pressure hoses and scoured the river’s bed with dredges. Loggers dragged trees down streambeds, causing massive erosion, and dumped sawdust into the river, smothering incubating salmon eggs. Cattle grazed at the river’s edge, causing soil erosion and destroying shade-giving vegetation. Farmers diverted water to feed their crops. The dams were the crowning blows. Between 1908 and 1962, six dams were built on the Klamath. The tallest, the 173-foot-high Iron Gate, is the farthest downstream, and definitively blocked salmon from the river’s upper quarter – after it was built, the river’s salmon population plummeted. In addition, the dams devastated water quality by promoting thick growths of toxic algae in the reservoirs. For Klamath basin farmers, however, the dams were deemed indispensable, as they generated hydropower that made pumping of their irrigation water possible.To the farmers, the potential loss of the dams’ hydropower was considered no less crippling than an end to Klamath-supplied irrigation.

For most of the last century, the farmers were oblivious to the damage that dams and water diversions caused downstream, while the tribes and commercial fishermen quietly seethed. The annual salmon run, once so abundant that people caught fish with their hands, was roughly pegged at more than a million fish at its peak; in recent years it has dropped to perhaps 200,000 in good years, and as low as 12,000 – below the minimum believed necessary to sustain the runs – in bad years. Spring Chinook, which once comprised the river’s dominant salmon run, entirely disappeared. Two fish species – the Lost River sucker and the shortnose sucker – that once supported a commercial fishery, were listed as endangered in 1988. Coho salmon were listed as threatened nine years later. All this has had a devastating impact on the tribes. Traditionally able to sustain themselves throughout the year on seasonal migrations of the river’s salmon, trout, and candlefish, tribal members suffered greatly as the runs declined or went extinct. For four decades beginning in 1933, the tribes were barred from fishing the river even as commercial fishermen went unrestricted. Members of the Karuk tribe once consumed an estimated average of 450 pounds of salmon a year; a 2004 survey found that the average had dropped to five pounds a year. The survey linked salmon’s absence to epidemics of diabetes and heart disease that now plague the Karuk. The 2001 cutoff left farmers without irrigated water for the first time in the Klamath Project’s history. Over the next four months, many farmers performed repeated acts of civil disobedience, most notably when a bucket brigade passed pails of banned water from its lake storage to an irrigation canal while thousands of onlookers cheered. The protests attracted Christian-fundamentalist, anti-government, and property rights advocates from throughout the West; former Idaho Congresswoman Helen Chenoweth-Hage likened the farmers’ struggle to the American Revolution.

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.