It happens to each bracketed text individually: https://lyse.isobeef.org/tmp/bracketed-text/triple.png
But then the question still is, why on earth does it happen to old twts, too? I'm getting into my code excavator.
It happens to each bracketed text individually: https://lyse.isobeef.org/tmp/bracketed-text/triple.png
But then the question still is, why on earth does it happen to old twts, too? I'm getting into my code excavator.
2024-08-04T21:22:05+10:00\t[foo][foo=][foo][foo=]
2024-08-04T21:22:05+10:00 [foo][foo=][foo][foo=]
2024-08-04T21:22:05+10:00 [foo][foo=][foo][foo=]
[foo] and ended up with [foo][foo=][foo][foo=] wut da actual fuq?! 🤔
[foo] and ended up with [foo][foo=][foo][foo=] wut da actual fuq?! 🤔
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
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.
I just set up a cronjob to fetch and analyze both feeds every six hours. I probably have to do some dedup, otherwise the list gets out of handy rather quickly.
> How do the feeds look on disk? Do they already contain this bracketed text?
Because the handle just serves the Twtxt file directly.
> How do the feeds look on disk? Do they already contain this bracketed text?
Because the handle just serves the Twtxt file directly.
was hoping for a breeze or some rain from this tropical depression "debbie" but saw none of that until i had stopped. broke it up in 4 mile blocks and walked a bit to regain composure/heart rate. had some at the end with speed. funny how the only people i saw out today were runners.
#running
was hoping for a breeze or some rain from this tropical depression "debbie" but saw none of that until i had stopped. broke it up in 4 mile blocks and walked a bit to regain composure/heart rate. had some at the end with speed. funny how the only people i saw out today were runners.
#running
was hoping for a breeze or some rain from this tropical depression "debbie" but saw none of that until i had stopped. broke it up in 4 mile blocks and walked a bit to regain composure/heart rate. had some at the end with speed. funny how the only people i saw out today were runners.
#running
How do the feeds look on disk? Do they already contain this bracketed text?
For reference, I just placed a copy of the feed here: https://lyse.isobeef.org/tmp/bracketed-text/bender-2024-08-04-10-34.txt
I haven't marked the changed twts by @mckinley as read last time, so I don't know if something changed there as well. In any case, current snapshot: https://lyse.isobeef.org/tmp/bracketed-text/mckinley-2024-08-04-10-39.txt
Yarnd gossipping might be the reason for the truncated stuff, @prologic. Who are your peers? Any obvious broken yarnd version or even some kind of an attacker involved? But there must be something else broken in yarnd for the bracketed text to be duplicated.
I could not reproduce this by manually duplicating those text areas in lyse’s twt. I end up with the hash
pjdciga instead, but I probably mistyped something.
I could not reproduce this by manually duplicating those text areas in lyse’s twt. I end up with the hash
pjdciga instead, but I probably mistyped something.
I could not reproduce this by manually duplicating those text areas in lyse’s twt. I end up with the hash
pjdciga instead, but I probably mistyped something.
I could not reproduce this by manually duplicating those text areas in lyse’s twt. I end up with the hash
pjdciga instead, but I probably mistyped something.
$ wc -l inactive.txt
152 inactive.txt
$ wc -l inactive.txt
152 inactive.txt
https://gist.mills.io/prologic/ae61ae2bfba6401e8955a33394fd858b
If anyone spots anything on this list that shouldn't be deleted, please let me know! 🙏
https://gist.mills.io/prologic/ae61ae2bfba6401e8955a33394fd858b
If anyone spots anything on this list that shouldn't be deleted, please let me know! 🙏
"[Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=]"
"[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",