

This configuration command sets the source where URLs shall be Urls-source (parameters: default value: "local")

Using Newsboat (a TUI RSS reader) as standard, I'd say the following backends are applicable: Your client then needs to sync two-way with such a backend. You can self-host a backend such as Nextcloud News, TT-RSS, FreshRSS. I've partly figured out the answer to my question. Because of that I regularly find out I've skipped chapters. one of the defunct serials I used to follow would publish a page per day), and so pocket is a mess of interspersed normal articles to read later and chapters from dozens of serials.
#Mac rss reader vienna serial
The issue is mostly that serial entries can accumulate rather fast in pocket (especially for those with small frequent entries e.g. "RSS to pocket" isn't really the issue, going through my RSS feed, reading the regular entries and sending the serials to pocket isn't much of a drain / difficulty. > You can automate the RSS-to-Pocket (or other read-it-later service) part with tools such as If This Then That. I really need to knuckle down and play with epub, seeing how googling around doesn't seem to yield anything useful. That is sort of the things I've considered, however each serial's feed really is a single work being updated (mostly append-only I guess, I don't know how many serials authors go back and significantly rework previous entries) and I don't know how well epubs and their clients deal with updates / additions (without intermediate proprietary storefronts). > Personally, I "solved" a similar issue of mine (collecting posts I want to read in a weekly EPUB and send them on my Kindle) with Pocket and a web service called Crofflr. So I guess you want to collate the posts rather than the feed entries themselves. They may syndicate limited content, may contain ads, etc. I think RSS are the wrong starting point for such a task.
