Skip to main content

I made a GIF!

Speak up and say no to SOPA

This Is Important, You Should Know About It...

PROTECT IP Act Breaks The Internet from Fight for the Future on Vimeo.


The Internet Blacklist Bill — known as the “PROTECT IP Act” or S. 968 in the Senate and the “Stop Online Piracy Act” or H.R. 3261 in the House — has been discussed in the past, but crunch-time is upon us as Congress officially began holding hearings today on the most harmful Internet censorship legislation of our time.

An informative video on the bill’s many ills has been posted above, but, in brief, the legislation, if passed, would essentially hand the Internet over to corporations, allowing them to sue and shut down any website that so much as hosts a link to copyrighted material.
Internet Service Providers could be forced to block social media sites, search engines could be required to delete results, and startups could lose their funding — all on the whim of the copyright holder.

Perhaps most distressing of all, however, is the fact that this bill, in true Orwellian fashion, does nothing to prevent actual piracy. The only thing it will succeed in doing is turning the Internet into a dystopic plutocracy where people are no longer free to share ideas and be creative for fear of running afoul of Big Business.

Despite what some would have you believe, the hearings are offensively lopsided, with pro-SOPA voices far outweighing those opposed. A slew of tech companies including Google, Yahoo!, Mozilla, Twitter, and AOL, have undersigned a full-page ad in today’s New York Times opposing SOPA, but it’s doubtful their voices will be heard by those who need to hear it.

That means it’s up to you to get this terrifying, jobs-killing, Internet-breaking bill off the table for good. Here are a few things you can do:
  • Reach out to your representatives in congress. Despite what they might think, they work for you. Remind them of that by e-mailing them this form letter (good), or look them up and write them a personal, heartfelt letter (even better). 
  • Sign this petition, and also this one.
  • Share this post and/or the video above.
  • Get the word out any way you can, because, soon you may no longer be allowed to.

Comments

Popular posts from this blog

Cisco ASA ICMP packet-tracer

Occasionally devices fail to respond to a ping.  This can result from devices being off-line, having a local firewall enabled or the perimeter firewall configuration.  The Cisco ASA ICMP packet-tracer options differ from the TCP or UDP command options.  An example is below: packet-tracer input outside icmp A.B.C.D 8 0 E.F.G.H The ICMP type is "8" (echo request) with code"0" (none).  There are no options on destination IPv4 address E.F.G.H. Complete ICMP documentation at URL http://www.iana.org/assignments/icmp-parameters/ Complete Cisco ASA packet-tracer documentation at URL http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/p.html#wp1878788

Xfce4 lock screen not working

Xfce4 would not start a screensaver on my Linux system.  Researching it, it ran xflock4 from the command line ad received an error: Property "/general/LockCommand" does not exist on channel "xfce4-session". To fix this, additional configuration needed, but no hacks. First, verify xflock4 and xfconf-query are available. $ which xflock4 xfconf-query /bin/xflock4 /bin/xfconf-query Next  install a lock screen package that provides 'xlock', 'slock', 'i3lock' or similar.  $ sudo yum install -y xlockmore-gtk i3lock Last, add an executable (with options) as /general/LockCommand in the xfce4-session settings. $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "xlock -mode matrix" --type  string $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "i3lock -c 000000" --type string Test by running xflock4 from the command line or through the GUI.

X11 Forwarding issue solved

TL;DR Disabling IPv6 necessitates SSHd AddressFamily is "inet" for X11 Forwarding to work. Issue OpenSSH assumes both IPv6 and IPv4 protocols are enabled, and default SSHd AddressFamily value "any" is valid. Quickly skimming the OpenSSH source code, it was not obvious why SSHd does not fail gracefully, selecting only an available IP address family. Therefore, for X11 Forwarding to work correctly, in /etc/ssh/sshd_config we must choose: Defaults - IPv6 enabled and SSHd AddressFamily value " any " Custom - IPv6 disabled and SSHd AddressFamily value " inet " Background PuTTY was not creating a $HOME/.Xauthority file on ssh login and no X11 applications would run, despite setting $DISPLAY.  PuTTY was correctly configured with: X11 Forwarding enabled X display location empty Remote authentication protocol MIT-Magic-Cookie-1 X authority file for local display empty On the initial ssh login there should be a .Xauthority notic