"Husain Alshehhi" <hus...@alshehhi.io> writes: > - inability to browse servers or individually configure settings on a > per-feed basis > > Do you mind elaborate into how nnnrss solves this?
nnnrss is based on nnfeed, which is the same backend used by nnatom. Like nnatom, each feed is treated like its own server, appearing in the server buffer with individual groups inside it (nnfeed supports multiple feeds in a single server, but RSS and Atom documents only ever contain one feed). Agent enrollment is therefore on a per-feed basis, and killing a group originating from a feed doesn't cause it to vanish into a netherrealm. It's also possible to rename feed groups once they've been created, which is another limitation of nnrss. > - and has at various times decided to chuck out my feed urls. > > Can you please elaborate on this? Because nnrss doesn't treat each feed as its own server, it needs some way to map groups to the underlying feeds they represent. It does this using internal data structures (this is probably why you can't rename an nnrss group: it would break the link between the group and its feed). In some cases, these datastructures can become corrupted and the corrupt versions can be saved to the disk. Should this occur, nnrss will no longer have any idea where to find your feeds, and there's no way I've found to fix this other than editing the files manually. I can't elaborate further on when or why nnrss does this, because I don't know. It could be a misconfiguration issue with my emacs setup. > I have used nnrss before, and my issue with it is that it (1) > syncriounus, causing emacs to freeze for a while, (2) does not support > atom, and I have not used emacs 30, and (3) cannot be configured to use > curl, and that was necessary in my case since some website required > auth. I moved on to use elfeed. nnnrss is still synchronous like the rest of gnus, and does cause emacs to freeze. I'd really like it and nnatom to be asynchronous, but I think that would require appreciably more work. I've enrolled all my feeds in the agent and configured the demon to fetch only if emacs has been idle for some time. However, both nnrss and nnnrss can be configured to use curl by setting `mm-url-use-external` and `mm-url-program` accordingly, so that works at least
