Language Selection

English French German Italian Portuguese Spanish

Stop the Internet Blacklist!

Filed under
Web

S. 3804, the Combating Online Infringement and Counterfeits Act (COICA), introduced by Sen. Patrick Leahy (D-VT) and Sen. Orrin Hatch (R-UT), would create a blacklist of domain names that the government thinks are involved in copyright infringement, which the Attorney General can then add to with a court order.

Internet service providers and others would be required to block any domains on the list.

This amounts to government censorship of the Internet. COICA is scheduled to be considered by the US Senate Judiciary Committee this Thursday, so there's no time to waste.

Please add your name to Demand Progress's petition at http://demandprogress.org/blacklist/, and contact your own Senator directly to let him or her know you oppose this bill and the rest of the War on Sharing.

For more information, see Peter Eckersley's analysis for the Electronic Frontier Foundation at https://www.eff.org/deeplinks/2010/11/case-against-coica.

Posted Here

More here




"Censoring the Internet is

"Censoring the Internet is something we'd expect from China or Iran, not the U.S. Senate."- Naaah, why is that? I'm not surprised at all, to be honest.

Internet blacklist

The Australian case proves that the anti-counterfeit or anti-child-pornography or whatever the evil-fed-to-the-sheeple of the day argument is just an excuse to blacklist sites that the groups at the power don't like and/or fear people to read. In Australia opinion and religious sites ended up in the blacklist, and they were the most in number.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

NHS open-source Spine 2 platform to go live next week

Last year, the NHS said open source would be a key feature of the new approach to healthcare IT. It hopes embracing open source will both cut the upfront costs of implementing new IT systems and take advantage of using the best brains from different areas of healthcare to develop collaborative solutions. Meyer said the Spine switchover team has “picked up the gauntlet around open-source software”. The HSCIC and BJSS have collaborated to build the core services of Spine 2, such as electronic prescriptions and care records, “in a series of iterative developments”. Read more

What the Linux Foundation Does for Linux

Jim Zemlin, the executive director of the Linux Foundation, talks about Linux a lot. During his keynote at the LinuxCon USA event here, Zemlin noted that it's often difficult for him to come up with new material for talking about the state of Linux at this point. Every year at LinuxCon, Zemlin delivers his State of Linux address, but this time he took a different approach. Zemlin detailed what he actually does and how the Linux Foundation works to advance the state of Linux. Fundamentally it's all about enabling the open source collaboration model for software development. "We are seeing a shift now where the majority of code in any product or service is going to be open source," Zemlin said. Zemlin added that open source is the new Pareto Principle for software development, where 80 percent of software code is open source. The nature of collaborative development itself has changed in recent years. For years the software collaboration was achieved mostly through standards organizations. Read more

Arch-based Linux distro KaOS 2014.08 is here with KDE 4.14.0

The Linux desktop community has reached a sad state. Ubuntu 14.04 was a disappointing release and Fedora is taking way too long between releases. Hell, OpenSUSE is an overall disaster. It is hard to recommend any Linux-based operating system beyond Mint. Even the popular KDE plasma environment and its associated programs are in a transition phase, moving from 4.x to 5.x. As exciting as KDE 5 may be, it is still not ready for prime-time; it is recommended to stay with 4 for now. Read more

diff -u: What's New in Kernel Development

One problem with Linux has been its implementation of system calls. As Andy Lutomirski pointed out recently, it's very messy. Even identifying which system calls were implemented for which architectures, he said, was very difficult, as was identifying the mapping between a call's name and its number, and mapping between call argument registers and system call arguments. Some user programs like strace and glibc needed to know this sort of information, but their way of gathering it together—although well accomplished—was very messy too. Read more