Once upon a time, the jobs in journalism were all at what we would consider traditional outlets — Time, Newsweek, ABC News, the Washington Post, etc. But these days, journalists who’ve had their pick of those publications are flocking to tech companies like Tumblr, Facebook and Twitter to create stories — content that competes, in breadth and scope, with the highest-caliber traditional publications. As print suffers a slow and painful decline, it’s not just the web that’s changing journalism as we know it — it’s tech companies like Tumblr and Facebook who are launching what could be the new new media movement. But what does this mean for the future of traditional journalistic outlets? Can a journalist remain objective when she’s employed by a company? Are journalists’ future homes in places that aren’t primarily about journalism, and should it be?
Interesting question. A thought on this: Tumblr is also creating a community of writers and journalists who wouldn’t need a job with traditional media with a little help on the traffic or monetization side. It’s one thing for Tumblr to hire people. It’s another for Tumblr to enable people to make their blog their full-time gig — so folks like those who went to Tampa and Charlotte to cover the conventions could rely on their work as their main source of income. There’s a lot more opportunity in that market (they already have the content verticals, without even really trying), and Tumblr could do more to tap the community’s creativity so it becomes sustainable creativity, the kind that strengthens the work they’re already doing.
Well after three years of free satisfaction and 20k users later, the road to maintain a good Wordpress plugin just got bumpier.
Users started asking questions and sending support requests. Tumblr had changed its API from v1 to v2, bringing a more secure way for their developer community and users to post stuff on their platform.
Naturally, Tumblr also started deprecating their v1 API thus making tumblrize useless for most of the install base.
I started this plugin right after Tumblr’s rise. I couldn’t make a choice between them and Wordpress. So I started working on something. Without any need for recognition, my plugin became the first to be able to cross-post to Tumblr. I was very proud to see it grow back then, and being referenced by Tumblr as example app for their API.
I had fun spending hours designing its poor logo on Fireworks.
Then I had something else to focus on. I switched jobs, switched again, and Meitar came to the rescue as for long needed updates. He helped a lot cleaning the code and adding new features.
Long-story short: neither do I (because of time and skills) nor Meitar (because of time) have time to update it. I wrote to a guy who pulled it from the Wordpress plugins repository.
I wish I could have answered all the questions or pushed a “thank you but it’s broken” message to those who were using it.
Thanks to Meitar for helping out and Mark@Tumblr for promoting it.
In case anyone’s interested: About a week ago, Tumblr shut down posting functionality to v1 of its API, requiring anyone who uses it to register and use v2. This broke a few plugins, most notably Tumblrize, one which SFB used a modified version of to do our cool numbers and blurbs and stuff. (I even gave ‘em props in an interview once!) Unfortunately, the developers (who did great work over the years and deserve a ton of credit) don’t have the time to do necessary updates to the plugin, so they retired it. There aren’t a ton of options that do what Tumblrize did at the level it did (Example: IFTTT kind of does it, but not very well), leaving a number of WordPress users in a bit of a lurch. In case any developers with Tumblr API and WordPress plugin experience are interested in helping out a community in need, there’s a definite gap here. — Ernie @ SFB
EDIT: We might be willing to chip something in financially to make this happen. Shoot us a message if this might interest you.
twentysomethingfloater says: in the words of ed love, “C’MON SON”. Those pws were basic, ya’ll gotta step your game up some degrees. I mean, ya’ll a pretty big deal, of course people are gonna try to hit you.
» SFB says: We had secure passwords. Matt was making a joke. We worked very hard to prevent this from happening after the first round — to the point of removing app access from the backend — and apparently that wasn’t enough. We’ll work harder to ensure security in the future. — Ernie @ SFB