Blog

sopa-cripple

SOPA for Dummies

There’s been a huge flood of news, articles, stories and posts on SOPA recently.  Many people are scratching their heads, wondering what this SOPA thing is all about.  So this is a quick primer on why I believe SOPA is bad.

As stated above, this is my opinion (that is, Eric Robichaud, CEO of 401 Consulting).  I’m neither a laywer nor a politician, so I invite you to view the actual, full text of the proposed bill here and judge for yourself.  That said, here is my overview / option on the matter.

The “Stop Online Piracy Act” bill, aka “SOPA”, is aimed at, well, stopping online piracy of copyrighted materials.  I certainly have my own opinions about copyright laws and approaches to this subject, but at no time am I debating the validity of protecting one’s copyrights.  This debate isn’t about whether or not to stop piracy online.  It’s about how to stop it.  And SOPA isn’t the way.

SOPA is far too broad-reaching, and far too vague in it’s language.  It overrules carefully crafted provisions of the Digital Millenium Copyright Act (aka “DMCA”), makes the wrong people liable for infringements, sets up website owners for massive lawsuits, and more.

For example, the DMCA has “safe harbor” provisions for web site operators and digital carriers. If I post an illegal video to Facebook, then Facebook is required to forcibly take it down if notified about it.  Stated another way, Facebook’s liability is merely to respond when notified.  They’re not liable for the original posting.  Under SOPA, Facebook itself is liable, and could be legally shut down, and sued!

The bill targets sites that are “dedicated to the theft of U.S. property.” That seems reasonable at first.  Except when you read how they define “dedicated to the theft of U.S. property.”  They define such a site (and therefore subject it to being shut down) if it is “primarily designed for the purpose of offering services in a manner that enables copyright violation.”

Read that closely.

The site does not have to be design for the purpose of copyright violation (such as “The Pirate Bay”).  No, it only has to be designed in such as way that it offers services that enable copyright violation!   So basically, Flickr, Youtube, Facebook, Dropbox, and nearly ANY site on the internet that allows anyone to upload content, would all suddenly become violators!

Facebook has no idea what it’s 800 million users are doing in real-time, at any given moment.  It’s impossible to police.  Facebook provides a communication and content-sharing platform.   But SOPA puts the onus squarely upon the website operator (eg. Facebook).

The DMCA already states that posting copyright materials is illegal, but doesn’t make the website liable (unless the website itself posted the content of course) — the website is required to remove offending material when alerted.  SOPA overrules all of that.

SOPA also grants the U.S. Attorney General the sole right to police foreign websites where it has no jurisdiction.  If it notices infringing materials on a foreign website, it can censor the site in the U.S. by requiring all internet ISPs, DNS providers, search engines, etc. to permanently block access to the site, making it invisible to U.S. citizens.  If it’s a foreign site that the U.S. government can’t take down, it can block it.

Personally, I try to not be a conspiracy theorist, but I see this as one of the primary motivations behind SOPA — to give the government the ability to censor websites it doesn’t like.  Is Wiki Leaks embarrassing?  No problem – gone in a heartbeat.  What are we now, China?

There’s a lot more to this bill too.  For instance, a copyright owner can now sue the offending website without any ceilings or limitations on damages, including attorneys fees, and will win if the website cannot prove that they’re not “dedicated to the theft of U.S. property.”  And the way this is all worded (see above), it’s nearly impossible to prove that it isn’t!  This becomes a field day for attorneys, and an entrepreneurs worst nightmare.

SOPA tramples free speech.  SOPA makes the wrong people liable for copyright infringement.  And it will kill innovation — who wants to launch a new site that will just get you sued or worse?  We’ll never see the next Facebook, YouTube or Google.

I’m not here to debate the merits of Wiki Leaks or copyright law in general.  Just merely giving the high-level overview of why I’m against SOPA. It’s the legal equivalent of using a nuke to kill an ant.  So what if hundreds of square miles are a radioactive wasteland now, millions of people were killed, and billions in property destroyed — we got the ant!

There are proper and reasonable ways to do things.  This just isn’t it.

FB_Magic_Numbers_thumb_204x124

adobe-flash-logo-204x124

If you haven’t heard yet, Adobe officially announced the end of Flash for mobile devices.  In some quarters people immediately exclaimed “Steve Jobs was right!” Too bad he didn’t live to see it, after all those years of fighting Flash.   But regardless of the Steve Jobs angle, I think this announcement is a good thing for developers for several reasons.

First and foremost, it ends the old “VHS versus Beta” quandary once and for all.  Now instead of “wait and see,” or going down a path of obsolescence and continuing to invest in a dead-end technology, we all know into which basket to place our eggs.  This allows all developers to get off the fence and start focusing in the same direction — towards HTML5 and open standards.

Additionally, with all developers moving down the same path, all of those resources will accelerate progress towards HTML5 as opposed to when resources and attention were divided.  This will speed the adoption of newer technologies.

The announcement, in my opinion, is long overdue.  Flash was breakthrough technology at the time (harkening back to it’s Macromedia days), but it’s past its prime.  Flash is inherently un-indexable by the search engines, appearing as a big void in web pages.  I’m sure I don’t have to comment on the incredible importance of search engine optimization in this blog, and having big pieces of content disappear in the eyes of the search engines is just bad business.   And with mobile access accounting for a significant and increasing percentage of all web traffic, having a page load up sans-Flash elements on an iPad or other mobile device is just not acceptable.

Trust me, I know Flash’s value.  Flash was the cornerstone to a multi-million dollar annual business I once ran.  I “get” Flash.  But I must also admit that Adobe has done a terrible job with the technology from a technical standpoint.  Most end users see the “cool” results of Flash in action, but don’t realize what goes on under the hood (and thus never really understood Steve Jobs’ main issues with Flash).   Flash is notoriously buggy, and a huge resource hog.  When it crashes (as it constantly does) it looks like your browser crashed.  Or Windows / Mac OSX. etc.  The vast majority of the time when things run slow or crash entirely, end users blame the web site or the OS or the browser, never realizing that the *real* culprit is the Flash plugin!    And on mobile, it just drains batter and resources way too fast — it’s a massive resource hog.

Adobe has been sprinting towards producing next-generation HTML5 development tools, in essence obsoleting its own technology.   I do not begrudge Adobe the opportunity to make a buck.  Not at all.  I hope they make just as much money with their new HTML5 tools.  I merely applaud the move to make the money from new HTML5 tools versus from Flash tools. And, in the process, allowing the industry at large to all start pulling in the same direction and accelerating the speed of adoption of these new open standards.

It’s good for the industry at large and for end users, who will see better, faster and more responsive web apps on both smartphones and desktops.

 

space_station_flyover

This posting basically has nothing to do with anything related to this blog, but is just a very cool little digression from day to day business in order to marvel at the wonder that is Earth.

If you pay attention and process quickly, you may notice the Great Lakes in the U.S., the Sinai Peninsula, Italy’s “boot” and more.  The flashes in the clouds are lightening, and the night scenes are amazing – especially those showing the green magnetic “aurora” effects in the atmosphere!

Enjoy!

classic cherry chapstick

Chapstick evidently didnt “get it,” and they’ve paid a huge price while taking a big hit to their brand.  But the story serves as a great reminder for all business folks, albeit at Chapstick’s expense.

It all began when they started running an ill-conceived ad of an attractive woman losing her Chapstick behind the couch. The print ad was essentially a huge shot of her bent-over, skinny-jean-clad backend.

Regardless of whether you think the ad crossed beyond the line of good taste, or couldn’t care less one way or the other, the undeniable fact is that it caused a (negative) stir and consumers started saying so, posting negative feedback comments on the Chapstick Facebook fan page.

In this case it went viral in the worst sense — like its real world brethren, a contagion of negativity and dissent.

What happened next was downright shocking to anyone who works in social media: the folks at Chapstick started deleting the negative comments!

Presumably the folks managing the Facebook presence of a national mega-brand ought to know better!  This breaks one of the cardinal rules of social media. It’s like censoring a newspaper and removing any articles critical of the government or a certain person or business, for example.

Social media is supposed to be about engaging your audience and interacting with them. This would have been a non-issue (and non-story) if they had merely responded to the negative posts with empathy and a promise to rethink their approach.

A simple “gee, we’re sorry you were offended. We certainly didn’t mean that. We were just trying to be funny. We’ll pass along your comments and see if the creative team can rethink their approach” would have not just quelled the negativity, but in fact would have been a major “win” for the brand. The folks at Chapstick would have demonstrated that they listen to their customers, and are responsive and approachable.

That sort of approach would have been exactly what social media is all about — interacting and engaging your audience and being responsive.

Instead, by trying to cover up the problem by deleting the negative posts, they just inflamed the community. Now even the people who didn’t care about the original ad were taking up arms.  It wasn’t the ad that was the issue, it was the handling of the issue — the censoring of comments.

The story grew legs, so to speak. Facebook postings went thru the roof.  The Twitterverse went viral with the story. And even worse for Chapstick — it crossed over into the mainstream media!  It’s been a PR disaster.

Like Watergate, it was the cover-up that inflamed a citizenry.

Lest any reader get the wrong idea here, the takeaway from this is not to stay out of social media — do that at your own peril.  As I always say: the conversation is going to go on with or without you. If you don’t participate then you have no hope of ever steering it or, in times of trouble, “setting the story straight.”

No, rather the issue here is how one handles its presence.

C’mon people, it’s not that hard. It’s like you were taught as a kid — honesty is always the best policy. If a bad situation arises, tackle it open and honestly, head on. Your customers will appreciate you for it.

That is the takeaway from this debacle.