> [Compared to Excel] serious financial, medical or industrial applications should probably stick to the more mature calculation capabilities found in Factorio circuits.
@darch I could be wrong, but I don't see a pun here, maybe some English native speaker can correct me. From my point of view it's just a parody on Robin Hood with some ridiculously funny spin. Monty Python at their finest. The lupin part *might* be a reference to tulip mania, when prices in the Netherlands for tulips bulbs went through the sky in 1637. Or it's just some random thing without a deeper meaning.
Our four hour long night hike turned out to be really great. It was surprisingly warm, most of the way a t-shirt was enough. Only in the end we had to pull over a jumper for the long sleeves. We saw plenty of bats flying around us and also a marten in one of the villages. It was sitting in the middle of the road and then hid under a parked car. On the downside, tons of mozzies were also around.
Gates of Ruin Rechberg are closed at nightIn one place the street lights shining on the tree leaves in combination with slight mist turned the scenery into something really incredible. Can't describe it other than mystical. Just super beautiful and impossible (for me) to capture on film.
We brought our torches, but didn't end up using them. The moon and starlit sky was enough. Only in the forests it sometimes got a bit dark on us. The first night hike of the season was a great success and will be repeated several times.
Lupinshttps://lyse.isobeef.org/waldspaziergang-2023-05-28/
Meadow
fc. @abucci Heck yeah, great story! :-D I never came across something similar. I know these buses exist, but I've never seen one in person.
Sunset
Rain and sun
Backlit cloud behind some trees at sunset
That reminds me that I have to get replacement ear pads for both my headset and headphone. The synthetic leather is falling apart and black fuzzy crap ends up all over my face. Also, my headset's left ear piece has some intermittent contact that seems to get worse lately. Shaking my head usually fixes it for some time. Not sure if trying to repair that will finally break the headset instead.
At the Fuchseck summit a guy went down the steep mountain straight through the brush. So we thought, let's take this beaten path, too. But there was none. We couldn't figure out where he went and which route he took. We only heard the rustling of leaves and cracking of twigs and branches at the beginning when we were still taking photos up top. But we said, let's try it anyway, when he manages it, we will, too. The North slope was about 70° steep and covered with 15 cm of leaves. Super slippery, we slid more than walked. But once committed, there was no easy way back up again. There were lots of sketchy sections and I wondered what the heck I was doing there. We had to brace ourselves with one or sometimes both hands on the slope. Then we saw the dude sitting in a tree and we continued our adventure downhill. 29-31 show the much easier parts closer to the bottom before we hit an official path.
Later we took a new well-graveled logging trail which then dead ended. So we then decided to walk through the tall grass in the forest to meet a parallel footpath. We survived much crazier terrain earlier. So what could possibly go wrong? This long patch of grass was an old, now probably abandonned path anyways. I misjudged the distance to the other path quite a bit and it took us much longer than anticipated. Finally, on the real path, I had collected ten ticks on my pants! Bloody bastards.
After the shower I now feel like a new person. I reckon I'll find some great sleep tonight.
Probably cherry stones on a barbed wire fence
Tadpoles
jot before. Often I simply use pwgen -sy 64.
Deer eating yummy grasses
Bird on a tree
Bees on dandlionsCan't get enough and want more? This way! I've got you covered.
Activity pixel display
Tool well boxes for sawhorses 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.~
Thick fog
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:
Very red sunset
https://lyse.isobeef.org/waldspaziergang-2023-04-28/
Particle board with fucked up rebbet
# 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, 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/
Sunset
Fenced in deer like the shade
Female common blackbird with nest construction material in her beak
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
/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?~
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
Blackbird looking at the cameraPlease 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.
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. :-)
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.
lexer.go and newparser.go resemble the parser combinators: https://git.isobeef.org/lyse/tt2/-/commit/4d481acad0213771fe5804917576388f51c340c0 It's far from finished yet.
The first attempt in parser.go doesn't work as my backtracking is not accounted for, I noticed only later, that I have to do that. With twt message texts there is no real error in parsing. Just regular text as a "fallback". So it works a bit differently than parsing a real language. No error reporting required, except maybe for debugging. My goal was to port my Python code as closely as possible. But then the runes in the string gave me a bit of a headache, so I thought I just build myself a nice reader abstraction. When I noticed the missing backtracking, I then decided to give parser combinators a try instead of improving on my look ahead reader. It only later occurred to me, that I could have just used a rune slice instead of a string. With that, porting the Python code should have been straightforward.
Yeah, all this doesn't probably make sense, unless you look at the code. And even then, you have to learn the ropes a bit. Sorry for the noise. :-)