Have fun. If you start using this, or start writing your own, I'd like to hear what you think. I made an account on my installation for Sumana so hopefully I can get some user feedback from someone who's not me.

Update: I redid the web page to make it more user-level "why you need a recommendation engine" and less academic "why is this recommendation engine different from all other recommendation engines?", since the latter is now well-covered in the paper.

In response to questions re: the naming of the Ultra Gleeper, especially Riana's question: I used to watch the 1980s sitcom "Out Of This World" but cannot recall any gleeping therein. The Ultra Gleeper is just a happy innovation that wants to gleep the web for neat things to show you and make you happy.

What XR7 said, plus anything beginning with /users/ or /user/, is what I use when stemming URLs of referrers to my site, and it works surprisingly well, though of course it has a pretty limited group of URLs to sort in that case.

By the way, I tried installing the Ultra Gleeper, and got this error when it came time to run UserGleeper:-bash-2.05b$ python gleeper/UserGleeper.py Traceback (most recent call last): File "gleeper/UserGleeper.py", line 1, in ? from Gleeper import GleeperImportError: No module named Gleeper...any idea what might be happening?

Aw, crud. That's the nonexistent parent class of UserGleeper. I removed it as cleanup while I was prepping the release, without checking if it was still used. Just get rid of the references to Gleeper in that class, or get version 1.0.1, which I just released, which does it for you.

Originally I thought that all the scripts would be Gleepers of a sort, and the Ultra Gleeper would be their conjunction. But then I realized that all the other scripts were just doing standard web crawler/RSS aggregator stuff, and the only real magic was in UserGleeper. So I renamed most of them to *Finder, but the Gleeper superclass remained. Such are the perils of basing your architecture around an undefined nonsense phrase.