Building Better Blog Tools
Today is one of those days I can’t get ideas out fast enough and it’s very frustrating. It all started with the idea of me setting up a work blog internally. The things I’d like to use it for are as follows.
- Give project updates as things progress.
- Clip interesting posts from other blogs to my work blog.
- Code review with peers.
- Share experience and tips as I find them.
So, I talked with my friend Ryan about the best interface for clipping from a blog and having a tool grab the pertinent RSS area. Turns out we want the following process to appear to users who want to linkblog.
- Right click a permalink for a blog.
- Click “clip this”.
- Full contents of the article (taken from rss item block) are credited and syndicated in new blog.
We didn’t care if this behavior was in an aggregator like Bloglines, or a plugin to Firefox that posted the necessary information to WordPress. We didn’t care if the tool created a feed somewhere that a WordPress plugin could read, or if it spoke directly with WordPress. What I wanted is a tool to automatically clip a post and make the clip go live on my site.
Inspired, I downloaded another cvs copy of WordPress and started to hack on this. But in the midst of that, I started thinking about how co-workers were going to use the internal blog, and I realized they should be able to read the blog from anywhere. Okay, so I want a private blog that’s accessable anywhere… riight. The only practical, scalable solution for this is to use a VPN. Okay, no biggie, we need a VPN anyways at work. People connect to VPN, they can read the dev-blog and get RSS now.
But shit, I don’t get RSS, Bloglines gets it for me, and there’s no chance in hell of them getting into my VPN. The whole point of putting it on an intranet is so Bloglines and other people can’t read it. >_<
How do I fix this? Install Bloglines behind the VPN so it can access the site and serve me my feeds over a secure connection. But I can’t install Bloglines, I don’t own it.
So, Mark Fletcher, I know you’ve been concerned with a revenue model for Bloglines. If you’re reading this, please, take heed. Either offer a separate Bloglines installation to my employer for a reasonable price, or open source the Bloglines engine. Bloglines has overcome the performance problems I’ve complained about before and I’ve come to love your service because of the user interface. I hope that you see that your unique value, to me, is in your interface, not your centralized service. For the most part, AmphetaDesk does the same centralized aggregator deal, but its interface is terrible. You’re kicking ass when it comes to centralized aggregator user interface.
Even if your strategy for Bloglines is as a portal, as you imply in your recent writings, there’s no reason licensing of your engine can’t provide supplemental revenue. Google does it, I don’t see why you can’t. Allowing custom installations is valuable to the enterprise market with VPNs, it’s valuable to anyone who can’t use your service because it belongs to you alone. Better yet, make the engine extendable, let me customize it. Create great hooks for a plugin system. Open source Bloglines, and sell dual-licenses like MySQL. Give discounts to educational institutions. Really add to the Bloglines web-service, give us way more options than we have now. I don’t care how I get to customize it, as long as I can for a reasonable cost.
You see, as it stands, your centralized hosting hurts me. I know it allows users to get feed suggestions and search feeds for topics, but I’d really be interested in hearing how many users actually are using that functionality. My guess is few, though I may be wrong.
Bloglines is a great aggregator and there are many things I’d like to modify and tweak but I just can’t. Take the clipping solution I’d like above. This would be so simple if when bloglines clipped a post, it offered to keep the original rss item block instead of a link back to Bloglines. If your clipping feature built a custom rss of my clips, I could easily use it and syndicate the “best of” my blogroll. Alas, you probably won’t implement this feature in a timeframe reasonable to me, but if I could could somehow extend your system… well, then the sky would be the limit.