@kingdomcome@yarn.girlonthemoon.xyz Oh, cool! Can we see the results? :-)
@prologic@twtxt.net Judging by the BRG and BIDV buildings, I conclude this is Hį» HoĆ n Kiįŗæm: https://en.wikipedia.org/wiki/Ho%C3%A0n_Ki%E1%BA%BFm_Lake
@kiwu@twtxt.net Iāve no idea about regulations in your area, but over here there are different taxation rules for video and photo cameras. Hence, manufacturers limit the video recording time of photo cameras typically to half an hour, so that they donāt classify as video cameras with their higher taxes.
@klaxzy@klaxzy.net Worked out perfectly for me, too! :-)
@prologic@twtxt.net Tada! There you once hope for your flight and ride to be delayed and then of course they are right on time! :-D You gotta wait either way. ;-) Looks like you got some good drinks, though.
@movq@www.uninformativ.de Haha, I would feel the same. :-)
@kiwu@twtxt.net It also greatly depends on what kind of videos you plan to record. When you go, letās say, diving, the specs need to be probably more suited to that type of environment. What about zoom, macro shots, wide landscapes, and so on? When typically mounted on a tripod, Iād say builtin image stabilization is not required, but for more action shots, this is fairly important to not get sea sick. :-)
Iāve got a Nikon Coolpix S9300. I typically only take photos, but it also works for the occasional video. Free hand moves are quite difficult, but when mounted to a tripod, this is not too shabby. Thereās absolutely no way around a (makeshift) tridpod when zooming in, though. The audio is definitely not the best, especially wind destroys everything. If I recorded more video, I would certainly want to have an external microphone.
@movq@www.uninformativ.de How sweet! :-) I find it super interesting that theyāre kinda common around your area: https://de.wikipedia.org/wiki/Alexandersittich#Verbreitung We donāt have them here.
The photo doesnāt do justice at all, it was blood red: https://lyse.isobeef.org/abendhimmel-2025-11-27/
@iolfree@tilde.club @movq@www.uninformativ.de So true! Good read, thanks for recommending. :-)
@movq@www.uninformativ.de I just skip all those merchants who only accept PayPal or credit card.
@arne@uplegger.eu Das klingt interessant. Aber wer definiert, welche Projekte darunter fallen? Keine Ahnung wie das sonst so mit dem Ehrenamt ist, aber das müssen ja dann auch gemeinnützige Vereine oder etwas Vergleichbares sein, oder? :-?
Wenn ich in der Petition schon wieder KI les, wird mir gleich anders.
@prologic@twtxt.net Oh shit, thatās not healthy! :-(
@movq@www.uninformativ.de @bender@twtxt.net @prologic@twtxt.net Thatās fine with me. It could be even the 1st January 2026, as simple as the change really is.
But it would be also alright to just stick with July, so that I donāt have to update the tests. :-P
/projects URLs since Sunday:
@movq@www.uninformativ.de Dang it. :-(
@movq@www.uninformativ.de Fail2ban to the rescue? :-?
@movq@www.uninformativ.de In my current project Iām typically far away from this pile of shit. Letās see how the project will be in this regard.
@bender@twtxt.net Unfortunately, this also breaks the browser search.
@movq@www.uninformativ.de Iām raising my hand for tt.
@movq@www.uninformativ.de Thatās what tests are for. To fix them. :-D
All my newly added test cases failed, that movq thankfully provided in https://git.mills.io/yarnsocial/twtxt.dev/pulls/28#issuecomment-20801 for the draft of the twt hash v2 extension. The first error was easy to see in the diff. The hashes were way too long. Youāve already guessed it, I had cut the hash from the twelfth character towards the end instead of taking the first twelve characters: hash[12:] instead of hash[:12].
After fixing this rookie mistake, the tests still all failed. Hmmm. Did I still cut the wrong twelve characters? :-? I even checked the Go reference implementation in the document itself. But it read basically the same as mine. Strange, what the heck is going on here?
Turns out that my vim replacements to transform the Python code into Go code butchered all the URLs. ;-) The order of operations matters. I first replaced the equals with colons for the subtest struct fields and then wanted to transform the RFC 3339 timestamp strings to time.Date(ā¦) calls. So, I replaced the colons in the time with commas and spaces. Hence, my URLs then also all read https, //example.com/twtxt.txt.
But that was it. All test green. \o/
@bender@twtxt.net Thanks. That pulley is just to hang back up the telephone wire (on the ground in 16) for that farm and restaurant in 04 once they finish logging. Hahahahahaaahaaaa, I didnāt see the nails on top of the pole. :-D
Yup, these ice crystals are just lovely. :-)
@prologic@twtxt.net Whoās got a life besides work, huh? Yeah, no, thanks, mate! Scratch that.
@thecanine@twtxt.net Cool! Letās hope they truly keep their word.
@prologic@twtxt.net I couldnāt have phrased it any better than @bender@twtxt.net. :-)
Twice or three times the money as before sounds a bit suspicious to me. Of course, I could be wrong, but I always was under the impression, that your last jobs werenāt all that badly salaried. If the new offer is really paid this highly, it might be a shit job. For me, money isnāt everything, Iād rather opt for a lower income where the job is fun than hating to go to work every day. But if the new job ticks all boxes, go for it. :-)
Also: Consult your pillow, donāt rush it.
I was looking at some ancient code and then thought: Hmm, maybe it would be a good idea to see more details in this error message. Which of the values donāt line up. On the other hand, that feature isnāt probably used anyway, because itās a bit ugly to use (historically evolved). And on top of that, most teams need something slightly different, if they deal with that sort of thing.
I still told my workmates about it, so they could also have a look at it and we can decide tomorrow what to do about it. Speaking of the devil, no kidding, not even half an hour later, a puzzled tester contacted me. She received exactly that rather useless error message. Looks like I had an afflatus. ;-)
Itās interesting, though, that in all those years, nobody stumbled across this before. At least we now know for sure that this is not dead code. :-)
I had no meetings this arvo, so I made an appointment with the woods in my extended lunch break. The 6°C warm sun was out all day long and there was only a very light breeze. So, a very nice autumn day.
When I stopped to take a photo in the forest, a deer behind me took off into the woodland. I didnāt see it before. Also, I came across one or the other clearing. Sadly, itās all commercial timberland here. Luckily, in a year or so, when nature slowly took over and reclaimed some spots, the apocalyptic sites are then looking a bit more decent again.
Cleaning of the ruin walls on my backyard mountain slowly takes shape. They made some progress and moved on to the other section. The flag on top is halfway disintegrated again, all the yellow half is completely gone. Iām wondering if they just stop replacing it at some point in time. But probably not.
@bender@twtxt.net Glad you like them! :-) Those colorful roof shingles are absolutely stunning. The golden building has quite a few folds in the facade skin, from the other sides a bit more. Check out this: https://upload.wikimedia.org/wikipedia/commons/0/07/Rems_in_Schw%C3%A4bisch_Gm%C3%BCnd.jpg Luckily, there werenāt this many people around today. :-)
Donāt think this is the norm, though, most stuff here is also much more modern. There are not a whole lot of historic buildings left. And if there are, theyāre not necessarily kept in good shape. But some are. So, donāt be fooled by my biased preselection of typically photographing the nicer ones.
The people photos are not for the internet. ;-) But I get your point, the reason why I ended up in that town is irrelevant and misleading, I should have introduced it differently. :-D
@bender@twtxt.net I knew it was supposed to be a lowercase ātā, but it reminded me of a tiny umbrella.
We had a nice family day in Schwäbisch Gmünd: https://lyse.isobeef.org/schwaebisch-gmuend-2025-11-16/
The gold saga on @quark@ferengi.oneās thoughts continues with https://netbros.com/1750974122. Thatās without any doubt the most beautiful 404 page Iāve ever come across in my entire life. What an overall master piece of art. Well done, mate! <3
https://netbros.com/some-rubbish-just-to-see-the-new-birds-on-the-404-page
@prologic@twtxt.net @bender@twtxt.net I also prefer the old one with the ball of string. :-)
@movq@www.uninformativ.de I think I now remember having similar problems back then. Iām pretty sure I typically consulted the Qt C++ documentation and only very rarely looked at the Python one. It was easy enough to translate the C++ code to Python.
Yeah, the GIL can be problematic at times. Iām glad it wasnāt an issue for my application.
Truly amazing and I agree with @quark@ferengi.one, more people need to know about Thomas Damboās wooden trolls: https://netbros.com/1750512577/ So beautiful! :-)
@quark@ferengi.one Yes, keep em coming. :-)
@prologic@twtxt.net Just start off the experiment now and see how far you get. :-D
Thatās a very entertaining talk about mining and analyzing radio station playlists: https://media.ccc.de/v/38c3-radiomining-playlist-scraping-und-analyse Itās in German, not sure how good the English translation or subtitles are.
Man, @quark@ferengi.one has an absolute gold mine. Having dealt again with different clocks and all sorts of strange time things at work today, this made my day! https://netbros.com/1755172401/ :ā-D
@bender@twtxt.net Hahahahahaahaaa, youāre right, it canāt be anything else! :ā-D Must have been one of these manmade objects. Letās hope they will become a full member of the Grant Wishes Council soon. In any case, I will keep trying.
@bender@twtxt.net I wished my mate would see it, too. But he turned his head a second too late. :-(
On todayās night walk I came across an absolutely giant shooting star. With it being visible for three seconds, itās my second largest Iāve ever seen so far.
The sky picked up a few colors for just a few minutes: https://lyse.isobeef.org/abendhimmel-2025-11-13/
@movq@www.uninformativ.de Yup, itās been some days here, too.
# url = fields, so maybe thatās it?
@movq@www.uninformativ.de Haha, you were spot on! It took me a bit to figure this out on my own. Iām actually very surprised to have gotten this wrong. Oh well.
No, I was using an empty hash URL when the feed didnāt specify a url metadata. Now Iām correctly falling back to the feed URL.
Hmmm, looks like my twt hash algorithm implementation calculates incorrect values. Might be the tilde in the URL that throws something off. :-? At least yarnd and jenny agree on a different hash.
@bender@twtxt.net Hmm, didnāt find anything. But you mean a giant bucketload of access_log /home/$USER/logs/access.log if=⦠where the condition matches the requested path for said user? Yeah, that gets annoying very quickly. :-D
@movq@www.uninformativ.de Uuuhhh, beautiful! <3
Nothing too crazy, but still nice: 
@bender@twtxt.net Sounds about right.
I had a brainfart yesterday, though. For whatever reason I thought of subdomains, which are modeled with server entries in nginx. So, each could define its own access_log location. However, there are no subdomains in place! Searching around, I didnāt find any solution to give each user their own access log file.
One way would be a cronjob, aeh, systemd timer as I learned the other day, that greps the main access log and writes all user access log files with only the relevant stuff.