Facebook takedown followup: what happened and what FB needs to fix
arstechnica.com
arstechnica.com
This is why my advice remains: Do what people have done for almost twenty years. Make a website. Do your stuff on your website. If you have anything worth while, people will come to your website. Stop handing the keys to the internet over to Facebook both by using their services directly or spamming your own site and uglifying it with Facebook Everything widgets.
Using Facebook as your web presence strikes me as about as professional and makes you look about as serious as using Angelfire or Geocities, anyway.
Someone in the comments on the first Ars Technica article wrote that Facebook took down the page for one of their websites (a wiki) and they lost loads of visitors because of that, never recovered, closed it down.
And yes, it is 'bad' and given those events 'not smart' to rely on Facebook for bringing in your visitors. But that's where they are at these days. And Facebook just 'randomly' killing pages, accounts, content is just messed up.
My point is basically: you can't really avoid/ignore Facebook if you want to get your name out there. (Sure, this might not apply to everyone but you get it.)
If the idea is that people will no longer bother going to a website or surfing the web in general unless "facebook.com" is somewhere in the URL and/or that they will only communicate with you via forums, wall posts, messaging on Facebook itself and nowhere else, then . . . well, I give up. That's not a world in which I want my service or site to exist and I'd rather not do it at all than do it as some sort of trivial Facebook Serf on their land, by their rules, and with their citizens. If we've come to the point that the entire success and popularity of a service and its continued lifeblood is owed to existing on and interacting via Facebook, then we should wave the white flag and admit we have lost the internet.
I think the smart thing to do is to take precautions. Host your content and auto-post it to Facebook, Twitter, etc. You should also have some way to contact your users/fans directly so that if things like this happen you can notify them.
I'm speaking from limited experience, of course, and with a service that established itself long before social networking even existed. I think the premise is still sound, though.
In a similar way, a lot of people (many of them not willing to put up with things like 'feed readers') are probably on Facebook like 'all the time' and will only drop by and check your site if they see some activity on your Facebook page. In other words: Facebook is like their feed reader or news aggregator. And all of a sudden, Facebook comes along and completely removes your feed...
And just to make that clear: I never liked Facebook although I have been active in many many online communities throughout the years. But Facebook just feels too corporate, serious and overall 'not cool' to me, meaning it's hardly any fun. I just want to express that they have got a lot of influence these days and the way they are going on about certain things can cause serious damage.
If you skip FB, you're skipping a lot of eyeballs potentially. If you get those eyeballs, it's up to you to keep them interacting directly sans-facebook afterwards.
For all those people trolling around complaining, the real complaint should be that illegal DMCA takedown requests are rarely followed up on in court. (In other words, Ars would do society better by suing whoever made their content get taken down.)
From ChillingEffects.org the service provider is then required to restore the material Not sure how forceful required is.
As several people have mentioned in these topics, the only real issue is Facebook's failure to handle counterclaims properly. That's how the DMCA is supposed to work. You file a copyright infringement claim, the host takes down the material. I file a counterclaim, the host puts the material back up, and it's up to you to sue me.
If they just responded promptly to counterclaims, the hand-wringing about bogus claims is mostly irrelevant.
The problem isn't process, the process is a symptom of not caring about their users.