Computers aren’t meant to give me three different answers 🤣

@movq@www.uninformativ.de / @lyse@lyse.isobeef.org / @xuu any ideas wut da fuq is going on here?! 🤣

In fact I cannot produce eitehr of these hashes:

$ pbpaste | ./yarnc hash -u https://lyse.isobeef.org/twtxt.txt -t 2024-08-03T19:30:00+02:00 -
bsormva

What da fuq?!

$ bat https://twtxt.net/twt/7hraijq | jq -r '.text' | ./yarnc hash -u https://lyse.isobeef.org/twtxt.txt -t 2024-08-03T19:30:00+02:00 -
bsormva

Yeah, this looks like a hash collision to me right? Same twt, same timestamp, same twter, produces two different hashes? I’m not even sure how da fuq this is even possible?

$ diff <(bat https://twtxt.net/twt/7hraijq | jq '.') <(bat https://twtxt.net/twt/ta6uu5q | jq '.')
10c10
<   "hash": "7hraijq",
---
>   "hash": "ta6uu5q",

@lyse@lyse.isobeef.org (ahh auto-complete is broken only on Mobile?) @xuu is our hashing reached a point where it’s broken and needs to be dumped? 🤔

What da actual fuq?! They have the same timestamp too!

$ bat https://twtxt.net/twt/7hraijq | jq '.created'
"2024-08-03T19:30:00+02:00"
$ bat https://twtxt.net/twt/ta6uu5q | jq '.created'
"2024-08-03T19:30:00+02:00"

And the same Twter (URI)

Hm mm these are identical in content:

$ diff -Ndru <(bat https://twtxt.net/twt/7hraijq | jq -r '.text') <(bat https://twtxt.net/twt/ta6uu5q | jq -r '.text') | wc -l
0

@bender@twtxt.net Shy are those seem like dupes with different hashes?

See:

https://twtxt.net/twt/7hraijq
https://twtxt.net/twt/ta6uu5q

Nope none that I can think of 🤔

Yeah okay I can reproduce that weird auto-complete bug

Hmm like @lyse@lyse.isobeef.org

Hmm I’m not sure either 🤔

Yeah, truly weird and odd behaviour.

@mckinley@twtxt.net I also see repeated Lyse twtxts, and I can’t even mention him on this twtxt. When I type @Lyse the pop up shows up, but when I tap on it, it just autocompletes as @lyse@, nothing else.

I am on mobile.

@lyse@lyse.isobeef.org nope. That’s all Yarn’s doing. 😳😬

Definitely something going on here. Cloudflare is my main suspect.

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@www.uninformativ.de 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?

You twt is truncated on twtxt.net, btw. 🤔

https://movq.de/v/7cb8a3bad4/huh2.png

@lyse@lyse.isobeef.org Yeah, jenny ignores twts that are older than the last timestamps it saw. In other words, it certainly looks like feed corruption on Yarn’s end. 🤔

Heck yeah, this water bellows is absolutely amazing! 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@www.uninformativ.de 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. :-)

@lyse@lyse.isobeef.org puxvjcq certainly does not exist in my cache.

(I feel the need to implement jenny --debugfeed <url> now which just fetches a URL and prints <hash> <original_line> for the raw feed. Could have used this a couple of times already.)

In fact, all (probably, I did not verify) of @mckinley@twtxt.net’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@twtxt.net’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@twtxt.net’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@twtxt.net?

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@twtxt.net’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@twtxt.net’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@twtxt.net?

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. ;-)

@prologic@twtxt.net I thought you were one of the people telling me how great it was. It is a Go project, after all. What do you usually use? I always find myself spending a lot of time making Nginx do what I want and I don’t think I’ve ever had automatic certificate renewal work the first time.

Caddy just works. I have some self-hosted Web services with easy-to-remember subdomains that only exist on my Wireguard network with a valid Let’s Encrypt (wildcard) certificate so browsers don’t complain. It should be automatically renewed without my input but we’ll see what happens. It took shockingly little effort, even considering I need to customize the Docker image and create API keys so it can solve a DNS challenge using my provider.

I’m still not thrilled about using software that does magic for you (like Docker and Caddy) but it sure makes things easy.

@lyse@lyse.isobeef.org will be fixed, thanks!

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.

@prologic@twtxt.net Well, in that case. :-D

@movq@www.uninformativ.de 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.

I’ve been tricked! 🤣

@lyse@lyse.isobeef.org Of! It’s not real?! 😱

@prologic@twtxt.net I heard in football they like to fire the trainer in these sitations. :-D Worry not, it’s the taking part that counts. :-)

@movq@www.uninformativ.de Ha, nice! Looks like it’s guarding this tree for quite some time now. @prologic@twtxt.net It’s maybe a moss feather owl. :‘-D Somebody placed this owl statue in the forest, it’s not a real one.

@movq@www.uninformativ.de I think you’re mistaking expectations for quality software 🤣 When have you ever seen quality software out of an enterprise? 😅

@movq@www.uninformativ.de Bahahaha 🤣

@prologic@twtxt.net God, no. 😂 That’s builtin. I just have to figure out how to link against the correct DLL. 🥴

@prologic@twtxt.net Yeah, call me naive. If they offer a web client, I’d expect it to be at least usable? Why does this even exist?

@movq@www.uninformativ.de So you gotta write your own TCP/IP stack right? 😅 Did that for an undergrad uni assignment, how hard can it. be 🤣

@movq@www.uninformativ.de Oh wow that’s a nice shot! 👌 Don’t think I’ve ever seen an Owl like this! What species of owl is it? 🤔

@movq@www.uninformativ.de And you thought it would be what exactly? 🤔 This is Meta we’re talking about 🤣

I’m experimenting with WhatsApp at the moment and it’s worse than I expected. 😳 There is https://web.whatsapp.com/ which you can use on a normal PC without constantly having the app running/installed on your phone. That was tempting. But … you can’t really do anything here. You can’t even initiate new chats to another phone number. It looks like this only works if you give the app on your phone access to your contact list – a total asshole move.

Fuck this. ☹️

Saw an “owl” in the woods today: https://movq.de/v/a7c2130c18/IMG_20240803_094845.jpg.jpg

@lyse@lyse.isobeef.org lol, the parking cars. 😂

Dragonflys are pretty awesome. Huge but chill guys. 🏖️

@prologic@twtxt.net Gotta figure out how to do TCP/IP on OS/2, first. 😂

@lyse@lyse.isobeef.org Well we lost all three rounds 🤣 6-1 6-1 7-0 😱