@marado@twtxt.net I see, thanks! Of course somebody had already thought of that. :-)
I had to use my tick stones twice today to crush those little bastards. I detected them on both of my hands shortly one after the other. Also came across two deer and finally managed to see some bees in closeup. My mate takes pictures of them for a month already. I reckon our seasons always lack a bit behind (but not this many weeks).
Can’t get enough and want more? This way! I’ve got you covered.
I’m wondering, has somebody ever tried to use these activity pixel matrices for some kind of art and create an image or text? It might become @thecanine@twtxt.net’s longest endeavor for a new grayscale dog so far. ;-)
https://lyse.isobeef.org/user/lyse/twtxt.txt
, http://lyse.isobeef.org
and https://lyse.isobeef.org
to the yarns blacklist? Especially the first URL spams my error log every hour. It might also be useful to do some housekeeping with other crap URLs: https://search.twtxt.net/stats/feeds/discovered?l=30&q=lyse&s=-failures
Now there is a way to block feeds in yarns: https://git.mills.io/yarnsocial/search/pulls/16
Finally, both tool well boxes for the sawhorses are done. 09-11 illustrates the use on a small sawhorse. However, they will be screwed to a larger one.
I’m thinking that I might be better off if they can be just hung without any tools. The first thing that came to mind are two U-shaped hooks which are attached to the box and get simply hung into the sawhorse beam. In order to avoid bumps on the beam by the hooks, I could mortise two slots, so the hooks are then flush. But then I have some mortises in the top, which might not be ideal when the tool wells are not attached.
Another idea is to mount two larger dowels (~20 mm diameter) to the side of the tool well and drill two matching holes into the beam. Then the tool well could be slid in from the side. To avoid coming loose, a wedge could be inserted in a mortise of the dowel on the other side of the beam. Like a traditional wooden joint in benches and tables. Let’s see what I end up with.
And three quarter of an hour later the sun has done its job. Although, it’s overcast now as I write this three photo update.
@stigatle@yarn.stigatle.no With his right eye pulled up, he’s gonna eat me every second! :-D He’s enjoying his new chain, isn’t he? Already ran around the tree stump a bunch of times. :-)
What a nice soup! Can’t even see the other hillside. There are two minutes between 02 and 03, one can see the fog slightly clearing.
@movq@www.uninformativ.de Yeah. Although, two thunders the whole day (just a few minutes apart when we were in the forest), that was it. But a very rainy day. ;-)
If I press the trigger button halfway down (until I feel a slight resistence), the camera sets focus and exposure. They get locked when I hold it halfway. Only if I press it all the way, the picture is taken. After today’s adventure the camera now triggers even when the button is only pressed halfway. Sometimes, maybe 10%, it works as it should. But the rest of the time, the photo is taken prematurely. I can feel both points, but the second one seems to have shifted upwards to the first one. This really sucks.
Had some nice fog and sunset today:
@movq@www.uninformativ.de Man, this is very nice! The bugs in 4642 and 4630 are really cool. :-) The low hanging clouds or fog in 4651 remind me of my view this evening. In just about 15 minutes, fog rolled in. 4653 is an awesome cloud photo. Your videos 4611 and 4613 are also amazing. I love how the birds are singing and thunder roars in the distance. Just super cool. Fascinating to see how rapidly the storm moves in.
The weather forecast was completely off. Dry with two small exceptions of rain in the next hour, they said. Literally the opposite was true. Even got thunder twice. I can’t get any wetter, legs and feet completely submerged in water. I had to wring out my socks and hiking trousers, shoes are too stiff, though. Should have worn rubber boots and a pair of rain trousers to my rain jacket. Even the camera went on strike (luckily, it works again). I have to admit, in the beginning, walking in the rain was really nice. But when you pump water with every step, it’s getting a bit unpleasant.
@prologic@twtxt.net Yeah. Also cut my short side pieces 16 mm too long because I’m an idiot (and hence wasted a bit more board than needed). But better than trimmed too short. And luckily, it’s reclaimed material, too. Gonna complete that project tomorrow. Hopefully.
@movq@www.uninformativ.de It’s you-urgently-need-a-break-day!
Oh crap, the clamp on my router fence slipped, so the fence moved and now my board has a crooked rabbet. This is the side piece of a tool rest box that can be mounted on sawhorses, so it could be worse if it were some nice project for the house. But it still looks like shit. Always make sure everything is tight before flicking the switch, kids!
I don’t like the idea of an additional special bang. DTD, bah! Why not simply use # doctype = whatever
? Also, which problem does this solve? What would clients do differently? And humans just could look at the comment or URL and see that this feed makes use of extensions – if they care. Twtxt purists would certainly hate such a new thing, too, I don’t think it helps them in any way. So I don’t see the use case for that. Can you please elaborate, @darch@neotxt.dk, what you had in mind?
My feed’s preamble starts with (links to be debatable):
# Learn more about twtxt at: https://github.com/buckket/twtxt
# This feed makes use of some extensions: https://dev.twtxt.net/
Thanks, @prologic@twtxt.net! Hahaha, “fire lake from hell”, I like that one! :-D 12 is zoomed into the sunset from 11’s bottom right.
@prologic@twtxt.net Phew, at first I thought that was ambient temperature. Glad you’re over the worst part.
@prologic@twtxt.net That’s cute.
@carsten@yarn.zn80.net I think nothing of AI in general. Too often AI-stuff turned out to be some kind of fraud. My general opinion of AI is very bad. You don’t know how or what the thing “learned”, most often something very different than what one would think. Hence, there’s no way to fix it if it’s broken. And as far as I understand it one doesn’t know when it’s trained enough. So in my eyes it’s a giant waste of resources. Anyways.
Hope you’re doing alright, @carsten@yarn.zn80.net. Just a nice cloud formation on my way to the scout meeting. Added two more shots:
@carsten@yarn.zn80.net Oh, all fake. Too bad.
It’s nearly suncream time again. The sun is blazing down today. T-shirt weather at 16°C without much wind. Even 19°C tomorrow. The yellow dandelion blooms beautifully in the meadows. We went on a quick stroll.
@carsten@yarn.zn80.net Wow, good drawings! What program did you use? Looks like straight out of a comic book.
@carsten@yarn.zn80.net Ein Kuchenduft liegt in der Luft!
Oh yes, @ionores@twtxt.net, I think the construction site is in the hedge. Some years back there were nests, too. But bloody cats mugged them. I hope the new residents are luckier this time.
Thanks, @movq@www.uninformativ.de! Yeah, that was really awesome. She just landed not even two meters next to me when I was taking photos of the sunset. There was just an empty washing line between me and her, but I reckon that doesn’t really count. :-) Normally, they all fly off immediately (or not land in the first place), but she watched me for about a minute over her shoulders. And I in turn froze and tried to push the trigger as many times as possible before she suddenly took off. Due to the low light, most photos were quite blurred, she turned her head very often left and right. And it certainly did not help that my zoom was too close at first, too. I just got very, very, very lucky today. :-)
@xuu@txt.sour.is Heck, this is interesting! I did not know about plan files, just read up on them and yes, your conclusion seems spot on! ;-) Hahaha, very cool.
@prologic@twtxt.net Damn, speedy recovery! In a few days you should be hopefully over the worst part. That’s what I’ve heard and seen most of the time.
@darch@neotxt.dk Haha, all good. I actually expected that to be a software bug for sure, not user error. ;-) But better that way. Much easier to “fix”, as proven. :-) And I can confirm, no more requests for that file.
@prologic@twtxt.net Aha, got you! Thanks for digging that up. :-)
@xuu@txt.sour.is @prologic@twtxt.net I will never give up threading! It’s a very vital civil achievement.
Thanks, @prologic@twtxt.net, these are common blackbirds: https://en.wikipedia.org/wiki/Common_blackbird
@prologic@twtxt.net That would be great.
@prologic@twtxt.net I only suggested to change the info page, not the user agent. ;-)
@prologic@twtxt.net Ah, I see! But why are there no caching request headers sent along (judging by HTTP 200 instead of 304)?
yarnd
, tt
, jenny
, twtr
and other clients? 🤔 Thinking about (and talking with @xuu on IRC) about the possibility of rewriting a completely new spec (no extensions). Proposed name yarn.txt
or "Yarn". Compatibility would remain with Twtxt in the sense that we wouldn't break anything per se, but we'd divorce ourselves from Twtxt and be free to improve based on the needs of the community and not the ideals of those that don't use, contribute in the first place or fixate on nostalgia (which doesn't really help anyone).
@prologic@twtxt.net I agree with @abucci@anthony.buc.ci, @darch@neotxt.dk and @marado@twtxt.net. Also, in order to set a good example, we would have to rename our feed filenames which would break threading.
https://lyse.isobeef.org/user/lyse/twtxt.txt
, http://lyse.isobeef.org
and https://lyse.isobeef.org
to the yarns blacklist? Especially the first URL spams my error log every hour. It might also be useful to do some housekeeping with other crap URLs: https://search.twtxt.net/stats/feeds/discovered?l=30&q=lyse&s=-failures
And another weird thing is that yarnd’s User-Agent header now contains all sorts of build information: yarnd/0.15.1@7dd5a93e 2023-03-27T00:53:59+10:00 go1.20.3 (~https://…
I reckon this is a regression from the version change on the info page I proposed on IRC months ago. Maybe even last year.
What a joy to look in the logs once in a while. :-D
https://lyse.isobeef.org/user/lyse/twtxt.txt
, http://lyse.isobeef.org
and https://lyse.isobeef.org
to the yarns blacklist? Especially the first URL spams my error log every hour. It might also be useful to do some housekeeping with other crap URLs: https://search.twtxt.net/stats/feeds/discovered?l=30&q=lyse&s=-failures
Also, @darch@neotxt.dk’s yarnd is requesting my /twtxt-2022-08.txt
every few minutes (interval varies between ~2-5 minutes). Nothing seems to be cached, though, because 200 is sent all the time. Any idea what’s going on here and how to fix it, @prologic@twtxt.net?
In yarnd one can block certain URLs. Is there a way to do the same in yarns, @prologic@twtxt.net? If so, can you please add https://lyse.isobeef.org/user/lyse/twtxt.txt
, http://lyse.isobeef.org
and https://lyse.isobeef.org
to the yarns blacklist? Especially the first URL spams my error log every hour. It might also be useful to do some housekeeping with other crap URLs: https://search.twtxt.net/stats/feeds/discovered?l=30&q=lyse&s=-failures
Please ignore the dirty railing. I simply claim that the blackbird only therefore feels so comfortable!! I just started to wipe it clean but then it began to rain. Gotta finish tomorrow.
Great, @stigatle@yarn.stigatle.no! Is this a double free in https://github.com/stig-atle/YarnDesktopClient/blob/main/YarnDesktopClient.cpp#L126? curl_easy_cleanup
is called twice (lines 126 and 128) in case of an error. Similarly in other code blocks.
And you’re leaking memory: https://curl.se/libcurl/c/curl_slist_append.html You gotta have to call curl_slist_free_all
. Maybe use a cURL C++ wrapper library or write your own wrapper around the C library to make your life a bit easier.
Regarding escaping the JSON input for your HTTP requests, have a look there: https://rapidjson.org/md_doc_stream.html#StringBuffer This is probably the easiest.
Yeah, I know, small baby steps. :-)
@stigatle@yarn.stigatle.no That’s what our weather looks like, too. A nice, dark gray rain soup.
@stigatle@yarn.stigatle.no Happy hacking, mate! :-) Assuming that the server sends a proper certificate chain, you need just the root CA that signed the intermediate or server certificate locally in your key store.
@prologic@twtxt.net You can’t win them all. Just leave that channel. Fixed. :-)
Nice work, @stigatle@yarn.stigatle.no! Didn’t try to compile it because I don’t run yarnd (and I avoid GTK like the plague), but looked at the code. First and foremost, I very strongly suggest you choose your favorite code formatter and apply it. :-) Especially the space placement is inconsistent. Secondly, if someone’s password contains a quote, they’re having a bad day. ;-)
Thirdly, are you sure about disabling TLS certificate checking? And one last remark: personally, I like early returns, it makes the code more readable in my opinion than deeply nested control structures. Especially, when the code gets longer, questions like “here’s an else
, what if
did it belong to a few pages up?” are greatly reduced. Some people even say that grouping stuff into functions avoids long functions altogether.
Enjoy your pizza! I’ll have some tomorrow. Dough is proving overnight.
@movq@www.uninformativ.de Wow, that’s crazy.
@xuu@txt.sour.is @prologic@twtxt.net @movq@www.uninformativ.de Not just limited to cloud.
@xuu@txt.sour.is @prologic@twtxt.net Ta! Will work on that and improve it as time permits.