-
badges
-
meta
-
categories
-
tag cloud
Nintendo pain horoscope quiz bored eBay feeds insurance hacks batteries massage Sierra Vista free opensource bullshit appointments flickr word of the day Firefox mp3 speed test opml livejournal rant quickie images Nokia last time youtube 802.11 pbs computers security ideas food California cable Yahoo! mail Cox gmail TiVo primary treating physician story news humor Google Negative Orange County PHX OpenID sleep aggregator reuters freedbacking EFF email libra SCIF money laptop maps dad mobile cringley education boredom boing boing crap adjective microsoft beta doctors Arizona information news yahoo -
archives
- October 2008 (4)
- September 2008 (15)
- August 2008 (29)
- July 2008 (16)
- June 2008 (18)
- May 2008 (23)
- April 2008 (16)
- March 2008 (8)
- February 2008 (17)
- January 2008 (10)
- December 2007 (7)
- November 2007 (16)
- October 2007 (11)
- September 2007 (16)
- August 2007 (3)
- July 2007 (23)
- June 2007 (22)
- May 2007 (13)
- April 2007 (8)
- March 2007 (11)
- February 2007 (15)
- January 2007 (14)
- December 2006 (28)
- November 2006 (13)
- October 2006 (8)
- September 2006 (9)
- August 2006 (12)
- July 2006 (35)
- June 2006 (62)
- May 2006 (47)
- April 2006 (17)
- March 2006 (9)
- February 2006 (6)
- January 2006 (3)
- October 2005 (51)
- September 2005 (43)
- August 2005 (58)
- July 2005 (24)
- June 2005 (24)
- May 2005 (17)
- April 2005 (11)
- March 2005 (21)
- February 2005 (27)
- January 2005 (41)
- December 2004 (2)
- November 2004 (6)
- October 2004 (36)
- September 2004 (29)
- August 2004 (14)
- July 2004 (45)
- June 2004 (48)
- May 2004 (47)
- July 2003 (2)
- May 2003 (4)
- April 2003 (10)
- March 2003 (2)
- February 2003 (12)
- January 2003 (14)
- December 2002 (3)
- October 2002 (1)
- September 2002 (5)
- August 2002 (15)
- July 2002 (12)
Tag Archives: python
Aggregator Showdown.
2006.07.17 – 2:24 pm PDT
I started writing this last week, but with a lack of energy, here’s the skinny on what I’ve written up.
Dave Winer reminds us the other day. “2/3/06: “Aggregator developers could sure use some competition!”
I like server side aggregators more than desktop. In a multi-user aggregator ideally it should be customizable by the end-user. One that shows you your feeds how you like to view them, whether it be email style, linear, reverse, upside down, reverse print, etc.
It should also remembers what’s new since the last visit.
I decided I’d see just what the opensource world has to offer in web-based single and multi-user aggregators.
I really wasn’t too impressed from a selection point of view with a multi-user installation in mind.
most opensource aggregators aren’t “pretty” or even still in development.
2004 was last real opensource aggregator development time period.
I even tried to get some of the ones listed in google’s directory to work.
here is some of my results in demo form.
| DATE | NAME | Code | Users? | In Devel? | OPML? | Working? |
| 2004.02.14 | rnews | php | single | no | yes | yes - with manual fix |
| 2004.11.06 | TALAggregator | python | single | no | yes | no |
| 2004.08.08 | planet | python | single | no | no | not latest dev version |
| 2004.12.16 | feedonfeed | php | single | no | import | yes |
Installation notes.
I first tried the Gentoo ebuild version of planet which is quite old but worked. planet has a nightly snapshot of their devel repo, which is missing a python dependancy I can’t figure out.
TALAggregator lacks a logout button, which makes it difficult to create users, and use your own account to browse feeds. Also logging in doesn’t usually work properly. TALAggregator stores it’s password in an encrypted format in the mysql database.
rnews stores the passwords as plaintext in the mysql database and also lacks a logout button/link. It is also having issues when creating it’s tables in the database. Being able to create the user_prefs table, but not the links, and users’ links table. ex. “links”, “px_links”
Once I applied some force and a crowbar, I now have the sql to create the needed table. It’s support with importing of opml files works fine and also adds your categorized material correctly. And of course the interface is a tad bit clunky.
CREATE TABLE `links` ( `id` INT( 16 ) NOT NULL AUTO_INCREMENT PRIMARY KEY , `src_id` VARCHAR( 36 ) NOT NULL , `link` TEXT NOT NULL , `title` TEXT NOT NULL , `description` TEXT NOT NULL , `state` VARCHAR( 16 ) NOT NULL , `pubdate` DATETIME NOT NULL , UNIQUE ( `src_id` , title( 255 ) ) ) ENGINE = MYISAM CREATE TABLE `px_links` ( `id` INT( 16 ) NOT NULL AUTO_INCREMENT PRIMARY KEY , `name` TEXT NOT NULL , `main_link` TEXT NOT NULL , `rss_link` TEXT NOT NULL , `image_url` TEXT NOT NULL , `user_order` INT( 8 ) NOT NULL , `category` TEXT NOT NULL , `last_update` DATETIME NOT NULL ) ENGINE = MYISAM ;




comment support working again.
OK, I believe the comments should be fixed now and OpenID should also be working too. Using my own livejournal account, it works fine. I would appreciate it if you have a chance to please try and leave a comment with your own LJ account or working OpenID setup.
[tags]OpenID, Livejournal, comments, posting, blogs, web, identity, identity2.0, python, service, security, id, hack[/tags]