Newsbeuter mentioned on podcast

September 25, 2007

Newsbeuter […] is the apparent replacement for the no longer actively developed raggle and snownews.

(Source: podcast #43)

And rightly so! 😉


Newsbeuter 0.7 released

September 18, 2007

Newsbeuter 0.7 has been released, and can be download from the usual place. The following changes have been implemented:

  • Filters can now be predefined
  • synchronization support has been added
  • OPML online subscription support has been added
  • Bookmark support (plugin-based) has been added
  • Custom flagging of article has been added
  • The search function has been remodeled
  • The possibility to optionally use external HTML renderers (such as lynx, links or w3m) has been added

If you want to know more about the new feature, the best reference is the newsbeuter online documentation. And if you know any new feature that you want to see in the next release, don’t hesitate to file a bug.

Article about newsbeuter on “Debian Package of the Day”

September 16, 2007

The blog “Debian Package of the Day” published a short introduction to newsbeuter that outlines the most important features, written by Truly Yours. It talks about how to start with newsbeuter, what the most important features are (OPML import/export, Snownews extensions, podcast support, the filter language, query feeds, notifications, …) and demonstrates the UI design, HTML rendering, configurability of colors and I18N/L10N through screenshots.

Support for external HTML renderers

September 14, 2007

Today I implemented support for integrating external HTML renderers. Newsbeuter’s internal HTML renderer is not perfect (e.g. it doesn’t support rendering of tables), and so I decided to provide the possibility to choose either between the internal renderer or an external one. That makes it possible to let the HTML content of articles get rendered by text browsers such as lynx, (e)links or w3m. The only disadvantage is that using an external renderer makes displaying a bit slower (since the invocation of external programs takes more time), and that it’s not possible to retrieve all links contained in an article, i.e. the ‘u’ key won’t work anymore in the article view.

A new RSS feed reader in the hood

September 11, 2007

There’s a new RSS feed reader for the text console out there, called NRSS. I took some time and had a look at it.

What is displeasing in the beginning is the lack of support for OPML file import. OK, then let’s fill ~/.nrss/config with a few URLs:

add “” “Fefe’s Blog”
add “” “Unicode-Test”
add “” “Dive Into Mark (Atom)”
add “” “Venzis Blog”

So I start NRSS, and what happens? NRSS immediately begins to reload all feeds, and crashes at the URL Oh, well. That Atom feed doesn’t seem to work, although the FAQ claims that Atom is supported. So I remove it from the configuration. (N.B. the guy is an absolute Atom nerd, and his feed is considered a kind of “benchmark” for Atom compatibility by many people)

The interface looks rather unusual, namely it starts with a feed’s name, below it its articles, then another feed, with its articles below, and so on. IMHO not very concise, especially for a lot of feeds (I read about 100 feeds right now, and I know newsbeuter users with 300 and more subscriptions). The articles can be collapsed, with the “C” key. BTW, help can’t be found via the ‘h’ or ‘?’ key, but via the rather un-intuitive ‘u’ key (as in “toggle-usage”).

Navigation is done via the cursor keys respectively page-up/down. Latter keys jump to the previous resp. next feed. With the space key, the selected article can be displayed. And here the next problem: HTML doesn’t get rendered. The documentation explains that a filter must be configured (it comes with an example to use w3m as such a filter). From the article view, it’s also possible to navigate to the next and previous article.

With Unicode characters, NRSS also seems to have problems (although I only tested with Japanese characters). The characters are displayed properly (well, not exactly in the Debian build, the colors are messed up there), but when switching from the article view to the article list, NRSS has redrawing issues. Ctrl-L, the “classic” keystroke to do a complete redraw in text-based applications, doesn’t work. Instead, the user has to press ‘D’.

After some more experiments, I had enough of NRSS, so I had a look through the documentation. The only special feature that caught my eye is the possibility to customize NRSS’ style with custom format strings. That’s a feature that’s not yet available in newsbeuter. Otherwise, NRSS has no interesting features, even Snownews and raggle provide a more complete set of features.

What especially amused me is the first entry in the FAQ, titled “What makes NRSS better than snownews/Raggle/newsbeuter/[other reader]?” that directly attacks these mentioned RSS readers.

There it says “With NRSS, the feeds are laid out in a predefined order, each with a summary of headlines, and I can read any story I like or go to its link without any clicking or tabbing. One of the philosophies of NRSS is that it should pack the most information into a single screen without seeming crowded.” Oh, well, this is possible in newsbeuter, too. In multiple ways. You can for example define a query feed that then displays articles of different feeds in a single list. From there, it’s a single keypress to view the article, and another one to return to the list. Exactly the same number of keystrokes that you need with NRSS. And you can navigate to the next article directly from the article view, too, in newsbeuter. And you can directly jump to a certain line in any article list or feed list, something that’s currently not possible with NRSS. In fact, there are so many more cool things in newsbeuter that simply can’t be done with NRSS.

And that brings me to my next point: scalability. Scalability in terms of extensibility. NRSS supports pipe-based plugins in many systems. This is pretty cool, in newsbeuter, support for Snownews extensions (and bookmarking support in the upcoming version 0.7) is implemented this way. But in some places, this isn’t really cool, like when it comes to display filters. Everyone who has used mutt probably knows display filters, and NRSS follows a similar concept. And everyone who knows display filters from mutt most likely has made the experience that this doesn’t perform really good, since a new process has to be spawned for every displayed article. An internal HTML renderer would fit well into NRSS. And it isn’t even too difficult to implement, as my own simple HTML renderer in newsbeuter shows.

But back to scalability: NRSS is written in pure C. The code quality is quite OK, what I could see from a quick look at it. But due to the IMHO poor choice of language, my prediction is that NRSS won’t scale in the mid- to long term. Adding new features will be harder and slower than in newsbeuter (unless the author spends more development time per day), and doing fundamental refactoring (and that is going to be necessary, I predict, if the author doesn’t want NRSS to end like mutt or slrn, which are both basically in maintaince modes these days) will be more painful. Snownews is a good example for an RSS feed reader, written in pure C, which lacks a lot of important features even after quite a long development time, and whose development practically came to a halt.

That said, I wish the author of NRSS all the best with further development, but I see no point in developing yet another RSS feed reader when there’s already a pretty good one out there.

(This article has been published in a shorter version [and in German] in my personal blog before)

Search interface remodeled

September 2, 2007

I implemented a search interface to newsbeuter very early, because there was quite a lot of demand for it. But I was never really happy with it, because it was awkward to use in some way, and it duplicated functionality that was already in the implementation of the article list. Well, not anymore. Today I sat down, and replaced the search interface with the article list (plus some extensions so that the article list could be used to display search results). Not only makes this all the functionality that is available in the article list also available to users of the search interface, but it also unified the user interface, since the input field for the search phrase was moved from an own line to the line at the very bottom, like all other input fields. As an extra, I added a search history, which should make refining searches easier than before. And not to forget, it also displays what feed an article belongs to, something that was already available for query feeds, and that became instantly available with the switch to the article list.

In my opinion, this is another great example how good the overall code quality is: I can do such changes within a few hours, without any bigger hassles. Adding new features to newsbeuter has become such a charm lately, it’s a real joy doing that. I think the feature list of the upcoming release shows that.

New translations

September 1, 2007

Thanks to Adiel Mittmann and Bart Van Loon, the next release of newsbeuter will feature two new translations: Brazilian Portuguese and Dutch. This means that newsbeuter 0.7 will be available in 7 languages (English [default], German, Italian, French, Russian, Brazilian Portuguese, Dutch), and I think that this is not only valuable to the users of newsbeuter, but it also shows how many users are motivated and willing to contribute to newsbeuter. More translations are always appreciated, of course. To start a new translation, just download and fill out the empty “msgstr” parts with the correct translations. When you’re finished, just send the file to me, and I will integrate it into the SVN repository, and it will appear in the next release.