# 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 60819
# self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=55891
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=55991
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=55791
@stigatle Nice one πŸ₯³ Kooking really good! πŸ‘Œ
@stigatle Nice one πŸ₯³ Kooking really good! πŸ‘Œ
@lyse I'm not sure this is a bug to be honest? What possible code could cause this?! πŸ€”
@lyse I'm not sure this is a bug to be honest? What possible code could cause this?! πŸ€”
@lyse Thank you! πŸ™
@lyse Thank you! πŸ™
@lyse Yes

> How do the feeds look on disk? Do they already contain this bracketed text?

Because the handle just serves the Twtxt file directly.
@lyse Yes

> How do the feeds look on disk? Do they already contain this bracketed text?

Because the handle just serves the Twtxt file directly.
@bender / @mckinley could you both please change your password immediately? I will also work on some other security hardening that I have a hunch about, but will not publicize for now.
@bender / @mckinley could you both please change your password immediately? I will also work on some other security hardening that I have a hunch about, but will not publicize for now.
Hmm I see it! It's so obvious πŸ€¦β€β™‚οΈ I smell an attack of some kind.
Hmm I see it! It's so obvious πŸ€¦β€β™‚οΈ I smell an attack of some kind.
@lyse No problems! Is it stils in the list when I redo this search, it'll be gone πŸ˜…
@lyse No problems! Is it stils in the list when I redo this search, it'll be gone πŸ˜…
@lyse This is really weird. Do you have an example of this bracketed text? Re peers, I'm aware of all the peers, nothing surprising there.
@lyse This is really weird. Do you have an example of this bracketed text? Re peers, I'm aware of all the peers, nothing surprising there.
@mckinley That's actually all I used it for myself πŸ‘Œ All those other "bells 'n whistles" are really just Traefik supporting lots of alternate setups and drivers for discovery, etc.
@mckinley That's actually all I used it for myself πŸ‘Œ All those other "bells 'n whistles" are really just Traefik supporting lots of alternate setups and drivers for discovery, etc.
@bender LOL 🀣
@bender LOL 🀣
@bender LOL 🀣
@bender LOL 🀣

$ wc -l inactive.txt
152 inactive.txt

$ wc -l inactive.txt
152 inactive.txt
πŸ‘‹ At some point over the next day or two I will be deleting the following feeds/accounts:

https://gist.mills.io/prologic/ae61ae2bfba6401e8955a33394fd858b

If anyone spots anything on this list that shouldn't be deleted, please let me know! πŸ™
πŸ‘‹ At some point over the next day or two I will be deleting the following feeds/accounts:

https://gist.mills.io/prologic/ae61ae2bfba6401e8955a33394fd858b

If anyone spots anything on this list that shouldn't be deleted, please let me know! πŸ™
@lyse@
@lyse@
We'll kind of the backend fixes it or grid to 🀣
We'll kind of the backend fixes it or grid to 🀣
@movq@ does not hmmm
@movq@ does not hmmm
@prologic works
@prologic works
The mobile autocomplete bug is something I can reproduce and likely fix soonβ„’ -- I _think_ its happenning because I accidentally nuked this pod's cache the other day (sorry!) 😒 -- But it is also a bug πŸ›
The mobile autocomplete bug is something I can reproduce and likely fix soonβ„’ -- I _think_ its happenning because I accidentally nuked this pod's cache the other day (sorry!) 😒 -- But it is also a bug πŸ›
Like what was this meant to be anyway?


"[Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=]"
Like what was this meant to be anyway?


"[Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=]"
As for @mckinley 's odd Twt, I only see one instance of this:


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 🀣
As for @mckinley 's odd Twt, I only see one instance of this:


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 🀣
As for @mckinley 's odd Twt, I only see one instance of this:


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 🀣
@mckinley Nah it wasn't me, trust me 🀣 I _actually_ use Traefik for my ingres.
@mckinley Nah it wasn't me, trust me 🀣 I _actually_ use Traefik for my ingres.
I don't think I'm smart enough to figure this out πŸ˜…
I don't think I'm smart enough to figure this out πŸ˜…
I can't explain this. I'm leaning towards a peering pod being responsible for producing a different hash, and twtxt.net pulling that in from a peer. But that would only happen if my pod doesn't have the Root Twt ans asked its peers for it. And that implies other pods are producing incorrect/different hashes "somehow". So all of that seems highly unlikely tbh.
I can't explain this. I'm leaning towards a peering pod being responsible for producing a different hash, and twtxt.net pulling that in from a peer. But that would only happen if my pod doesn't have the Root Twt ans asked its peers for it. And that implies other pods are producing incorrect/different hashes "somehow". So all of that seems highly unlikely tbh.
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.
That is this one:


ta6uu5q 2024-08-03T19:30:00+02:00	(#puxvjcq) Hmmm, what is going on here? ...
That is this one:


ta6uu5q 2024-08-03T19:30:00+02:00	(#puxvjcq) Hmmm, what is going on here? ...
That is this one:


ta6uu5q 2024-08-03T19:30:00+02:00\t(#puxvjcq) Hmmm, what is going on here? ...
A equivalent yarnc debug <url> only sees the 2nd hash
A equivalent yarnc debug <url> only sees the 2nd hash
Computers aren't meant to give me three different answers 🀣
Computers aren't meant to give me three different answers 🀣
@movq / @lyse / @xuu any ideas wut da fuq is going on here?! 🀣
@movq / @lyse / @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
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",
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 (_ahh auto-complete is broken only on Mobile?_) @xuu is our hashing reached a point where it's broken and needs to be dumped? πŸ€”_
@lyse (_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)
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
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 Shy are those seem like dupes with different hashes?
@bender Shy are those seem like dupes with different hashes?
Nope none that I can think of πŸ€”
Nope none that I can think of πŸ€”
Yeah okay I can reproduce that weird auto-complete bug
Yeah okay I can reproduce that weird auto-complete bug
Hmm like @lyse
Hmm like @lyse
Hmm I'm not sure either πŸ€”
Hmm I'm not sure either πŸ€”
I've been tricked! 🀣
I've been tricked! 🀣
@lyse Of! It's not real?! 😱
@lyse Of! It's not real?! 😱
@movq I _think_ you're mistaking expectations for quality software 🀣 When have you ever seen quality software out of an enterprise? πŸ˜…
@movq I _think_ you're mistaking expectations for quality software 🀣 When have you ever seen quality software out of an enterprise? πŸ˜…
@movq Bahahaha 🀣
@movq Bahahaha 🀣
@movq So you gotta write your own TCP/IP stack right? πŸ˜… Did that for an undergrad uni assignment, how hard can it. be 🀣
@movq So you gotta write your own TCP/IP stack right? πŸ˜… Did that for an undergrad uni assignment, how hard can it. be 🀣
@movq 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 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 And you thought it would be what exactly? πŸ€” This is Meta we're talking about 🀣
@movq And you thought it would be what exactly? πŸ€” This is Meta we're talking about 🀣
@lyse Well we lost all three rounds 🀣 6-1 6-1 7-0 😱
@lyse Well we lost all three rounds 🀣 6-1 6-1 7-0 😱
@lyse Hehe these are accounts that haven't been used for over 800 days 🀣
@lyse Hehe these are accounts that haven't been used for over 800 days 🀣
@mckinley what makes it so great? πŸ€”
@mckinley what makes it so great? πŸ€”
@shreyan Haha my criteria is being inactive for over two years 🀣
@shreyan Haha my criteria is being inactive for over two years 🀣