FeedBurner feeds will be discontinued today. They should redirect from Google for thirty days, but you should update your subscriptions immediately. The shortcut links below are to the new locally hosted locations.
The Linkage feed through Google Reader will be discontinued today. Future Linkage will appear on Twitter.
I have always preferred to run everything on this site locally, without relying on third-party services. On a few occasions in 2009, I lightened up on this policy and expanded a few things outside my control.
Most notably, I migrated the photograph gallery to Flickr
, started using Google Reader
to publish shared links of interest ("Linkage") and began providing RSS feeds through FeedBurner
. Overall, I have been pleased enough with these arrangements.
While I continue to worry about the future of Flickr under Yahoo!
, my experience there has been excellent. Although my primary motive was to reduce the overhead in managing the gallery and costs of hosting, the unanticipated result has been the far-wider audience my pictures have received worldwide.
license that I now just link to the license
here. But so long as the service remains essentially the same, I will continue to pay for a Pro subscription and keep my images on Flickr.
Since I was already using Google Reader as my RSS aggregator, using its sharing feature to publish Linkage was a logical progression. I enjoyed the fact that this content could be viewed as a list in the sidebar, on a stand-alone page
with images and via RSS.
Yesterday I learned of Google's plans
to "clean things up" as they said, referring to the discontinuation of sharing, following and friending inside Reader. Instead, new Google+
integration is designed to take over. By forcing this change, the usefulness of this product for me has just gone to zero.
, my first choice as an alternative RSS reader, has so far proven to meet my needs. I did not find any add-ons to share feeds from Thunderbird, so I will now be posting Linkage on Twitter. This works immediately, the only issue being that my script does not yet interpret the newish Twitter shortlinks (e.g. http://t.co/AkgyGG0v
). With that fixed, I think this will work out fine. UPDATE: this issue has been resolved.
Finally, I have decided that the cons outweigh the pros with regard to using FeedBurner. I had originally sought the compatibility features and web front-end, but I find that my site's feeds are often delayed for no reason. RSS is ubiquitous and while Chrome
still mysteriously has no internal means of displaying feeds, the other four major browsers now do.
I hate that it may be a hassle for those two or three subscribers to update their feed software, but think it is better to cut this cord before I have an even more compelling reason to do so.