@movq@www.uninformativ.de Und nicht behebt. Schlag ich morgen mal unserem Auftraggeber vor. 8->
@movq@www.uninformativ.de Yup, I think thatās my favorite season.
I do not notice any lag with my Logitech Lift. Havenāt changed the inital battery from July last year yet. I have to say Iām rather impressed. The only reason for this cordless mouse is that I havenāt found a vertical mouse with a tail. Otherwise, Iād 100% taken that.
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 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!
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. 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 Yep, certainly not a larger city, just a ~20k town.
@thecanine 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 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-)