↳
In-reply-to
»
Hmmm, after fixing my feeds to move the
⤋ Read More
<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.
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!?
↳
In-reply-to
»
Great, last system update broke something, building from current master I get:
⤋ Read More
@lyse@lyse.isobeef.org interesting… ill look into the parsing on that one
↳
In-reply-to
»
Great, last system update broke something, building from current master I get:
⤋ Read More
@lyse@lyse.isobeef.org interesting… ill look into the parsing on that one
↳
In-reply-to
»
Great, last system update broke something, building from current master I get:
⤋ Read More
@lyse@lyse.isobeef.org WTH.. i cant reply to this?
↳
In-reply-to
»
@prologic Alright, there's some erroneous markdown parsing going on, I reckon. In my original twt I have a code block surrounded by three backticks. The code block itself contains a single backtick. However, at least for rendering, yarnd shows three backticks instead (not sure if my markdown is invalid, though):
⤋ Read More
@lyse@lyse.isobeef.org ill check this out.. also.. why the heck is my reply trying to set the subject to #bd3yzvq)