# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 6
# self = https://watcher.sour.is/conv/ttqxgfa
lyse
lyse.isobeef.org
View Thread
Hmmm, after fixing my feeds to move the <author> from <entry>s to <feed>, Newsboat marked all old affected articles as unread. IDs were untouched, of course. Need to investigate that. Had something similar happen with another feed change I did some time ago. Can't remember what that was, though.
lyse
lyse.isobeef.org
View Thread
And I just found out that my enqueue script also broke. All authors are "None" in ybeuter. Turns out, the author column in the rss_item table of the _cache.db_ is now empty and also Newsboat does not render an "Author" header in the article view anymore. The feed's author is ignored.

Looking at the code, I noticed the <contributor> is not supported at all. Gotta file a bug report or even better directly submit a fix MR (to some of the issues) tomorrow. Gotta test my C++ "skills". Duck and cover everybody!

In my enqueue script I now just fall back to the "Feed" field, so at least that's working again.
lyse
lyse.isobeef.org
View Thread
Great, last system update broke something, building from current master I get:


/usr/bin/ld: /lib/x86_64-linux-gnu/libm.so.6: unknown type [0x13] section
.relr.dyn'


What the heck!?

And it also appears that I'm not really able to reproduce this unread bug. It only kind of works a single time. And it has something to do with my config. Not sure what it is yet. I also noticed that the
timestamps in the entries somehow shifted between the old and new feed. Da fuq!?
lyse
lyse.isobeef.org
View Thread
Great, last system update broke something, building from current master I get:


/usr/bin/ld: /lib/x86_64-linux-gnu/libm.so.6: unknown type [0x13] section `.relr.dyn'


What the heck!?

And it also appears that I'm not really able to reproduce this unread bug. It only kind of works a single time. And it has something to do with my config. Not sure what it is yet. I also noticed that the <updated> timestamps in the entries somehow shifted between the old and new feed. Da fuq!?
lyse
lyse.isobeef.org
View Thread
Hmm, I figured out, that in the old rewritten feed the original <published> timestamp was used as <updated> in an <entry>. And now it's the original feed's <updated> timestamp. I never used <published> elements in <entry>s. I have absolutely no clue why now the updated instead of the published timestamps are used. I definitely should just use both fields properly and not just one. In the Newsboat source code <published> take precedence over <updated>.

But I guess this explains the weird behavior I've seen in Newsboat, that suddenly, read entries were marked unread. They were older than a year and I've set keep-articles-days 356, so they were removed from the cache. With updated timestamps Newsboat just recreated new articles in its cache, which of course are unread.
lyse
lyse.isobeef.org
View Thread
Alright, my Python script, that rewrote the feed, just preferred the <updated> over <published>. Easy as that. As a bonus it did that forever. No idea, why the generated feeds suddenly caused all the trouble. Basically all feeds were affected. Luckily, no Newsboat bug.

I just filed a question for Newsboat about the unsupported <author> on <feed> level: https://github.com/newsboat/newsboat/issues/2256 Is it a feature or a bug?