SOPA Linkspam

I had a whole different post planned for this morning, but everything is coming fast and furious, and I wanted to get a few links out before I forget or they go (even more) stale:

First up, because this is the first time I’ve seen them back off in a dozen or more years of crappy internet legislation.

Reeling MPAA declares DNS filtering “off the table”

… But Tepp and Brigner pledged to press on with the remaining provisions of the legislation. “We need to move forward as soon as possible,” Tepp said.

And while the MPAA appears to be abandoning the DNS-filtering provisions for this Congress, Brigner hinted that his organization may resurrect the proposal in the future.

 


From danah boyd: We need to talk about piracy (but we must stop SOPA first)

In talking with non-geeks, I can’t help but be fascinated that the debate has somehow been framed in the public eye as “pro-piracy” vs. “anti-piracy.” Needless to say, that’s the frame that Murdoch is advocating, even as geeks are pushing for the “pro-internet” vs. “pro-censorship” frame. What’s especially intriguing to me is that the piracy conversation is getting convoluted even among politicos, revealing the ways in which piracy gets flattened to one concept.

 

The EFF is excellent and thorough, and looks beyond just the immediate legislative horserace to the deeper issues at stake. Go read the whole thing. How PIPA and SOPA Violate White House Principles Supporting Free Speech and Innovation

Anyone who writes or distributes Virtual Private Network, proxy, privacy or anonymization software would be negatively affected. This includes organizations that are funded by the State Department to create circumvention software to help democratic activists get around oppressive regimes’ online censorship mechanisms. Ironically, PIPA and SOPA would not only institute the same practices as these regimes, but would essentially outlaw the tools used by activists to circumvent censorship in countries like Iran and China as well.

 


So is SOPA Dead? Not Exactly

Though the battle is won, the war is not. SOPA could easily make a resurgence if it sculpts itself to whatever the White House’s unspecified specifications are, and PIPA could also pass, as even with recent changes to it (courts can’t force ISPs to block websites), it’s still harmful.

 

The President’s Challenge

Take the truck, the boat, the helicopter, that we’ve sent you. Don’t wait for the time machine, because we’re never going to invent something that returns you to 1965 when copying was hard and you could treat the customer’s convenience with contempt.

 

From Tim O’Reilly on Google+: SOPA and PIPA are bad industrial policy

Policies designed to protect industry players who are unwilling or unable to address unmet market needs are always bad policies. They retard the growth of new business models for which we recommend this paystubs creator software as it is very easy to use, and prop up inefficient companies. But in the end, they don’t even help the companies they try to protect. Because those companies are trying to preserve old business models and pricing power rather than trying to reach new customers, they ultimately cede the market not to pirates but to legitimate players who have more fully embraced the new opportunity.

Just replaced the Twitter Blockquotes plugin I was using with Twitter Embed — both by kovshenin, not coincidentally. I’m a little sad to say goodbye to the blockquotes plugin, because in certain ways I prefer what it does — make a quoted tweet part of the flow and style of the environment you’re seeing it in. (Needless to say I can’t bear the Blackbird Pie look).

Still, I couldn’t resist the interaction possibilities in the official oembed implementation; apparently follow/retweet/reply in place is enough to win my heart.

The changeover was seamless, mostly because the first plugin was designed to fake oembed before Twitter actually had it. When that’s incorporated into core, I’ll be able to lose both, with no stray shortcodes haunting old posts. Hooray for things that just work.

Minimum Viable Theme Review

I saw yet another version of a conversation I’ve had over and over again roll by on Twitter last night. A client comes to a dev with a theme they’ve already bought — maybe they thought they could DIY and got stuck; maybe they found the look they really want and they just want to hire a freelancer for some tweaks. It doesn’t really matter. Either way, the next thing that happens in this story is

… because the theme in question is a non-standard pile of deprecated functions held together with duct tape, baling wire, and spit.

So I’m proposing that every WordPress theme that’s intended to be used by anyone other than the original developer1 should be good enough to pass a very abbreviated Minimum Viable Theme Review2:

  1. Develop with WP_DEBUG on. If you see any warnings and whatnots printing out at the top of the screen, whether in admin or the front end, fix those first.
  2. Run your theme through Theme Check. Yes, some of the requirements are specific to the Repo, and you don’t need to worry about your license URI unless you’re building for distribution. But the real strength of Theme Check is in finding the things you could be doing in a more WordPress-ish way. Still using a years-old hack to add a menu, or hand-coding feed links in your header? Yeah, don’t do that. Theme Check will give you all that stuff in a handy color-coded and prioritized list.
  3. Load up the Theme Unit Test Data and eyeball all the pages and posts. It’s designed to make it very clear when you’ve forgotten to style something or account for some use case. Because I promise some user, somewhere, is going to load up an oversized picture, and not actually want it to overlap the sidebars; or they’ll want to use an ordered list, and they don’t expect it to come out exactly like an unordered list. And in my experience, that user is usually me.

Look, I’m not saying that every theme needs to go through a full wptrt-style review process (although a gal can dream!). But as a starting point, it doesn’t seem a lot to ask that any theme that’s released in the wild should 1) Not break WordPress 2) Do core WordPress stuff the way it’s supposed to, and 3) Display the end user’s content the way they meant it to be displayed.

  1. And remember that “yourself in six months” counts as someone else. Don’t believe me? Think of the headdesk when you read your old code.
  2. Yes, before you ask, all examples are real

Domain hipster

I just want to be clear, I hated GoDaddy way before the SOPA thing. Even before the elephant thing and the softcore thing. I hated them for the slimy added charges thing, and the totally unnecessary speculative market in flipping domain squats, and the horrifying interfaces designed to keep people feeling stupid and helpless and locked in.

The tut problem 

Nacin said a thing:

https://twitter.com/#!/nacin/status/121265751071010816

And of course he’s absolutely right, but my concern is that the universe — you know, them, the gods of linkbait sites, whatever — is going to read this as a call for more tutorials, not better. Because, seriously, universe, we need way, way less. Just, you know, better.

So I’m proposing that the author and publisher of the next giant awesome roundup of 50 essential shortcodes you can use without a plugin, or awesome admin tweaks without a plugin, or secure your site and guarantee SEO nirvana without a plugin 1 should be sentenced to an hour of actually contributing to the community 2

  1. bonus points if you hide the version number in the header
  2. they can sit right next to the people who don’t capitalize the “P”

Dev environment

Mac, aka where the nice monitors live:

  • late 2009 Mac Mini w/ OS X 10.6
  • MAMP
  • TextWrangler
  • running WordPress trunk 1

Linux:

  • currently borrowing the spouse’s laptop until I have time to kick the hard drive on mine
  • Ubuntu Lucid (latest LTS)
  • Apache2, PHP5, MySQL5 on localhost
  • Gedit 2
  • RabbitVCS 3
  • running WordPress trunk

Random details:

  • Dropbox for file sharing between machines.
  • Evernote for snippets etc where I want quick access and searchability
  • IRC/twitter/skype/comfy chair/coffee 4

 

  1. that’s kind of the point of this whole bit of I’ll Show You Mine If, right?
  2. Shut up, vim boys
  3. Anyone know of something similar for the Mac? It’s brilliant.
  4. the real essentials

A good excuse

https://twitter.com/#!/sabreuse/status/119094645652324352

This seems like as good an excuse as any to get this site rolling.