(#payoedq) Yeah, @movq@www.uninformativ.de, I’m thinking the same. What do you mean, @prologic@twtxt.net? Names are in the shiny new image descriptions (I just extended my script for that). Both German and English.

@prologic@twtxt.net (#ybzvcta) Sounds good to me.

@fastidious@twtxt.net @prologic@twtxt.net (#dl7auta) Nice indeed!

@movq@www.uninformativ.de (#f7ydt7a) Ta, I’m glad the fabulous adept approves of my botching. :-D

@prologic@twtxt.net @thecanine@twtxt.net (#6gszxta) The only problem with time-based approaches is that if a feed is down for some reason (or just not fetched in time) you might miss older twts you haven’t seen. Depending on the use case that might even be a feature to ignore outdated content. In my client I just mark every twt read and the next time I start it, all fully read conversations will be hidden.

@prologic@twtxt.net (#cdl6foa) Yeah. :-)

@prologic@twtxt.net (#vels76a) This sheet lightning looks really nice.

Birds were quite active in front of my window this morning, unfortunately, the sun wasn’t really out yet. https://lyse.isobeef.org/voegel-2021-10-23/

@prologic@twtxt.net (#cdl6foa) I agree on a release process. However, I’m not so sure on the code signing part. M$ lately signed rootkits again. So it’s more a false sense of security. Could be a different story for your own code, though, as there’s no other party involved. Need to think about that a bit more.

@prologic@twtxt.net (#6gszxta) :-D Don’t get me wrong, the idea isn’t bad at all, maybe just needs slight tweaking. Like maybe showing the new unread twts in that conversation if you’re logged in. But I think there’s no concept of read/unread twts in yarnd, so well, probably won’t work, but could be useful I reckon. It’s just an appearance issue.

@prologic@twtxt.net (#gyxy4ta) So that’s not too bad. But skimming over Cache.FetchTwts(…) reveals that the cache isn’t touched when the parsing of the feed fails. Assuming that an invalid feed produces an error (might be wrong, didn’t investiage any further), the cache is not populated, triggering a fetch each time somebody visits the profile.

@prologic@twtxt.net (#ybzvcta) I reckon the metadata should certainly be honored. Only if that is unsuccessful fall back to the trial and error search. Maybe also limit the attempts to find an avatar to a smaller subset of filenames. Do you have any numbers on (un)successful filename discoveries?

@prologic@twtxt.net (#gyxy4ta) Do you have any numbers on how often that happens? Maybe viewing a profile should not immediately fetch the feed but only if the feed hadn’t been fetched in say the last five minutes or so. Otherwise it just displays its empty cache. Or will this empty result set trigger the fetch?

@fastidious@twtxt.net (#6gszxta) It was dramatic, indeed. I completely felt like @darch@twtxt.net, the red circles were too encroaching in my opinion, just like ads. Warning, click me! Fix me! You need to act now! Don’t miss out! And all it was was an informational number. Especially since twtxt.net puts great stress on a calm and unagitated user experience with no push notifications and things like that, it just looked exactly like the opposite. Your blue version over on arrakis.netbros.com is a completely different deal, it fits much better but still raises too much importance on the number for my taste.

@prologic@twtxt.net (#cdl6foa) Auto updates are one the worst things in the world in my opinion. They always update at the wrong point in time which is not only very inconvenient but also often breaks stuff and then you’re fucked for at least a moment. It adds useless complexity to the software. The most terrible thing, however, is undermining security in my opinion. Don’t do it.

@off_grid_living@twtxt.net (#3or3axa) Uuuuuuuh, very nice bedtime sweet, thanks mate! So you’re turning it with a pipe wrench then? Happy fitting!

@darch@twtxt.net (#6gszxta) Didn’t know what you’re talking about until I visited twtxt.net. Agreed, this looks really wrong!

We had a colorful sunset just now: https://lyse.isobeef.org/abendhimmel-2021-10-22/ (Whoops, fixed the wrong URL…)

@movq@www.uninformativ.de (#lecztrq) Nice, off with that shit!

@movq@www.uninformativ.de (#f7ydt7a) Thanks! Yeah, not sure why I can’t hold my camera straight. :-( I rotated it 2° to the left, now the sign post is pretty much vertical and the horizon horizontal. In case you’re interested in the original versions: 1[15]{,-gedreht}-original.jpg

@prologic@twtxt.net (#gyxy4ta) So does yarnd try to fetch this “feed” now periodically or just at the very first time or when somebody tries to view the profile?

@prologic@twtxt.net @quark@ferengi.one (#gyxy4ta) So tt just renders this mention as an unfollowed feed as I expect. I can then open the URLs view manually and follow the “feed”. But that would be a manual step, tt doesn’t fetch anything automatically. I don’t think you can’t really do something about it. Maybe the URL was valid at the time or will become valid in the future. Valid as in a valid twtxt feed.

@kt84@twtxt.net (#5hxqdgq) This looks nice!

@prologic@twtxt.net (#f7ydt7a) Ta! :-)

@quark@ferengi.one (#boco3fq) I quite like autumn storms, but when the wind rattles the shutters it’s getting quite loud.

@movq@www.uninformativ.de (#gxh3f7a) That’s what’s tt is doing, too. Was one of the first things I implemented to save space: https://git.isobeef.org/lyse/tt/#show_subjects

@prologic@twtxt.net (#h62bcha) Hmm, what do you mean by “rebuilding by hand”? I think it’s best to just write everthing directly in HTML. No processing required. I don’t think there will be frequent updates.

Quickly went up the local mountain in an hour to see the sunset. Without a camera I would have been 5-10min faster. https://lyse.isobeef.org/waldspaziergang-2021-10-21/

@prologic@twtxt.net (#yywfv5a) Yummy!

@prologic@twtxt.net @eldersnake@yarn.andrewjvpowell.com (#p6vbmtq) That does not only apply to Australia.

Far from spectacular, but still a nice cloudy sunset today on my way to the dairy farm: https://lyse.isobeef.org/abendhimmel-2021-10-20/ The bridge is coming together slowly.

@quark@ferengi.one (#ck2oria) Well put! ;-)

@movq@www.uninformativ.de (#3xfftqq) \o/

@movq@www.uninformativ.de (#ck2oria) Ah, I see. Yes, the fallback would still be needed and thus, doesn’t really change the world. In fact there are now two ways to produce message IDs and if one client doesn’t adpopt to the new message ID field, conversations are forking themselves automatically in a rather ugly way.

@prologic@twtxt.net (#5cjjnba) I see a badger.

@quark@ferengi.one (#ck2oria) It is then a very different format, though. Not twtxt anymore. All the extensions we’re having now are still backwards-compatible to the original spec. Granted, they don’t really work without client support, but technically it’s still compatible. At the moment I’m not sold on redoing everything. But a version 2 would allow to fix a couple of things. E.g. feed relocation and stuff like that.

@movq@www.uninformativ.de @prologic@twtxt.net (#3xfftqq) There you go!

@movq@www.uninformativ.de (#ck2oria) Yes, this is the only reliable way. Everything else is just a quirk. One could put place the message ID in the third field and the reply ID in the fourth to help the purists without clients.

@movq@www.uninformativ.de (#lecztrq) Fits well in your motto of owning less. :-) Now the important bit: get well!

@off_grid_living@twtxt.net (#2q6b5jq) Wow, M20 is substantial, looking forward for detail pictures! :-)

@movq@www.uninformativ.de @quark@ferengi.one (#3xfftqq) So you want me to send a merge request? :->

@stigatle@twtxt.net (#efbtw6q) Newsboat gets ported from C++ to Rust, you might tackle some things over there. ;-)

@movq@www.uninformativ.de (#3xfftqq) I just added a test case with “our” expected hash and it passes: https://git.mills.io/lyse/yarn/commit/314fc1f29f6500b6b0686a5895e3148ac8b06d05 The thing is, https://f.adi.onl/conv/egdmpoa still shows the other twt hash movq was talking about, @quark@ferengi.one. It doesn’t feel right.

@movq@www.uninformativ.de (#3xfftqq) I get #tkdjrmq, too. Let’s see.

@quark@ferengi.one (#mehlzga) Oh dear, I hear you! Everything above 25°C is absolutely awful. We’re having high humidity in summer as well.

@adi@f.adi.onl (#4cpz2da) Haha, I first read screw sizes. :-D

@prologic@twtxt.net (#mkomilq) Yes, the goats were really cool and quite curious.

@jlj@twt.nfld.uk (#zo6r7rq) So what’s an eight? I reckon that means pretty good. :-?

@stigatle@twtxt.net (#txxq7pq) Lovely! When I had to go to the old work office I often saw some nice sunrises in autum, winter and spring, too.

@stigatle@twtxt.net (#qv6en5q) Hell yeah, this is beautiful, mate!