OK, I really like this too, for a bunch of reasons.
But for it to work with Twitter properly, though, there'd have to be at least a few configurable options, which could make the feature rather complicated to use. The big problem is that in general, an RSS sidebar module should display both the title and the description, and possibly the post time, along with a link to the full story.
While Twitter does make RSS feeds available, so that people can follow individual Twitter accounts in an RSS reader, they'd look really wacky if you did them that way - there's an example of a Twitter RSS feed here. The title and the description are the same (format username: Tweet), and the link goes to the status update page, which just shows the same Tweet again. Drawing a Tweet the same way you'd want to draw a normal RSS feed would make for a really ugly Twitter update.
I think you'd probably also want for any RSS module to have options for the maximum description length to display, and for the number of entries to show, and I'm not sure how that would fit into the UI, although I suspect someone could come up with something clever.
That being said, it might be easier (and easier to maintain) to subclass an RSS module for a Twitter module, rather than developing one using Net::Twitter. All you'd have to do is change the display code to only show the description code, a set number of them, and link at the top to the user's main Twitter page to make a subclass work.
no subject
But for it to work with Twitter properly, though, there'd have to be at least a few configurable options, which could make the feature rather complicated to use. The big problem is that in general, an RSS sidebar module should display both the title and the description, and possibly the post time, along with a link to the full story.
While Twitter does make RSS feeds available, so that people can follow individual Twitter accounts in an RSS reader, they'd look really wacky if you did them that way - there's an example of a Twitter RSS feed here. The title and the description are the same (format username: Tweet), and the link goes to the status update page, which just shows the same Tweet again. Drawing a Tweet the same way you'd want to draw a normal RSS feed would make for a really ugly Twitter update.
I think you'd probably also want for any RSS module to have options for the maximum description length to display, and for the number of entries to show, and I'm not sure how that would fit into the UI, although I suspect someone could come up with something clever.
That being said, it might be easier (and easier to maintain) to subclass an RSS module for a Twitter module, rather than developing one using Net::Twitter. All you'd have to do is change the display code to only show the description code, a set number of them, and link at the top to the user's main Twitter page to make a subclass work.