Tomopop joins the Jan. 18th SOPA/PIPA blackout protest

Jan 17 // Brian Szabelski
   @brianszabelski

We'd like to take a time out from the usual stream of posting news about toys and other cool collectibles to bring you this little announcement. As part of the effort to protest against SOPA and its sister bill in the U.S. Senate, PIPA, Tomopop and our sister ModernMethod blogs (Destructoid, Japanator and Flixist) will all be going silent tomorrow, Wednesday, January 18. 

Despite the fact that SOPA has been shelved for the moment, that doesn't mean either bill is formally dead. And while you may not think it has much effect on you, the toy fan, remember that these proposedlaws have all kinds of nasty things in them regarding DNS and search engine blocking that could keep you from getting to Tomopop, other toy blogs/sites or really, any other site you enjoy ... permanently. 

Since we'll all have tomorrow off, take the time to call your senators and representatives, spread the word and let everyone know what's really up with these bills. For more information, head on over to the Entertainment Consumers Association.

 

Photo Gallery:   (you can use your arrow keys)



 Reblog (or) Blog Reply


Brian Szabelski, Editor-in-Chief
 Follow Blog + disclosure brianszabelski Tips
Brian Szabelski is Tomopop's Editor-in-Chief, stuck with an ever-growing collection of figures and toys. When he's not posting on Tomopop, he can usually be found working on any number of project... more   |   staff directory

Get more tomopop:   We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out

Get comment replies by email.     settings



Unsavory comments? Please report harassment, spam, and hate speech to our comment moderators

Can't see comments? Anti-virus apps like Avast or some browser extensions can cause this. Easy fix: Add   [*].disqus.com   to your security software's whitelist.

advertisement:




Back to Top