Own your social media–install Storytlr

I guess I’m just not very trusting, because I like to have copies of my data.  I host my own blog, rather than use blogger or wordpress.com.  I host my own email (or at least one of my two main accounts).  I prefer to document interesting things on my blog, rather than a site like Quora or Stack Overflow (though I do have an account on the latter).  Heck, even though I use an open ID provider, my own domain is the master, and I just delegate to myopenid.com.

So, since I recently have been putting a bit more effort into my social media presence (you can find me on twitter here), I looked around to find a backup solution.  I did find one–Storytlr–via this article on backing up your twitter feed.  It apparently used to be a hosted service, but now is open source–code here, install instructions here.  (There’s at least one for pay service too, but then, you don’t really own your data, plus I’m cheap.)

It was pretty trivial to install.  I ran into this issue with Storytlr not recognizing that PDO was installed, but the fix (hacking the install script) worked, and I didn’t run into the Zend error also in that bug post.

I also ran into an issue where I chose an admin password of less than six characters on install.  Storytlr was happy to let me do that, but then wouldn’t let me enter the exact same password when I was logging in for the first time.  To fix this, I had to update the password column in the users table with a new MD5 string, created using this tool.

So, what does Storytlr actually give me?

  • Access to my data: I set up feeds to be polled regularly (requires access to cron) and can export them to CSV whenever I want.  And I keep them as long as I want to.
  • One single point of view of all my social content.
  • Really easy way to add more feeds if I join a new social network.  Here are the sites/networks Storytlr supports right now.

The issues I ran into are:

  • Technical issues, resolved as documented above.
  • No support for facebook.  (Well, there’s this experimental support, announced here, but nothing that is part of the project.)  This is big, given how bad Facebook is with respect to privacy.  I am not sure what my next steps are here.
  • Not wanting others to have access to my lifestream.  This was easily fixed with a Auth directive.

If you are depending on social media sites, have some technical chops, a server to host it on, and want to ensure a historical archive, you should look at Storytlr.

What did I ship in 2010?

In the spirit of this post, I wanted to outline what I shipped this year.  (Shipped in the sense of software–building something and putting it out to the world.  Personal achievements in the past year, not least of which was getting married to my lovely wife, aren’t in the scope of this list.)

  • 41 blog posts on this blog, and 95 posts on two others I run.
  • Many, many releases (over 20) of COhomefinder.com.
  • Released version 2.0 of a dating site for the mentally ill.
  • Rewrote my Colorado CSAs directory and vastly increased the number of CSAs contained.
  • With a team, researched and presented a plan for a local Boulder currency.
  • Scoped, built (with a team), and launched an ecommerce website.
  • Set up a scholarship for a permaculture course.

As Seth said about his list, there were other projects I didn’t have the guts or follow through to launch, but I’m pretty happy with this list.  Here’s to 2011!

Shuttering a blog

Not this one!  But recently, as part of an effort to simplify my life, I’ve shuttered a couple of blogs I had been running for a while.  Here’s my list of best practices to do so:

  • Forgive yourself.  Running a blog is a lot of work, so if you don’t have time to do it adequately, it’s better to admit it than to do a poor job.
  • Try to find someone else who is interested.  If you’ve built up a following (you know how many visits you’re getting a day, right) and want to continue to see whatever topic you are blogging about more fully explored, you may be able to find someone else.  If you do, make sure to add them as a contributor, and discuss where they see things going from there–do they want to fully take over the blog, just write the occasional post, or what?
  • Announce the hibernation on the blog.  Feel free to phrase is as a long pause, or a hibernation, or whatever, but make sure you tell your readers.
  • Leave the content up for as long as you can.  Consider moving it to a different server if you need to consolidate, but if you’ve put up useful posts, people will continue to visit via search engines.
  • Leave up your contact info as well.  I’ve had several emails about my shuttered blog, and they’ve actually spiked my interest to start writing again.
  • Shut down your CTAs; for instance, I had a newsletter signup on one blog.  To me, it’s not fair to ask people to give their email address if I’m never going to send them useful content.  Along with the previous two suggestions, this is really about being respectful of your readers.

Do you have any tips for shutting down a blog in a graceful manner?  Here’s an interesting post on the topic, but written from the perspective of a more professional blogger.

Blogger adds support for pages

I’m a big believer in simple websites that users can maintain–I wrote about how to set one up in less than two hours.  Snarky comments from Ralph aside, it’s a great way to get onto the web and add that much more credibility to any business you’re doing.

Blogger and WordPress.com are the two big options for easy, free web sites.  Blogger gives you more freedom in most ways, but until recently, came with a big downside–you couldn’t create standalone pages (for contact info, ‘about us’, etc)–everything had to be a post.  That’s changed: blogger now lets you create up to 10 stand alone pages.


Upgrading WordPress is shockingly easy

I was all set to write a post about my experience with the most recent BDNT, when I got distracted by an excellent post from Josh Fraser about never using captchas–excellent post well worth the read. After reading through the comments, mollom seemed like a great way to avoid captcha and comment moderation, and I decided to give it a try. However, mollom didn’t work on my ancient version of wordpress (2.0). This being a weekend I’m heading out of town, it seemed like the perfect time to upgrade my wordpress site (the backend–I hope you’ll notice that the soothing front end look and feel hasn’t changed).

I browsed through the releases list to find the oldest one with automatic upgrade functionality, and then followed the quite painless upgrade guide. From there, it was a pretty simple matter to automagically upgrade to 3.0. Shockingly easy.

Overall, it looks like there are a few snafus–the home page didn’t have a sidebar because of post content for a bit, my tagging plugin doesn’t appear to be compatible with this version of wordpress–but it looks like all the content is there. If you see any content that looks broken, and you feel charitable, please post a comment on this entry.

Why Are You Following Me on Twitter?

Don’t you know that I’m a web developer posting geeky stuff and you’re a bar posting specials?

I joined the Twitter movement a while ago (not a first mover by any means) but have been actively using it more in recent months.  I find it useful as well as diverting.  However, I don’t want to discuss how I use it right now; what I want to focus on is a behavior that interests me.

It seems if I follow someone, mention anyone by name, or tweet on a topic of interest once, there’s a reflex for people to follow me.  This doesn’t happen all the time, but happens often enough that it bears examining.  Why would someone do this?

  • if I posted once on a topic of interest, I might post again
  • it’s easier to follow and then unfollow than it is to read my twitterstream and see if I’m actually worth following
  • I might follow someone who follows me, and followers are good
  • Someone might know me (online or offline) and a tweet might have alerted them to my presence on twitter
  • Someone might have seen my tweet, clicked through to my profile, and thence to my website, read a couple (or all :)) of my posts, considered whether or not I might have more of interest to say, and followed me.

Those are the main reasons I can think of.  Did I miss any? Oh, and the last couple are improbable, based on my web stats.

I think it’s early in the Twitter game, especially for the pragmatists (Twitter having crossed the chasm), and it feels like the early days of my RSS reader (when I first discovered the wonderful world of blogs).  Any time I stumbled upon a blog that had an interesting post, I added the blog’s feed to my RSS reader.  Eventually, I was following hundreds of blogs.  For a while, I kept up, reading the new posts diligently, but because of real life and work, I fell behind.  Now, I rarely open Bloglines–I know which blogs I want to check out and just visit them directly.

I think the same thing can happen to your twitter home page–if you add people indiscriminately (or even slightly discriminately) you risk polluting it and decreasing its value.  Note that I don’t use any of the tools built around Twitter.  They may help manage this issue–and I hope they do.

Because it is so easy to follow people on Twitter (easier, in fact, than determining whether it would be worthwhile to follow them), it’s also easy to clutter up your experience.  In the end, I believe this clutter will either drive you away from Twitter, or force you to spend time unfollowing (or, as Dion put it, “gardening”).

Technorati Tags: , ,

Four year blogaversary

It’s been four years and a few days since I started writing this blog. It’s been a great experience. I’ve had good months (15 posts) and bad months (1 post), but I’ve written 352 posts over the last four years. I’ve learned a lot from this blog–how to shoot my mouth off, how to acknowledge mistakes in public, and how to write a post that gets hijacked by others for their own purposes. I thought I’d take the opportunity to highlight four of my favorite posts.

  • Business Process Crystallization: This is a nice little post about how software is both shaped by the business process it will assist and shapes that same process. It’s one of my original thoughts–at least I haven’t seen too much literature taking this view of software.
  • Installing the median user defined function on MySQL: I always enjoy step by step tutorials, and this is one of the better ones I have written. I also enjoyed the challenge of making a mysql user defined function work when I’d never done any significant C development.
  • The Social Life of Information: This book was a slow read, but explains a fascinating concept–that much of the information we receive is contextual and connotative. This was a revelation to me, since I’m more comfortable with denotative, explicit information.
  • Step By Step: A Mortgage Calculator using GWT: I enjoyed this blogging experience, the entire series. My client and I worked together to release a site repeatedly over a week, as well as releasing the source code and documenting the entire experience of learning, developing and deploying a new technology.

Marc Andreessen considers his blogging

Well, Marc Andreessen has been tearing up the blogging world, with prolific excellent writing including his series on the truth about venture capitalists and his ongoing series on startups, among others. But after 5 weeks of blogging, he has written about 11 lessons he’s learned from blogging. It’s an interesting read, and I think every blogger wants to be a little self referential, as the feelings tha blogging evokes are powerful. Heck, I did it myself. I hope he proceeds back to regular content, as opposed to blogging about blogging, quickly, but I do think he makes some strong points, especially #5:

Fifth, writing a blog is way easier than writing a magazine article, a published paper, or a book — but provides many of the same benefits.

I think it’s an application of the 80/20 rule — for 20% of the effort (writing a blog post but not editing and refining it the quality level required of a magazine article, a published paper, or a book), you get 80% of the benefit (your thoughts are made available to interested people very broadly).

I encourage everyone who is interested in not being a commodity to blog (and that pretty much means everyone!). Because of the widespread distribution, if you have something interesting to say (and I believe pretty much everyone does), you can quickly gain readership. It’s the best form of marketing for individuals that there is.

That doesn’t mean blogging is easy–there are posts I’ve written on this blog that, as I read back over them from a few years on, are rather embarrassing (technical mistakes, pompous pontifications, etc). But the benefits to having a nearly four year public collection of my thoughts and interests including some very useful and articulate posts, outweighs the less than stellar bits.

Does any other blogging platform approach WordPress?

This person’s answer is ‘No!’. Looks like someone in the blog platform world has declared that the WordPress community has learned the lessons the Struts community learned a few years ago: If you document an open source system, provide plenty of examples and a supportive community, you can distance yourself from your competitors. Make it easy for the developers (QT) to choose you!

He states:

…the blogging market is c.l.o.s.e.d. – as in no more room, and most importantly, no more competition… [emphasis his]

(Regarding the strength of Struts, as of today, Dice has 1965 jobs matching ‘struts’, versus 176 for ‘rails’, 1481 for ‘spring’ and 493 for ‘JSF’. Now, it’s been a while since I commented on web frameworks, but it’s a pleasant surprise to see Spring approach Struts. Yes, yes, my methodology for documenting the ‘distance’ of Struts from its competitors is somewhat suspect. I don’t have access to book trends data, and what I can find doesn’t break things down to the framework level. Thanks for caring.)

However, Spring looks to be on the rise; even the most popular packages and/or platforms can fall from popularity. Especially in technology, where “new” is often a feature. Hence, I disagree with the statement that WordPress has locked down the blogging application market. My point is not argued from a knowledge of WordPress, but rather a knowledge of technology and tech trends.

Via sogrady.

Technorati Tags:

© Moore Consulting, 2003-2017 +