"[Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=]"
2023-01-09T22:42:37Z (#dusjj6a) @<lyse https://lyse.isobeef.org/twtxt.txt> As far as I know, they're still visible in the Web UI. Although, in the mobile app and youtube.com, I believe it tells you that the video isn't available without having to click on it. They don't tell you that in the RSS feed, and I agree; it gets annoying.
If we had a custom feed generator that hooks directly into the YouTube API, 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.
And I have no fucking clue how this happened. I can't imagine anything in the
yarnd codebase would be responsible for this weirdness 🤣
2023-01-09T22:42:37Z (#dusjj6a) @<lyse https://lyse.isobeef.org/twtxt.txt> As far as I know, they're still visible in the Web UI. Although, in the mobile app and youtube.com, I believe it tells you that the video isn't available without having to click on it. They don't tell you that in the RSS feed, and I agree; it gets annoying.
If we had a custom feed generator that hooks directly into the YouTube API, 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.
And I have no fucking clue how this happened. I can't imagine anything in the
yarnd codebase would be responsible for this weirdness 🤣
2023-01-09T22:42:37Z\t(#dusjj6a) @<lyse https://lyse.isobeef.org/twtxt.txt> As far as I know, they're still visible in the Web UI. Although, in the mobile app and youtube.com, I believe it tells you that the video isn't available without having to click on it. They don't tell you that in the RSS feed, and I agree; it gets annoying.
If we had a custom feed generator that hooks directly into the YouTube API, 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.
And I have no fucking clue how this happened. I can't imagine anything in the
yarnd codebase would be responsible for this weirdness 🤣
bsormva is not a hash found in @lyse 's feed at all according to yarnc debug which is printing the hash and corresponding Twt per line.
bsormva is not a hash found in @lyse 's feed at all according to yarnc debug which is printing the hash and corresponding Twt per line.
ta6uu5q 2024-08-03T19:30:00+02:00 (#puxvjcq) Hmmm, what is going on here? ...
ta6uu5q 2024-08-03T19:30:00+02:00 (#puxvjcq) Hmmm, what is going on here? ...
ta6uu5q 2024-08-03T19:30:00+02:00\t(#puxvjcq) Hmmm, what is going on here? ...
yarnc debug <url> only sees the 2nd hash 
yarnc debug <url> only sees the 2nd hash
$ 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
$ 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
$ diff <(bat https://twtxt.net/twt/7hraijq | jq '.') <(bat https://twtxt.net/twt/ta6uu5q | jq '.')
10c10
< "hash": "7hraijq",
---
> "hash": "ta6uu5q",
$ diff <(bat https://twtxt.net/twt/7hraijq | jq '.') <(bat https://twtxt.net/twt/ta6uu5q | jq '.')
10c10
< "hash": "7hraijq",
---
> "hash": "ta6uu5q",
$ 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)
$ 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)
$ diff -Ndru <(bat https://twtxt.net/twt/7hraijq | jq -r '.text') <(bat https://twtxt.net/twt/ta6uu5q | jq -r '.text') | wc -l
0
$ diff -Ndru <(bat https://twtxt.net/twt/7hraijq | jq -r '.text') <(bat https://twtxt.net/twt/ta6uu5q | jq -r '.text') | wc -l
0
https://twtxt.net/twt/7hraijq
https://twtxt.net/twt/ta6uu5q
@Lyse the pop up shows up, but when I tap on it, it just autocompletes as @lyse@, nothing else.I am on mobile.
https://movq.de/v/7cb8a3bad4/huh2.png
https://movq.de/v/7cb8a3bad4/huh2.png
https://movq.de/v/7cb8a3bad4/huh2.png
https://movq.de/v/7cb8a3bad4/huh2.png
Haha, yeah. I also thought a few times that such a utility would be handy. :-)
(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.)
(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.)
(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.)
(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.)
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/puxvjcqJust 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?
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/puxvjcqJust 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?
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/puxvjcqJust 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?
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/puxvjcqJust 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?
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. ;-)
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.