torrent

I have a new obsession hobby. This past weekend, I discovered BitTorrent, a cooperative distribution protocol for sharing large files. In my case, it’s a way to get concert recordings (of artist who approve of that sort of thing) without having to set up a snail mail trade with someone and hope it works out … Continue reading “torrent”

I have a new obsession hobby. This past weekend, I discovered BitTorrent, a cooperative distribution protocol for sharing large files. In my case, it’s a way to get concert recordings (of artist who approve of that sort of thing) without having to set up a snail mail trade with someone and hope it works out for the best. It’s fast way to distribute shows, too. I was able to download a show yesterday that was recorded the day before!

The key to scalable and robust distribution is cooperation. With BitTorrent, those who get your file tap into their upload capacity to give the file to others at the same time. Those that provide the most to others get the best treatment in return. (“Give and ye shall receive!”)

Cooperative distribution can grow almost without limit, because each new participant brings not only demand, but also supply. Instead of a vicious cycle, popularity creates a virtuous circle. And because each new participant brings new resources to the distribution, you get limitless scalability for a nearly fixed cost.

So, what’s the library world application of this kind of protocol? The obvious one that comes to my mind is distribution of electronic publications. If part of the difficulties of publishing electronically is the cost of maintaining the backfiles, then perhaps publisher should look into a BitTorrent-type distribution model where everyone who is interested in the electronic content shares the burden of distributing it on demand.

I’m not sure if this would work in libraryland, but it certainly makes it a lot easier to share concert recordings.

nasig part four

This one is a bit long. Sorry about that.

This one is a bit long. Sorry about that.

Continue reading “nasig part four”

nasig part three

The Friday vision session was given by Marshall Keys. He spoke about the chaotic transitions brought on by technology. He said that the “future of libraries depends on their ability to meet the emerging needs of users” and that we need to first understand what those needs are. None of us know what tools we … Continue reading “nasig part three”

The Friday vision session was given by Marshall Keys. He spoke about the chaotic transitions brought on by technology. He said that the “future of libraries depends on their ability to meet the emerging needs of users” and that we need to first understand what those needs are. None of us know what tools we will be using in libraries in the future, but we should keep aware of trends and try to anticipate them.

Keys talked about the “blog mentality” of the younger generation of library users:

  • What I think is important
  • What I think is important to other people
  • Something is important because I think it is important (“Whatever” corrolary: If I don’t think it is important… whatever.)
  • Privacy is unimportant
  • Community is important

The last two aspects of the “blog mentality” are particularly relevant to library technology. Emerging users want community, personalization, and portable technology, and they are willing to have it all at the expense of a loss of privacy. For example, they want to know what their peers are interested in, and they can get that kind of information from places like Amazon, Netflix, and Friendster, but not from the library catalog.

Another point on technology that Keys made about our emerging users is that the phone is their primary information appliance, and as the sales of ringtones indicate, these users are willing to pay for the ability to customize their tools. One not-so-emerging proponent of a phone as a primary information appliance is the Shifted Librarian herself, Jenny Levine, and her treasured Treo. She and Marshall Keys would make for an interesting pair.

Side note: I am writing this in the SeaTac airport while waiting for my shuttle back to Ellensburg. At a nearby table is a ten year old girl and her little sister along with her father. Just now, he was having trouble with something on his cell phone, and she took it and showed him how to do what he wanted to do. I suppose I shouldn’t be surprised that someone so young would know more about how to use the phone than the person who owns it, but I am anyway.

The point that Keys was trying to make was that if emerging users consider their phones to be primary sources of information, then we need to be developing reference tools that acknowledge that reality. There are text message services that answer questions quickly for a nominal fee, and if our users are more inclined to pay for that service rather than come to us through traditional methods, then we need to consider ways to implement similar services. We also need to face the reality that a majority of library functions can be outsourced off-shore, including technical services and reference services. If we aren’t preparing for this eventuality, then it will be even more difficult once it happens.

Keys stated that, “a wealth of information creates a poverty of attention.” If we aren’t prepared to provide accurate information quickly to our users in the formats they prefer, then we will become irrelevant.

feeds for indie rock fans

In case you haven’t heard, indie rock label Sub Pop offers a variety of RSS feeds: multimedia downloads, label news, and artist/band tour dates (including feeds for specific states/countries and artists/bands). The multimedia downloads are a mix of Quicktime and mp3 files, and I don’t know what that might do to your iPod or other … Continue reading “feeds for indie rock fans”

In case you haven’t heard, indie rock label Sub Pop offers a variety of RSS feeds: multimedia downloads, label news, and artist/band tour dates (including feeds for specific states/countries and artists/bands). The multimedia downloads are a mix of Quicktime and mp3 files, and I don’t know what that might do to your iPod or other portable digital audio music player.

(This just reminded me that I had a dream last night about owning an iPod. Hm.)

rss agregator

I have been using Feed on Feeds as my RSS agregator for the past month, but I have decided to go back to using Bloglines. I liked the clean lines of Feed on Feeds, as well as the ability to host my feeds on my own website. However, it uses Magpie RSS to parse the … Continue reading “rss agregator”

I have been using Feed on Feeds as my RSS agregator for the past month, but I have decided to go back to using Bloglines. I liked the clean lines of Feed on Feeds, as well as the ability to host my feeds on my own website. However, it uses Magpie RSS to parse the feeds, and it can be quite persnickety if the feed does not completely validate. This limited me in the feeds I could track, as well as causing headaches every time I tried to update the feeds. Also, I couldn’t get the silent update feature to work. I tweaked my crontab file until I was blue in the face, but nothing worked. Overall, Bloglines requires less maintenance or headaches on my part. Feed on Feeds has great potential, but for now, I will give it some time to mature.

redirects

I set up my feed on FeedBurner to pick up the index.xml file, and then I stupidly created an .htaccess redirect for that file that sent agents to the FeedBurner feed. Thus, the FeedBurner feed was stuck in a loop and wasn’t being updated. I fixed that just now by creating a copy of the … Continue reading “redirects”

I set up my feed on FeedBurner to pick up the index.xml file, and then I stupidly created an .htaccess redirect for that file that sent agents to the FeedBurner feed. Thus, the FeedBurner feed was stuck in a loop and wasn’t being updated. I fixed that just now by creating a copy of the index.xml feed and directing FeedBurner to pick that up instead. Those of you reading this blog via RSS will suddenly have several new posts.

D’oh.

feedburner

One of the problems of offering RSS feeds instead of making people come to one’s website to read stuff is that one does not have any good way to measure the number of eyes one is reaching. Thus, I was pleased to learn about a beta service called FeedBurner that will keep stats for you, … Continue reading “feedburner”

One of the problems of offering RSS feeds instead of making people come to one’s website to read stuff is that one does not have any good way to measure the number of eyes one is reaching. Thus, I was pleased to learn about a beta service called FeedBurner that will keep stats for you, and even throw in some Amazon links and ads for revenue purposes, if you like. I prefer the vanilla for this site, as it is only a labor of love. I am now serving my feeds through FeedBurner and as soon as my host fixes some intermittent FTP issues, I’ll be redirecting my current feeds through FeedBurner. However, you can get ahead of the game by subscribing now. [thanks wil]

gmail atom feed

Cool! I just noticed that I can grab an Atom feed for my Gmail inbox. After doing a quick search on this, it seems that I’m about four months behind on this news. I probably won’t use this, since I hit my feed aggregator once or twice a day. I much prefer the Gmail Notifier … Continue reading “gmail atom feed”

Cool! I just noticed that I can grab an Atom feed for my Gmail inbox. After doing a quick search on this, it seems that I’m about four months behind on this news.

I probably won’t use this, since I hit my feed aggregator once or twice a day. I much prefer the Gmail Notifier sitting my systems tray.

rss feed

Sorry for all of the weirdness with my RSS feed this week. I had some issues with MovableType and I’ve been tweaking my feed setup. It should be stable from now until I decide to tweak it again.

Sorry for all of the weirdness with my RSS feed this week. I had some issues with MovableType and I’ve been tweaking my feed setup. It should be stable from now until I decide to tweak it again.