Autumn is there: https://lyse.isobeef.org/morgensonne-2024-10-11/
@prologic@twtxt.net Bluetooth still classifies as connecting remotely. The attacker has to be in close proximity, but yeah. If you use it only where noone else is around, you’re fine. :-)
@prologic@twtxt.net I have no clue, but the only thing that comes to mind is that chances of RCE are higher the more it exposes.
Content-Type: text/plain
might be not enough, as the HTTP spec defaults to Latin1 or whatever, not UTF-8. So there is a gap or room for incorrect interpretation. I could be wrong, but I understand @anth's comment that he doesn't want to even have a Content-Type
header in the first place.
Just to be clear, I’m 100% for mandating UTF-8 and only UTF-8. Nothing else. Exactly how it has always been.
I just like to send a proper Content-Type
stating the right encoding to be a good web citizen. That’s all. :-)
Righto @anth@a.9srv.net, v2 is up again for me:
Clients (and human readers) just assume a flat threading
structure by default, read things in order […]
I might misunderstand this, but I slightly disagree. Personally, I like to look at the tree structure and my client also does present me the conversation tree as an actual tree, not a flat list. Yes, this gets messy when there are a lot of branches and long messages, but I managed to live with that. Doesn’t happen very often. Anyway, just a personal preference. Nothing to really worry.The v2 spec requires each reply to re-calculate the hash
of the specific entry I’m replying to […]
Hmmmm, where do you read that the client has to re-calculate the hash on reply? (Sorry, I’m probably just not getting your point here in the entire paragraph.)Clients should not be expected to track conversations back
across forking points […]
I agree. It totally depends on the client.
@movq@www.uninformativ.de If my memory serves me right, I think v2 doesn’t mention UTF-8 at all. Then I came along and noted that the Content-Type: text/plain
might be not enough, as the HTTP spec defaults to Latin1 or whatever, not UTF-8. So there is a gap or room for incorrect interpretation. I could be wrong, but I understand @anth@a.9srv.net’s comment that he doesn’t want to even have a Content-Type
header in the first place.
I reckon it should be optional, but when deciding to sending one, it should be Content-Type: text/plain; charset=utf-8
. That also helps browsers pick up the right encoding right away without guessing wrong (basically always happens with Firefox here). That aids people who read raw feeds in browsers for debugging or what not. (I sometimes do that to decide if there is enough interesting content to follow the feed at hand.)
Merci, @movq@www.uninformativ.de! Back to gray this afternoon again, mostly dry, though.
Cool, @anth@a.9srv.net, thanks for the followup! I have to reread the original v2 in order to really follow your explanation, but that document seems to be offline at the moment. I’ll try again later. :-)
Oh no, @xuu@txt.sour.is. :-( Speedy recovery and I hope you still miss out on long-covid.
Ta, @prologic@twtxt.net!
Finally, a sunny day. I jumped at the opportunity and went for a quick evening stroll: https://lyse.isobeef.org/waldspaziergang-2024-10-09/
Good luck and all the best wishes, @bender@twtxt.net. Please don’t die!
@movq@www.uninformativ.de That was indeed an interesting dive! I also never heard of just
before.
Couldn’t agree more, great article!
Open(…)
being successful and only executing the first command giving me that error. Meh.
@movq@www.uninformativ.de No, that’s just a general SQLite thing: https://gitlab.com/cznic/sqlite/-/issues/102 But, mkdir -p $dir
and just retrying the command works.
b2sum
program isn’t very widely available.
@movq@www.uninformativ.de yarnd, jenny and tt.
@bender@twtxt.net Yep, certainly not a larger city, just a ~20k town.
@thecanine@twtxt.net Woof-woof! If it’s already perfect, no need to disimprove. :-)
Awesome, “unable to open database file: out of memory (14)” actually means that the SQLite file cannot be created, because the parent directory does not exist. Bonus points for Open(…)
being successful and only executing the first command giving me that error. Meh.
@bender@twtxt.net Haha, the easter bunny brought me a Bad Gateway.
@bender@twtxt.net Over here, people can put red ribbons on their fruit trees to signal that they are free to use for everyone. That’s an effort to minimize the giant food waste. Meadow orchard owners who do not have the time or energy anymore to harvest themselves (I reckon a lot of them are of age nowadays), can ensure that the tasty things do not simply rot away. Also, the town hangs those ribbons on trees on municipal properties.
They introduced these ribbons a few years back. It’s a really cool system. The colors of the ribbons vary from town to town. It seems most actually use yellow ribbons. The rules are to be respectful, only take what you really need (common household amounts) and be careful not to break branches, not to trample down higher grass, watch out for pants and animals, etc. Sometimes, a tree owner only grants access to a few trees. So, you’re only allowed to take from the explicitly marked ones. I mean, common sense really, don’t be an asshole. :-)
We just pick up what has fallen down. You’re also allowed to pick directly from the tree, but the apples on the ground are already fully ripe. Or bad, but you can typically distinguish between the two rather easily. The apples that fall down early are usually full of worms. Later on, it’s the ripe ones. Yeah, if a ripe one lands in a patch of spoiled ones, it’s also going bad fairly quickly. So, it pays off to visit regularly and check.
Not all apples are equal, though. It’s important to check the variety before gathering them. Cider apples are worthless to us. They just taste awful. Typically, these are the tiny ones, but there are also some tiny ones which are actually very delicious. So, a taste test is mandatory.
Then for apple sauce we just wash off the occasional dirt on the apples at home. Typically, you can get rid of the worst already by wiping it on the grass when picking. We simply cut them in quarters, bigger apples also in eights. Bad spots and the cores are removed. To avoid oxidation, we throw them in a bowl of water with citric acid. Once that bowl is full, we transfer them into a big pot. Rinse and repeat.
The pot has some water in it, so the apples do not scorch. Shortly before we finish cutting the apples, the stove is heated. Then, we just let the whole mass heat up. Don’t forget to stir every now and then. The longer it simmers, the easier it gets to actually stir the now softer mass. It also sinks down a bit. You can also use a potato masher to help get some sort of a pulp.
When the pulp is fairly soft it’s pressed through a strainer. People here call the food mill “Flotte Lotte” (quick Charlotte) after a brand name. We use the tiniest sieve with 1mm holes. Unfortunately, there’s no smaller one. But it gets 99.99% of the junk out, skin, missed seeds, all the coarse stuff. After each load the food mill has to be cleared from pomance, so it doesn’t plug up all the holes or worse, the coarse crap is pressed through.
For some strange reason we have not figured out, we got quite a bunch of skin pieces in the apple sauce on Wednesday. Somehow they managed to get through. Very strange, this has never happened before. To filter them out, we just passed the whole thing through the Flotte Lotte a second time.
Around 10% sugar by weight is added to help preservation. A pinch of cinnamon and then it’s basically ready when mixed up properly.
Fill the apple sauce is in jars and make sure to leave enough space for some expansion when getting cooked in a moment. Wipe any spilled sauce form the glas rims, close the lids with a rubber seal and clamp ‘em shut. The jars are placed in a big pot or “Einkochautomat” (translates roughly to preserving machine). It’s a large pot that is electrically heated and automatically maintains the temperature using a thermostat. The water level has to be about 2/3 of the top layer of the jars (they can be stacked). Any higher is unnecessary and just wastes water. The jars get cooked for half an hour at 90°C. Then, they can be lifted out with a pairs of jar tongs. After cooling down, the clamps are removed. If a jar hasn’t sealed properly, you notice it right away.
The last thing is to label and store them in the cellar or somewhere.
Eventually, pull on the rubber seal’s tab to open a jar, put the apple sauce on a waffle or something else and enjoy the blast of taste in your mouth. :-)
Oh, that text got a wee bit longer than anticipated. 8-)
Made the first apple sauce of the season in around three to four hours of work. Pretty cool, very, very little waste. The jars are currently cooking.
@bender@twtxt.net Yes, a proposal alone is certainly not enough, but a good start. Absolutely necessary in my opinion. With everything just in thin air and constantly changing (at least it appears to me that way), I’m lost.
I have the feeling that the hashing part is the most important one that should be sorted first.
@quark@ferengi.one I definitely agree with the first part. Not so sure about the second one. Maybe it then turns out miserable, too. :-?
@bender@twtxt.net I do hope that it ends up fancy! But maybe it turns out rather crappy. Metal working is definitely beyond my capabilities. I just find it super fascinating.
I’d also appreciate if somebody wrote a proposal. It’s very hard to piece everything together across all those many conversations.
@david@collantes.us I plan on building an X-Y table. But with these leadscrew prices, I might as well just buy a whole import table altogther.
Oh boy, I’m looking for trapezoidal (like ACME thread) screws and nuts in left hand form. The rods are already expensive, but nuts feel like a total ripoff. A hex nut for Tr20x2 being 30mm long and 30mm in “diameter” costs me 22 bucks! O_o Just a single one, made of regular steel. A meter of rod is 21€. The more common Tr20x4 hex nut is just 7€ and the rod 17€, but 4mm pitch is a bit much for a leadscrew for semi-precision work I reckon.
Well, maybe I just use metric threads. I will sleep on this.
@prologic@twtxt.net That can only work if I happen to have the original one as well. But what are the odds for that? Quite low I’d say. It’s rare that I see a once working thread to be cactus later on. Usually, when I arrive, police already broke up the party. Yarnd might be more lucky in that it constantly pulls, but I don’t.
Anyway, I won’t implement that in my client. Sounds too much effort for the tiny gain.
Ta, @movq@www.uninformativ.de and @bender@twtxt.net! No, that is Wäschenbeuren: https://en.wikipedia.org/wiki/W%C3%A4schenbeuren My town is in the opposite direction.
And yes, it literally took hours to remove 90% of the photos. It’s the necessary evil. I’m never looking forward to the sorting process. The longer the hike, the worse the aftermath.
We had 3°C the other night, quite cold. That’s the price to pay for the nice temperatures at daytime.