Thanks to @kat@yarn.girlonthemoon.xyz and her shelf I finally spent several hours in the woodshop. I wanted to build two drawers for the workbench and thought that I will complete this project in no time. I’ve been so wrong again. ;-)
I didn’t draw any plans, just measured a few times and then went to cutting a bunch of particle board leftovers at the table saw. I routed rebates on the sides, fronts and backs to lap the boxes and sink in the bottom. It turned out that having no plans was a stupid idea. I cut exactly on the lines as I calculated and measured, however, the math in my head fell apart when it eventually met reality. The bottoms are too short, so I gotta glue on some strips. Also, with the longer fronts, the sides won’t work either, I have to fix them as well. :-D
Finally, the lid of my cyclone bucket broke when the negative pressure got too large. Oh well. It was just an old wood glue bucket, I’ve got another empty one, so I can use that lid but strengthen it first with some plywood. Something for future Lyse to deal with.
All in all, it was still good fun. Wood (haha) do it again, but at least with some sketches on paper. ;-)
@anth@a.9srv.net Congrats, that’s pretty cool! Quite some time, I’m impressed.
@prologic@twtxt.net You’ll sometimes find the “Creation Date” in whois
. Our domain was registered in 2009. Woah. That’s also been a while, crazy.
@movq@www.uninformativ.de Yup, that’s Mr. Compiler Explorer. :-)
printf
?!)
@prologic@twtxt.net There have always been and there will always be people who have absolutely no clue what they’re doing. I’ve been 100% one of them when I started. Guaranteed, heaps of new SQL injections are born every single day, numbers rising.
That doesn’t justify all the WAF crap in the first place, though. In my opinion it’s just a filthy plaster applied to an injected wound. The software itself must be secure. Otherwise, don’t put that shit on the internet. Probably not even operate it at all. Nowhere. Fix it or throw it in the bin.
@kat@yarn.girlonthemoon.xyz @bender@twtxt.net Hahaha! I can’t recall either, maybe even just a chisel or a knive? I’m not terribly good at it, not even close. It’s just fun. And I do it all too rarely. :-/
@kat@yarn.girlonthemoon.xyz That’s cool. Also, looks like a fun woodworking project in case you exceed the hundred slots. :-) The plywood lap joints might be quite repetetive, but gang cutting them with a story stick or some other fixture shouldn’t be too terrible.
@movq@www.uninformativ.de Their gold teeth collection? ;-)
What do you think I just learned about in this awesome Computerphile video with Matt Godbolt called “Subroutines in Low Level Code”? https://www.youtube.com/watch?v=1su3lAh-k4o
Here’s the plot twist, the phrase “till the cows come home”. Hahaha, I never heard this before, but I love it! It’s always interesting to me to hear English sayings. Sometimes we have the same in German, sometimes – like in this case – entirely different ones. It’s fascinating that even though one hasn’t come across proverbs, it’s typically still clear from the context what’s meant.
Yep, some unexpected language stuff. ;-)
Thanks, @movq@www.uninformativ.de! That seems to be much easier. It’s already implemented in the Python docs as examples of recvmsg(…)
and sendmsg(…)
:
- https://docs.python.org/3/library/socket.html#socket.socket.recvmsg
- https://docs.python.org/3/library/socket.html#socket.socket.sendmsg
I looked at them sooo many times in order to figure out why my SCM_CREDENTIALS
sending code didn’t work. :-D
Yesterday, I had a look at Unix domain sockets and how to obtain the caller information: https://lyse.isobeef.org/caller-information-via-unix-domain-sockets/
@bender@twtxt.net Deal!
@movq@www.uninformativ.de @bender@twtxt.net @kat@yarn.girlonthemoon.xyz Oh yeah, this is a great article! The site looks quite horrible, but tastes are different. :-)
@kat@yarn.girlonthemoon.xyz Oh dear, what a way to start the day! :-(
Once again, we had a lovely sunset: https://lyse.isobeef.org/abendhimmel-2025-05-04/
@javivf@adn.org.es You also cut from the front and not the back.
@prologic@twtxt.net I also wore gloves, but after hours of demanding work, my shoulders and wrists were shattered. I hope I’m back to normal tomorrow. :-)
@prologic@twtxt.net To clarify, from my observations on how the system behaves, it feels like that. This doesn’t make it any better, I know. Sorry mate! I never claimed that testing is always easy, but in my experience it sure does help cutting down regressions. But to each their own, no worries. The diagram is all Greek to me. Anyway.
@bender@twtxt.net True.
@movq@www.uninformativ.de Indeed, a Wüstenmaus sounds cute. However, a Wüstenratte — which is more a desert rat — not so much.
@prologic@twtxt.net ODD, lol. I don’t wanna be rude, but this sounds more like Code And Fix.
We just split about one and a half cubic meters of fire wood at our scout yard. And even more chainsaw action to cut the logs in smaller chunks. I’m bloody tired now. But it was really great fun swinging the axe. I will sleep like a rock tonight.
We went on a 14 kilometers long hike in the heat, only a few spots were in the shade, most of our trip was in the open fields with the sun beating down on us. We reapplied the sun blocker after about two hours or so. All in all it took us about three and a half hours before we reached our destination Besigheim.
Last time I was there it was rainy, now we had the exact opposite. After some yummy Chinese lunch we visited the old town. There’s some gorgeous timer framing to see. When kept in decent shape, it just looks so dang cool.
Since it was too hot, we rode back by train. Despite the heat and some sections near the roaring Autobahn, this was a nice hike. Would do it again. Only in colder weather, though. I certainly don’t wanna trade my comperatively larger (still nothing to other more rural areas), covering forests with the wide open fields and vineyards in summer. That’s for sure.
https://lyse.isobeef.org/wanderung-von-asperg-nach-besigheim-2025-05-01/
@quark@ferengi.one Despite the Reddit part (I never understood it), this is a great analysis. I could not have put it any better. I also feel quite home here with the all feeds I follow. It’s a small bunch of good people.
The temperatures are getting pleasant now. All the freshly cut grass really smells lovely. Looks like farmers are securing their harvests before the rain hits tomorrow in the arvo.
@movq@www.uninformativ.de @bender@twtxt.net 28°C right now, but luckily, just 20°C tomorrow and rain. Even a thunderstorm at night. On Sunday we’re down to 12°C. What a ride. Oh boys!
@bender@twtxt.net It’s like having good manners at the table. Use forks and knives. ;-)
@movq@www.uninformativ.de This suits the background image perfectly.
3rvya6q
and your feed, but your feed certainly does not include that particular twt (it comes from my feed).
@movq@www.uninformativ.de Oooooohhhhhh, I see. Hmmmm.
To answer your question: Ideally, you would have replied directly to my reply. :-) The flat conversation model always felt unnatural to me. I just yielded to the community’s way of doing it.
@movq@www.uninformativ.de When I reply to a message, I typically already mention the feed. Just like in this very message. I believe this mechanism should work for most replies. But there are of course the odd responses where I do not mention the original feed, but rather some other feed(s) instead to which I actually want to reply. Maybe “forking”, as prologic calls it, would be the better option there.
I visited a good mate after a day in the office and went for a stroll in the evening. It still was really hot, phew, about 24°C. Must have been the aftermath of the fire in the morning! For sure! The firealarm went off during a meeting and we all had to leave the building. Anyway, I only managed to take one lizard photo, all the other ones we came across immediately vanished in the brush or cracks in the vineyard walls. The kestrels were way more cooperative:
@movq@www.uninformativ.de Oh, I see. I reckon I accidentally late April-fooled myself. :-D
It’s an interesting comparison. I really should have thought about that.
You’re right, the rendering would not be very spectacular. :-)
@movq@www.uninformativ.de Agreed, finding the right motivation can be tricky. You sometimes have to torture yourself in order to later then realize, yeah, that was actually totally worth it. It’s often hard.
I think if you find a project or goal in general that these kids want to achieve, that is the best and maybe only choice with a good chance of positive outcome. I don’t know, like building a price scraper, a weather station or whatever. Yeah, these are already too advanced if they never programmed, but you get the idea. If they have something they want to build for themselves for their private life, that can be a great motivator I’ve experienced. Or you could assign ‘em the task to build their own twtxt client if they don’t have any own suitable ideas. :-)
Showing them that you do a lot of your daily work in the shell can maybe also help to get them interested in text-based boring stuff. Or at least break the ice. Lead by example. The more I think about it, the more I believe this to be very important. That’s how I still learn and improve from my favorite workmate today in general. Which I’m very thankful of.
@movq@www.uninformativ.de Wow, that’s sick! Assuming the rendering is correct, I never realized the mountain ranges being this steep and tall. This has real education potential for geography classes. Really cool!
git pull
on one of my repos – once every two minutes. This is a very pointless endeavour. I push new code a couple of times per month.
@movq@www.uninformativ.de In case you reconsider, it would be even easier then to just send an HTTP 429 Too Many Requests
. :-)
now()
or the message's creation timestamp? I reckon the latter is the case, but it's undefined right now. Then we can discuss and potentially tweak the proposal.
@bender@twtxt.net Hehehe! :-D
@movq@www.uninformativ.de I have to admit, I didn’t follow the topic very closely, but I was under the impression that there were more votes on location-based addressing. But maybe I’m completely wrong. Anyway. I don’t have the energy to be part of a fundamental debate.
@prologic@twtxt.net Thank you for writing this together. I just left a few comments.
git pull
on one of my repos – once every two minutes. This is a very pointless endeavour. I push new code a couple of times per month.
@movq@www.uninformativ.de You better push new code sooner!!
As @bender@twtxt.net says, that sounds like a bot. I’d just block the IP address, hoping it doesn’t change all the time. But then you know for sure that it’s the AI fuckwits.
Also, the devil in me thinks it’s funny to swap out the repo in question for something entirely different. :-D
Oh wow, that 48 hours timelapse from SDO is super cool: https://social.bund.de/system/media_attachments/files/114/413/834/747/006/466/original/91b1698392ae5188.mp4 At the end, the moon is whizzing by.
@xuu@txt.sour.is Hahaha, that’s cool! You were (and still are) way ahead of me. :-)
We started with a simple traffic light phase and then added pedestrian crossing buttons. But only painting it on the canvas. In our computer room there was an actual traffic light on the wall and at the very end of the school year our IT basics teacher then modified the program to actually control the physical traffic light. That was very impressive and completely out of reach for me at the time. That teacher pulled the first lever for me ending up where I am now.
@prologic@twtxt.net Exactly, @bender@twtxt.net! :-D This is at the entrance of a veggie farm (11 & 12) where there are free-ranging kids playing on the road, so people should slow down when driving there to buy some supplies. I also wondered why the sign says “Halt!” instead of “Langsam fahren!” (Drive slowly!) or something like that. On second thought, maybe to actually park there on the street right at the property line.
I actually never walked on that road before and discovered that this was a dead end. There’s usually at the very least a foot path on which to continue when passing a farm. Not this time, though. I didn’t want to stamp down the high grass to cut across country, so I had to walk back maybe 150 meters. Not too bad.
twtxt.txt
feeds. Instead, we use modern Twtxt clients that conform to the specifications at Twtxt.dev for a seamless, automated experience. #Twtxt #Twt #UserExperience
@prologic@twtxt.net Phew, I’m indeed not twtxt.dev, because I sometimes actually do edit my feed with vim like a barbarian.
7
to 12
and use the first 12
characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q
or a
(oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! -- I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social's 5th birthday and 5 years since I started this whole project and endeavour! 😱 #Twtxt #Update
@prologic@twtxt.net Can you please draft up a specification for that proposed change with all the details? Such as which date do you actually refer to? Is it now()
or the message’s creation timestamp? I reckon the latter is the case, but it’s undefined right now. Then we can discuss and potentially tweak the proposal.
Also, I see what you did there in regards to the reply model change poll. ]:->
@movq@www.uninformativ.de I started with Delphi in school, the book (that we never ever used even once and I also never looked at) taught Pascal. The UI part felt easy at first but prevented me from understanding fundamental stuff like procedures or functions or even begin
and end
blocks for if
s or loops. For example I always thought that I needed to have a button somewhere, even if hidden. That gave me a handler procedure where I could put code and somehow call it. Two or three years later, a new mate from the parallel class finally told me that this wasn’t necessary and how to do thing better.
You know all too well that back in the day there was not a whole lot of information out there. And the bits that did exist were well hidden. At least from me. Eventually discovering planet-quellcodes.de (I don’t remember if that was the original forum or if that got split off from some other board) via my best schoolmate was like finding the Amber Room. Yeah, reading the ITG book would have been a very good idea for sure. :-)
In hindsight, a console program without the UI overhead might have been better. At least for the very start. Much less things to worry about or get lost.
Hence, I’d recommend to start programming with a console program. As for the language, not sure. But Python is probably a good choice, it doesn’t require a lot of surrounding boilerplate like, say Java or Go. It also does exceptionally well in the principle of least surprise.
@sorenpeter@darch.dk I see, ta. The big spring cleaning continues. ;-)
I went on a small hike, just 12-13km this time. The weather was great, blue sky, sunny 18°C, but with the wind it felt colder. Leaves and other green stuff is exploding like crazy. It looks super beautiful right now.
I came across an unfortunately dead salamander on the forest road, some fenced in deer, heaps of sheep, some unmagnetic cows (some were aligned very roughly north-south, but mainly with the axis of the best view I believe), a maybeetle and finally an awesome sunset. Not too shabby! The sheep were mehing all the time, that was really lovely to hear. And the crickets were already active, too. Didn’t expect them to hear yet. I tried to record the concert, but the wind messed it all up. Oh well.
@bender@twtxt.net Must be the US tariffs, it’s working reasonably quick in Europe. :-D
@movq@www.uninformativ.de Your next experiment should be triangles. :-)
I just fixed a bug in tt’s reply to parent feature. Previously, when the message tree looked like the following
Message
├╴Reply 1
│ └╴Subreply
└╴Reply 2
and “Reply 2” was selected, pressing A
to reply to the parent should have picked “Message”. However, a reply to “Reply 2” was composed instead. The reason was a precausiously introduced safety guard to abort the parent search which stopped at “Subreply”, because its subject didn’t match “Reply 2”’s. It was originally intended to abort on a completely different message conversation root. Just in case. Turns out that this thoght was flawed.
Fixing bugs by only removing code is always cool. :-)
@movq@www.uninformativ.de Bwahahaahaaa, this is fucking brilliant, I love it! :-D What a wonderful thing to start my Sunday.