Conversation showing properlyNow that I updated my feed with this twt, all yarnd caches should hopefully receive a new twt with the correct hash, once they refetch my feed.
Did you have a power or network outage?
Xuu replied correctly, without noticing
2021-06-12T08.03.22Z is an illegal timestamp format. The periods must be colons.
Not matching markdown in tt and yarnd
Conversation tree in ttWhat do other clients see here? Which hash does that linked twt produce on your implementations?
A few years ago, we clocked mountainbiking vs. hiking. By bicycle (real ones, no fancy electric motors) we weren't any faster than by foot. Just on the way home, of course, the bike won by a large margin. The fastest ride home took only 12 min. But that was totally insane. Just plain stupid. If anybody had come our way, it would have ended really, really badly. So we only did that once.
Depending on the picked route, 1:30 or even 2:00 hours one-way to the top is easily possible at our walking pace. So your guess of a bunch of hours is not that wrong. Just depends on our mood and path choices. :-)
Mt. Hohenstaufen over the roofs
Welcome to Lyse's evening of pessimistic views.
As for twtxt in particular, I see growth more as a bad thing, I don't want to deal with all these idiots out there, not even indirectly. If the network grows, other folks, best not to tangle with, are naturally attracted, too. It's a normal thing, there's no way around it. I'd like to rather keep my filter bubble small and familiar. I know, a lot of, if not most, people here disagree with me.
Also, I even don't know whom of my friends I would want to create their own twtxt feed, since I'm in touch with them in other ways, anyways. The ones I told about twtxt in the past were very hesitant to join. So was I in the beginning. For very good reasons. Writing shit publicly on the internet is not everybody's cup of tea. And by now people have already established ways of publishing truly interesting things. So, there's simply no need for alternatives to them. My best mates have low opinions on social media, so do I. I try to convince my brain not to consider twtxt as social media. :-) I'm just here because I initially was intrigued by the simplicity of twtxt and I like the people I follow.
Lastly, there are days I hardly can keep up with the amount of new messages, so a larger community would make that job even harder.
Quite a pessimistic and selfish view, some might say. And they were probably not too far off. It's very hard to explain. And then even not in mother tongue.
Don't get fooled with jenny and mutt. ;-D Twtxt is way much more like a website. Well, in fact, it basically is.
And I try not to talk people into twtxt. It's just something I try to avoid in general.
Deerstand in the the yellow forestYesterday, I forgot my SD card at home, so the camera was totally useless. We had a very crazy, fiery glowing, blood-red sunset from what I could see through and above the trees. But I was about 15 minutes too late. Only saw the last red stripes over the horizon when I finally made it to the lookout outside of the forest. Todays sunset was quite boring.
<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?
<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.
/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!?
/usr/bin/ld: /lib/x86_64-linux-gnu/libm.so.6: unknown type [0x13] section
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!?
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.
Alright, multipass is basically for administrating multiple systems at once. Good thing, I'm not an admin. :-) But now I remember a good mate doing this, too. If I'm not mistaken, he used tmux's builtin functionality to update all his, I don't know how many, machines at the same time. Pretty cool actually. This also reminds me that I really should finally take a deeper look at tmux some day. Never did that before. I just open a new terminal and my tiling window manager takes care of most things, well the layout. Except that I would have to explicitly ssh into the other system if I were working some remotely.
Yes, I'm on i3 and really not in a mood to fiddle around and waste my time with broken or unfinished stuff if I can easily avoid it. I just want my system to work. :-)
What's your use case to send keyboard events to an asortment of windows? I never did that and can't see when that would be useful. But I'm sure there are lots of applications out there for that.
If I want a fucked up clipboard, I can also simply use a VM… Oh dear, this is a total killer. So Wayland is absolutely worthless to me.
I never tried Wayland myself. Nor did I do any research on that matter. From all you said and I heard from other mates, let me answer your question why you want to switch: You don't. :-) This model really sounds totally insane. It feels like it's heavily contradicting KISS at all possible levels. Complicating everthing at basically no gain. Security is all good and nice, but if you can't do basic things anymore, then that's the opposite of progress or even a working system. I fear it's going to be the same with systemd and System V Init. Eventually everybody is forced to switch over. But not now. Hopefully, by then some things are sorted out and even simplified. Hope dies last, but it dies.
Very nice quote, I completely agree! :-D
<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.
<link> would be treated as <id> if there's no explicit <id>. But I guess, it's too late now.Interesting, tag URIs are a first for me, too.
Fog patch and sunset at the dairy farm
@nick@hostname yarnd syntax was a mistake. Long live proper @<nick url> twtxt syntax, only.
xml:base attribute, just like @mckinley said. Never heard of <link rel="self" … /> being used for that. Maybe some last resort fallback in some feed readers, though. But that would be very fragile, too.Unfortunately, the reasoning behind
rel="self" remains a mystery.
Unfortunately, the autodiscovery document in one of your linked resources does not exist anymore. What annoys me in Atom is the distinction between
<id> and <link>. I always want my URL also to be my ID, so I have to duplicate that – unnecessarily in my opinion.Also, never found a good explanation why I should add
<link rel="self" … /> to my feeds. I just do, but I don't understand why. The W3C Feed Validation Service says:> […] This value is important in a number of subscription scenarios where often times the feed aggregator only has access to the content of the feed and not the location from which the feed was fetched.
This just sounds like a very questionable bandaid to bad software architecture. Why would the feed parser need access to the feed URL at this stage? And if so, why not just pass down the input source? Just doesn't make sense to me.
Also, I just noticed that I reference the
http://purl.org/rss/1.0/modules/syndication/ namespace, but don't use it in most of my feeds. Gotta fix that. Must have copied that from my yfav feed without paying attention what I'm doing.Your article made me reread the Atom spec and I found out, that I can omit the
<author> in the <entry> when I specify a global <author> at <feed> level. Awesome! Will do that as well and thus reduce the feed size.
Sunset
In all our meeting invitations the audience is allowed to see who's also invited, so a simple invitation is enough.
And then watching the incredible sunrise from the top of my backyard mountain. Today was one of the best sunrises I've ever experienced. Easily in the top ten, photos don't do justice at all. Not even close. It was nicely red 360° around me, which is quite rare in my opinion.
SunriseAnother early hiker showed me that we could even see the Zugspitze in the alps, Germany's highest mountain at 2962 meters above sea level. It's the light lavenderish thing in the distance, that look a bit like clouds:
Zugspitze in the alps 175 km awayConditions have to superb in order to be able to see that far, 175 km. I've actually never witnessed that before. My dad just told me that he'd seen it once in his life, my mum never, happens very few times a year.
Up top it was very windy and cold, I was glad to bring a spare t-shirt, scarf and beanie. My camera battery died a few times on me today, also during video recordings. I muted the rushing noise of the wind and set to bird's twittering from last year.
The same goes with random code names, they're even sillier than abbreviations in my opinion. At work even teams give them super random names, so you've not having even the slightest chance of guessing what they do or whom to contact if a problem arises. Luckily, my direct work mates also hate this shit and we just call us after our component. Sometimes I think unrelated team names are just in place to avoid having to support their broken rubbish. If nobody finds you, you're not bothered.
If there's a glossary, it's not too, too bad. You'll learn the abbreviations eventually. But it's just normal and like everywhere. Every trade has its technical terms and that also includes abbreviations. They need to be chosen carefully, though.
Shadows of my mate and myself when enjoying the view to Mt. Rechberg