# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 6510
# self = https://watcher.sour.is?uri=https://lyse.isobeef.org/twtxt.txt&offset=5234
# next = https://watcher.sour.is?uri=https://lyse.isobeef.org/twtxt.txt&offset=5334
# prev = https://watcher.sour.is?uri=https://lyse.isobeef.org/twtxt.txt&offset=5134
Righto, @prologic, I just checkout out current main of yarnd (commit 5101ec240ddb0e5e39809bf8a7b847508b3ac298) and ran make dev. After registering a user and logging in, I then entered a twt with double bracketed text (without the equal sign on the second one, though) and it was expanded into eight brackets. So, this is clearly a bug. Let me dig deeper.
I hope I zoomed in enough, so you can read the stuff on my screenshot: https://lyse.isobeef.org/tmp/bracketed-text/bug.png
@prologic To clarify, I meant some kind of a cache poisoning attack using the gossipping mechanism to inject garbage on purpose. Not hijacked user accounts.
However, since this all relates to bracketed text, I do not find an attack of some sort very likely. It's probably just a bug somewhere.
@bender This one had me laugh real hard! :'-D Well done, mate.
@prologic Ah, I already forgot that I had a backup user Let's get rid of this guy. :-)
Now, https://twtxt.net/twt/puxvjcq from my original post also works. Yarnd must have parsed it and indexed in the meantime. However, it renders the truncated version of mckinley's message. Notice that it directly ends at the beginning of the bracketed text.
Okay, when I click on on the "Root" link, it brings me to https://twtxt.net/conv/puxvjcq?p=1#7hraijq where both my truncated and full twt are shown. I can 100% guarantee that I did not modify this twt ever. Not sure where the truncated one originates from. Looks like the yarnd twt parser tripped and generated two twts out of this. O_o
@movq Interesting! What the heck!? Is this a bug or feature? I'm now wondering if this bracketed text stuff of corrupted feeds and truncated display are related?
Heck yeah, this water bellows is absolutely amazing! <3 https://youtu.be/M6gYhD6_yLI Now, I want to make one, too, even though I do not have a real use case for this. Very rarely do I light a fire. A simple pipe to blow through would be much more mobile for my occasional need. Still, soooo cool! :-)
@movq You're just incrementally parsing the feed, right? Start off where you ended last time. All (updated) twts from the past are not even looked at, if I remember correctly. So, the missing twt is expected.
Haha, yeah. I also thought a few times that such a utility would be handy. :-)
In fact, all (probably, I did not verify) of @mckinley's square bracketed text twts are now showing up as new twts.
Hmmm, what is going on here? I noticed this a couple of times in the recent past already. Very old twts appear in my client as unread. The pattern seems to be that there is always repeated text in square brackets and some of them contain equal signs. Is yarnd corrupting feeds somehow? I kind of doubt that people actually typed that themselves.
Last time, it was @bender's feed that showed me new weird twts in my client. I don't remember the details, but I'm pretty sure it was this week. Refetching his feed a couple of times (across multiple days) and I got new messages.
And it just happened again, this time with @mckinley's feed. This twt from 2023-01-09T22:42:37Z here newly popped up, it contains magic bracketed text:
> \n I'll bet we could find that information and put "\n\n\n\n\n\n\n\n" in the title for premieres and remove it when the video is available.
Currently, its hash is puxvjcq. There is no sign of evidence that this twt existed ever before. Maybe I'm doing something wrong. But https://twtxt.net/twt/puxvjcq 404s and the search engine also just gives me "error loading twt from archive" (quite a generic error message): https://search.twtxt.net/twt/puxvjcq
Just open https://twtxt.net/user/mckinley/twtxt.txt and search for ][Scheduled or =][ to find even more. This also reveals some "\n\n" stuff. Is that maybe coming from Clownflare?
In https://twtxt.net/user/bender/twtxt.txt it felt to me that the bracketed text from 2024-03-28T18:34:36Z always got duplicated each time it changed for whatever reason: "\n\n" etc.
mckinley and bender, do you recall actually typing that out or somehow updating your feeds on yarnd? Or am I just doing something wrong here? But the fact, that my browser shows the same stuff, I'm pretty sure it's not my client, that's messing things up here.
Any idea, @prologic?
Hmmm, what is going on here? I noticed this a couple of times in the recent past already. Very old twts appear in my client as unread. The pattern seems to be that there is always repeated text in square brackets and some of them contain equal signs. Is yarnd corrupting feeds somehow? I kind of doubt that people actually typed that themselves.
Last time, it was @bender's feed that showed me new weird twts in my client. I don't remember the details, but I'm pretty sure it was this week. Refetching his feed a couple of times (across multiple days) and I got new messages.
And it just happened again, this time with @mckinley's feed. This twt from 2023-01-09T22:42:37Z here newly popped up, it contains magic bracketed text:
> […] I'll bet we could find that information and put "[Scheduled][Scheduled][Scheduled][Scheduled][Scheduled][Scheduled][Scheduled][Scheduled]" in the title for premieres and remove it when the video is available.
Currently, its hash is puxvjcq. There is no sign of evidence that this twt existed ever before. Maybe I'm doing something wrong. But https://twtxt.net/twt/puxvjcq 404s and the search engine also just gives me "error loading twt from archive" (quite a generic error message): https://search.twtxt.net/twt/puxvjcq
Just open https://twtxt.net/user/mckinley/twtxt.txt and search for ][Scheduled or =][ to find even more. This also reveals some "[email protected][email protected]" stuff. Is that maybe coming from Clownflare?
In https://twtxt.net/user/bender/twtxt.txt it felt to me that the bracketed text from 2024-03-28T18:34:36Z always got duplicated each time it changed for whatever reason: "[162.159.205.11][162.159.205.11]" etc.
mckinley and bender, do you recall actually typing that out or somehow updating your feeds on yarnd? Or am I just doing something wrong here? But the fact, that my browser shows the same stuff, I'm pretty sure it's not my client, that's messing things up here.
Any idea, @prologic?
Hmmm, what is going on here? I noticed this a couple of times in the recent past already. Very old twts appear in my client as unread. The pattern seems to be that there is always repeated text in square brackets and some of them contain equal signs. Is yarnd corrupting feeds somehow? I kind of doubt that people actually typed that themselves.
Last time, it was @bender's feed that showed me new weird twts in my client. I don't remember the details, but I'm pretty sure it was this week. Refetching his feed a couple of times (across multiple days) and I got new messages.
And it just happened again, this time with @mckinley's feed. This twt from 2023-01-09T22:42:37Z here newly popped up, it contains magic bracketed text:
> […] I'll bet we could find that information and put "[Scheduled]\n[Scheduled]\n[Scheduled]\n[Scheduled]\n" in the title for premieres and remove it when the video is available.
Currently, its hash is puxvjcq. There is no sign of evidence that this twt existed ever before. Maybe I'm doing something wrong. But https://twtxt.net/twt/puxvjcq 404s and the search engine also just gives me "error loading twt from archive" (quite a generic error message): https://search.twtxt.net/twt/puxvjcq
Just open https://twtxt.net/user/mckinley/twtxt.txt and search for ][Scheduled or =][ to find even more. This also reveals some "[email protected]\n" stuff. Is that maybe coming from Clownflare?
In https://twtxt.net/user/bender/twtxt.txt it felt to me that the bracketed text from 2024-03-28T18:34:36Z always got duplicated each time it changed for whatever reason: "[162.159.205.11]\n" etc.
mckinley and bender, do you recall actually typing that out or somehow updating your feeds on yarnd? Or am I just doing something wrong here? But the fact, that my browser shows the same stuff, I'm pretty sure it's not my client, that's messing things up here.
Any idea, @prologic?
Hmmm, what is going on here? I noticed this a couple of times in the recent past already. Very old twts appear in my client as unread. The pattern seems to be that there is always repeated text in square brackets and some of them contain equal signs. Is yarnd corrupting feeds somehow? I kind of doubt that people actually typed that themselves.
Last time, it was @bender's feed that showed me new weird twts in my client. I don't remember the details, but I'm pretty sure it was this week. Refetching his feed a couple of times (across multiple days) and I got new messages.
And it just happened again, this time with @mckinley's feed. This twt from 2023-01-09T22:42:37Z here newly popped up, it contains magic bracketed text:
> […] I'll bet we could find that information and put "[Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=]" in the title for premieres and remove it when the video is available.
Currently, its hash is puxvjcq. There is no sign of evidence that this twt existed ever before. Maybe I'm doing something wrong. But https://twtxt.net/twt/puxvjcq 404s and the search engine also just gives me "error loading twt from archive" (quite a generic error message): https://search.twtxt.net/twt/puxvjcq
Just open https://twtxt.net/user/mckinley/twtxt.txt and search for ][Scheduled or =][ to find even more. This also reveals some "[email protected][email protected=]" stuff. Is that maybe coming from Clownflare?
In https://twtxt.net/user/bender/twtxt.txt it felt to me that the bracketed text from 2024-03-28T18:34:36Z always got duplicated each time it changed for whatever reason: "[162.159.205.11][162.159.205.11=]" etc.
mckinley and bender, do you recall actually typing that out or somehow updating your feeds on yarnd? Or am I just doing something wrong here? But the fact, that my browser shows the same stuff, I'm pretty sure it's not my client, that's messing things up here.
Any idea, @prologic?
My wood glue rarely leaves me hanging. But today was that day again. Before lunch, I cut a slat of a slatted frame in half and glued it together. The two banana shapes were facing each other like two parentheses "()". This made it straight.
After 3-4 hours, I unclamped it and handplaned it to its final shape, so it can become the last rung of my "ladder" for the laundry shelf. Yeah, I'm still on that project over half a year later. You can call me a really lazy ass. ;-)
When I was about to round over the long edges with my handplane, the bananas suddenly came apart. Both ends still held, so I had some kind of an "O". The glue had not fully set yet. It was still a tiny bit moist in the inside. I scraped off the leftovers with a chisel. To increase my odds the second time, I roughed up the surfaces with 40 grit sandpaper and a rasp, so that the glue has something to bite into. Didn't do that the first time. I reckon that majorly contributed to the fail, because the boards were fairly smooth, maybe even coated with something, who knows. Any kind of finish is bad for glueing.
Now, I'm also using a few more clamps and let it sit over night. Well, two days in fact, since I cannot bang around tomorrow. Unfortunately, I can't finish this frame/ladder today. But maybe on Monday.
Usually, I let wood glue set at least over night, even though a couple of hours should™ suffice I'm told. I will definitely go back to that regular setting period. Especially when mechanical forces are working against me and there is stress in the wood. Never can go wrong with a longer waiting time. I have always had good experience with this in the past. In fact, whenver the wood glue failed on me, it was either removing the clamps too early or a sloppy glueing surface preparation. Or both. ;-)
Wow, time really flies. I just rotated February to May 2024 into archive feeds. So my main twtxt feed now contains only the last three full months and a little bit again.
@movq Yeah, what a silly driver.
Dragonflies do really look great! This one was really huge, its body length was at least 10-12 cm I'd say. It was trapped at the kitchen tent addition. They always try to leave by going up, but almost never down (this usually works out in nature without manmade structures). After 5-10 min of struggle I carefully helped it escape using a cooking spoon from the dishwashing pile.
@prologic I heard in football they like to fire the trainer in these sitations. :-D Worry not, it's the taking part that counts. :-)
@movq Ha, nice! Looks like it's guarding this tree for quite some time now. @prologic It's maybe a moss feather owl. :'-D Somebody placed this owl statue in the forest, it's not a real one.
@prologic Yeah, it's always great fun. Haha, they definitely prefer roof balconies.
@prologic Sometimes you lose, sometimes the others win. :-D In any case, enjoy!
@prologic Twelve hours might be a bit short. On the other side, when people have not even logged in for I don't know how much time, it may not even matter all that much.
Phew, @iolfree! Great that one can do these kind of experiments in a safe environment. :-)
You're getting there, @stigatle, this looks nice. :-)
@iolfree Oh crap, I hope this did not end in a crash or something. :-O
@prologic @movq Both feeds often result in 503 or connection refused for me as well. But at the moment, they're fine.
@stigatle Congrats, mate! That's a funny story. :-) Enjoy your day of glory!
@stigatle @movq Yeah, that was nice, just 22°C at the moment. But earlier it reached 26°C. The next thunderstorm is forecast for the evening. Yesterday, I could only hear thunder in the distance, it never reached us. Might be different today.
Oh, the lovely smell of rain. Wonderful! 33°C today, yikes! And I can already hear the thunder rolling in.
@thecanine Step 1: Uninstall it. Step 2: Success! :-D
@bender Ah, thank you! <3 So, 14:00 UTC+2 might work out.
Heck yeah! I saw my first slow worm this year. Very cool. :-) We also came across some art in the woods. Surprisingly, the blackberries in the forest were mellower than the ones on the south side bushes with sun exposure all day long.
Blackberries
@prologic I will try. Which time was it again?
The search engine is broken:
> Error error parsing created field: parsing time "1689093798000000000" as "2006-01-02T15:04:05Z07:00": cannot parse "093798000000000" as "-"
@movq Ah, I did not have a portable diskman. Just a stationary radio with an integrated CD player. Or my parent's stereo. But it's sooo long ago, I can't remember how long switching tracks took. Yeah, on second thought, maybe a second. Well, that actually improved then. Finally. Nice. :-) Loading the CD took several seconds, that's for sure. And some devices were certainly slower than others.
@movq @bender Thanks, mates. I was on the fence with 13 and 15. :-)
@movq There's a big difference between being usable somehow and having fun using it. My tolerable limits are lower, but yeah. Up to five seconds for the "next track"? What music player are you using? :-D This must happen in way under a second, and luckily, this works here. :-) (But I'm also not streaming my music, it's all on the local disk.)
@abucci Can you please check if you reported @xuu's IP address 162.211.155.2 on mistake and let his ISP know that this was some false alarm? They're monitoring his traffic to your server and treating this as continued abuse. :-(
(His twts have been synced to your yarnd by yarnd's gossip protocol.)
@abucci Just making sure you're seeing @xuu's twt, in case he's still on your blacklist:
> Hey so.. i just got an email from my ISP saying they will terminate my service. Did i break something @abucci ?
>
> – https://txt.sour.is/twt/oohzbqa
@movq My issue is, now that we have the chance of getting something fast, people artificially slow it down again. Wether they think it's cool that they added some slow animation or just lack of knowledge or whatever. The absolute performance does not translate to the relative performance that I observe. Completely wasted potential. :-(
In today's economy, nobody optimizes something if it can be just called good enough with the next generation hardware. That's especially the mindset of big coorporations.
Anyway, getting sidetracked from the original post. :-)
@prologic Yup. Didn't regret climbing these three hundred odd meters of elevation. :-)
@stigatle Worky, worky now! :-)
Mate, these are some really nice gems! What a stunning landscape. I love it. Holy cow, that wooden church looks really sick. Even though, I'm not a scroll guy and prefer simple, straight designs, I have to say, that the interior craftmanship is something to admire.
@stigatle Welcome back! I don't know what's going on, but all the photos fail to load for me. Wget reports decoding errors for the received TLS packets. :-?
Went for a walk onto my backyard mountain again and ate the first three wild blackberries of the season. Watching the sunset unfold from the summit was quite spectacular. The solar disk was glowing extremely blood red. The photos show it way too white, though.
Blood red sunset
More: https://lyse.isobeef.org/waldspaziergang-2024-07-24/
@movq It's fascinating how people always find ways to completely waste all gained resource improvements and speedups and beyond, so every new and more powerful computer actually feels like a big step backwards. :-( The web shit is particularly terrible.
@prologic I reckon, it's just so that they can say: "Oh, whoopsy daisy. Too bad that you fell for our trap. Sorry, it's entirely your own fault. Go away, leave us alone."
The bullet point 8.6 continues right away (I forgot the ellipsis in my initial quote, excuse me):
> \n Customer agrees that it is Customer’s responsibility to ensure safe use of an Offering and the CrowdStrike Tools in such applications and installations. CROWDSTRIKE DOES NOT WARRANT ANY THIRD PARTY PRODUCTS OR SERVICES.
And in the one before that:
> 8.5 No Guarantee. CUSTOMER ACKNOWLEDGES, UNDERSTANDS, AND AGREES THAT CROWDSTRIKE DOES NOT GUARANTEE OR WARRANT THAT IT WILL FIND, LOCATE, OR DISCOVER ALL OF CUSTOMER’S OR ITS AFFILIATES’ SYSTEM THREATS, VULNERABILITIES, MALWARE, AND MALICIOUS SOFTWARE, AND CUSTOMER AND ITS AFFILIATES WILL NOT HOLD CROWDSTRIKE RESPONSIBLE THEREFOR.
In other words: "Just give us your money and hope for the best. It might work. Maybe." Nope, of course it doesn't.
@prologic I reckon, it's just so that they can say: "Oh, whoopsy daisy. Too bad that you fell for our trap. Sorry, it's entirely your own fault. Go away, leave us alone."
The bullet point 8.6 continues right away (I forgot the ellipsis in my initial quote, excuse me):
> […] Customer agrees that it is Customer’s responsibility to ensure safe use of an Offering and the CrowdStrike Tools in such applications and installations. CROWDSTRIKE DOES NOT WARRANT ANY THIRD PARTY PRODUCTS OR SERVICES.
And in the one before that:
> 8.5 No Guarantee. CUSTOMER ACKNOWLEDGES, UNDERSTANDS, AND AGREES THAT CROWDSTRIKE DOES NOT GUARANTEE OR WARRANT THAT IT WILL FIND, LOCATE, OR DISCOVER ALL OF CUSTOMER’S OR ITS AFFILIATES’ SYSTEM THREATS, VULNERABILITIES, MALWARE, AND MALICIOUS SOFTWARE, AND CUSTOMER AND ITS AFFILIATES WILL NOT HOLD CROWDSTRIKE RESPONSIBLE THEREFOR.
In other words: "Just give us your money and hope for the best. It might work. Maybe." Nope, of course it doesn't.
Thanks, @aelaraji! :-) I nearly missed it, because the shutters are closed to keep the heat out.
@movq What a pity for all the effort!
It's also funny to read their terms and conditions:
> 8.6 \n THE OFFERINGS AND CROWDSTRIKE TOOLS ARE NOT FAULT-TOLERANT AND ARE NOT DESIGNED OR INTENDED FOR USE IN ANY HAZARDOUS ENVIRONMENT REQUIRING FAIL-SAFE PERFORMANCE OR OPERATION. NEITHER THE OFFERINGS NOR CROWDSTRIKE TOOLS ARE FOR USE IN THE OPERATION OF AIRCRAFT NAVIGATION, NUCLEAR FACILITIES, COMMUNICATION SYSTEMS, WEAPONS SYSTEMS, DIRECT OR INDIRECT LIFE-SUPPORT SYSTEMS, AIR TRAFFIC CONTROL, OR ANY APPLICATION OR INSTALLATION WHERE FAILURE COULD RESULT IN DEATH, SEVERE PHYSICAL INJURY, OR PROPERTY DAMAGE.
That's why all airports remained operational. Oh wait…
It's also funny to read their terms and conditions:
> 8.6 […] THE OFFERINGS AND CROWDSTRIKE TOOLS ARE NOT FAULT-TOLERANT AND ARE NOT DESIGNED OR INTENDED FOR USE IN ANY HAZARDOUS ENVIRONMENT REQUIRING FAIL-SAFE PERFORMANCE OR OPERATION. NEITHER THE OFFERINGS NOR CROWDSTRIKE TOOLS ARE FOR USE IN THE OPERATION OF AIRCRAFT NAVIGATION, NUCLEAR FACILITIES, COMMUNICATION SYSTEMS, WEAPONS SYSTEMS, DIRECT OR INDIRECT LIFE-SUPPORT SYSTEMS, AIR TRAFFIC CONTROL, OR ANY APPLICATION OR INSTALLATION WHERE FAILURE COULD RESULT IN DEATH, SEVERE PHYSICAL INJURY, OR PROPERTY DAMAGE.
That's why all airports remained operational. Oh wait…
@movq No, no, not snarky at all. That's just their Aussie name. :-)
@prologic Right, I hate it. I'd stick to regular pagination and page sizes that are reasonable large. But if you think another approach is better, go for it. It's your sofware after all.
Ah, thanks, @bender! Yeah, that combines the disadvantages of both approaches and successfully throws away the advantages. I actually know at least two webshops with that terrible UI.
@prologic Just look at their website. Yesterday, there was this quote, it's already gone by now:
> Cybersecurity’s AI-native platform for the XDR era
Mo-mo-mo-monster bingo!
Someone archived this screnshot, that I've also seen yesterday: https://assets.chaos.social/cache/media_attachments/files/112/812/257/953/926/994/original/c9de6459751f2ebf.png „Your company can be ruined in just 62 minutes“ Luckily, ClownStrike can shorten this timeframe even more. :-D
@movq I hope all admins can at least tell management: Told you so! But of course, no manager gets fired for their bloody stupid decision.
@xuu We got several e-mails about this whole desaster at work.
@prologic I do not like infinite scroll at all. I think it is an anti-pattern. It doesn't let me quickly jump ahead. Pagination is superior in that regard.
@prologic @movq Haha, didn't affect me or my direct workmates either. But our scrummie logged off with BSOD and another workmate also told me to have already experienced three with successful reboots, though. Another branch was completely offline and I heard rumors about factories being shut down, too.
Anyone who reads the CrowdStrike self-description and then buys the product has really earned a major fault.
This is exactly what's going to happen, movq. Zero lessons learned. No consequences. Maybe just a bit more snake oil on top.
@movq Yeah, I don't get it either. Some "security" scanner at work also complains about "dead" libraries all the time, just because the most recent commit is a few years or even just months old. What a giant joke.
This mindset _might_ come from today's kids who can build stuff only with gazillions of dependencies. And plenty of these suck, are full of bugs, vulnerabilities and bad code in general. So they have to be patched constantly. If one is always surrounded by that, it just feels normal. One might even come to the conclusion that it simply has to naturally be that way. And then, the incorrect deduction is that the project is abandoned, once there are no new commits in a week. It maybe doesn't occur to these people that it is actually possible to work out differently.
To be fair, there is also a lot of unfinished and truly dead code out there. So that assures their theory even further, once they stumble across one of those projects.
And the same doesn't only happen to private projects. All enterprise software systems also pull in so much stuff, that there is always something to update.
The lack of proper planning, just building and delivering buggy banana software in cycles and the mindset of shipping fast and often and doing things agile in general does not do this any favor. It just feels like today's sofware is never ever finished. And if it finally reaches such a point, it must be dead.
I know of some otherwise reeeeaaaaally great software developers who also think that way. I don't understand why they disagree with us here. :-?
@movq Why would that be surprising? :-) They definitely fit my style of music. Well, I don't wanna know how much a ticket is. And the Wasen is also a terrible location. :-D
The overcrowded train was run by GoAhead, the S-Bahn by DB. They're interchangeably bad.
Over fifty kilometers is a very long bike ride. That at least doubles my commute to more than six hours in total. No, thanks. ;-)
@movq It requires heaps of discipline. Lots of.
@movq @prologic Good analysis! Another aspect is: Trying out new stuff is appealing to a lot of people. I'm certainly not unguilty of that either. But when you experiment, things will naturally go wrong somewhere at some point. You probably don't even know that at this point in time and realize this only much later. If at all.
To make it better, throwing things away and starting over with the newly aquired knowledge would be the right thing to do. But that doesn't happen for a myriad of reasons. So you ended up with overly complex stuff.
A bit like building a prototype and keeping it alive forever. "Denn nichts hält länger als ein Provisorium." – "Nothing is more definitive than the temporary."
Then there comes in feature creep. And preliminary optim^Wfeatures, "hey, maybe somebody would like to bla in the future, let's add this".
I just heard AC/DC play live in Stuttgart-Bad Cannstatt for the first time in my life!
Well, when I was waiting for my train home on the station platform. I didn't recognize that it was Acca Dacca, and I tried hard. In fact, the stage was 500 meters away, so it was just some music-like sound that found its way into my ears. Still kinda cool to know that I heard them live.
I had a barbie with my old workmates. That's why I have a story to tell now. On the way there, the train was hopelessly overcrowded with AC/DC fans. You couldn't fall down, simply impossible. It was like in the videos of Japanese subways, where guards press in passengers to utilize every square centimeter. At later stations, plenty of people didn't get in. Not a chance. This caused quite some delays. And boy, was it hot in there. Streams of sweat running down everywhere.
Originally, I wanted to meet up with a workmate in a city train for the second part of the trip. Due to a signal failure, his train was delayed, though. It got delayed even more and more and was finally cancelled altogether. I eventually got my connecting train while he was still stuck and decided to abort mission and go home after 40 minutes. Catching my connection was another adventure. It was rerouted to another platform, of course without announcement. Because why would you? Fuck the passengers! Luckily, I noticed that it took a different branch at the switch on arrival and ran down and up the stairs to the other platform. The delay counter in this train showed 40 minutes when I finally got off.
With the exception of Acca Dacca, the way home was pleasantly uneventful. Just a few minutes delay and a relatively low passenger volume.
I'm so grateful for not having to experience all this shit on a daily basis anymore. Not looking forward to the next time I have to go into the city. Not at all.
@prologic Haha, no, I meant something work-related. ;-)
But you're right, yarnd has potential for improvement, too (what doesn't?). Rest assured, there are several universes between the two. And yarnd is lightyears ahead.
@movq Oh dear, people who have to always get an answer immediately have all sorts of issues. :-( They're dead losses.
I will not use WhatsApp in a million years. It's not worth it. Might be trickier with family members, but I also refuse to use such stuff. It definitely degrades some friends to aquaintances, but oh well. If I don't know what I'm "missing out" on, then I simply cannot miss it. On the positive side, it frees my time for other things. :-)
@movq @prologic Just slowly creating software is not enough. It doesn't cut it. The focus has to be on quality. I see suuuper slow progress in a project, but the quality still totally sucks balls.
@movq Yeah, my software is definitely completely irrelevant to everyone else.
I don't send my bank or insurance company any bug report e-mails or the like. I'm talking about mailing software developers or projects. On a side note, though, I've seen lot of (German) companies use GMail & other terrible mail providers. My former employer fell also in this category (so does my current one, but at least I receive all e-mails).
@prologic Haha, we're already in summer. :-)
@movq No, both are a manmade lakes and ponds, but the fish are real. :-) In fact, the fish are in the much smaller "tadpole pond" as I call it. The tadpoles are now all gone and we've seen tiiiiiny frogs jumping around. But we were not successful in capturing them on film. Maybe fish were brought in these artificial lakes by mankind, too, I don't know. Good question.
@movq @prologic Maybe your softwares are just perfect and there are simply no bug reports and contributions required. :-)
I reckon if someone really wanted to participate, they will. Despite where it is hosted.
I just also see the issue with smaller mail servers being blocked by the large ones. This also happened to me I believe. My mails just never made it to the people. Or they were ignored, I cannot tell.
@movq Yikes, true! The hail covered road looks super sick. I'm very glad living in my area.
@movq Having juggled all the low level bits makes one also appreciate higher level languages. At least that's my own experience.
By the way, @xuu, it looks like you're running an old, buggy version of yarnd, that duplicates twts in the feed on edit.
@xuu @bender Yeah, we're quite lucky with this very, very wet summer this year. It's supposed to be just 21°C today, good hiking conditions. Some nice 16°C to cool off the house right now, I love it. Tomorrow, temps are rising again, though.
The 26°C humidity was through the roof and we just barely escaped the thunderstorm on our stroll. Only the adjacent rain hit us hard. Black clouds caught up on us and we decided to take cover at a barn. Not even a minute later it started to rain cats and dogs for ten minutes straight. Holy crap, that was cool to watch. :-) Also, the smell of rain was just beautiful.
We then decided to continue our return in the light drizzle. But it then got much heavier again and we got completely soaked. With the wet t-shirt and the wind it actually felt rather cold. I anticipated to get rained on, so I left my camera at home. Plenty of paths turned into brook landscapes, several centimeter deep creeks ran down the hilly trails. Quite fascinating. :-)
The sunset a few minutes ago wasn't too bad:
Sunset
@prologic Haha, didn't expect that from the introduction. :-D
@prologic Your message got a bit mangled up I reckon, not sure if I understand it. I don't find these lists hard to read. The question is more, which of the standards do you follow? I doubt that another package really helps a lot. I mean, one can just use the codes already if one wanted to.
@shreyan Hell yeah, that looks great! I love it. :-) Where is this?
@movq And all of a sudden, a week has passed. :-D Hahaha, I know. Let's *quickly* finish this tiny thing here…
@movq Yeah, the "Vernichter" is a pretty violent word. ;-) Oh, you have one? I don't know when I last used a shredder. Must have been when I was a kid. Hm, what do you shred? Unwanted invoices? :'-D
Oh, this is interesting! Reading the Crafting Interpreters book, I came across a table of exit codes in FreeBSD.
I didn't know that a command line usage error is supposed to report exit code 64. In the past I either simply exited with 1 or sometimes each exit statement got its own dedicated number. The latter came in useful for debugging shell scripts. I exactly knew which branch was executed. That was handy when the error messages were similar or even the same.
I was always wondering if there is some kind of a standard, but I never did my reasearch. Looking at other people's code, it always seemed to me that everybody just did wantever they wanted to in regards to exit codes. I just looked up what else is out there and systemd also defines heaps of errors. It even references the FreeBSD one and links to the Linux Standard Base specification, too. Cool, cool!
Do you guys know of these conventions and make use of them?
Hahaha, @bender! Watching some YouTubers I get the impression that this is even legal in Utah. :-D
@movq Oh wow, couple of days!? You're *very* passionate about that. ;-) Respect, reverse-engineering this sort of thing is waaay beyond my capabilities. This sort of stuff is too low-level for me.
@movq I like the term "Reißwolf". But I have to admit, there are not a lot of opportunities to actually use it. Do you think this word has been superseded by "Schredder"? Or even "Aktenvernichter"? :-D
Hahaha, @movq:
> And then be very thankful that we don’t have to deal with this anymore today. 😂
That's exactly what I thought when reading your explanations. :-D
Dragonfly
Sunset
Blackbird on a ridge with a slightly colored sky in the background
Three butterflies