# 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 196309
# self = https://watcher.sour.is?offset=161325
# next = https://watcher.sour.is?offset=161425
# prev = https://watcher.sour.is?offset=161225
@aelaraji Ahh no worries! πŸ˜‰ I _hope_ the docs are okay πŸ‘Œ
@prologic Checking it out right away! Thanks!
@prologic Checking it out right away! Thanks!
@slashdot Good, those US congressmen are fucking idiots I swear to god 🀣 They don't know the difference between China, Taiwan, Singapore or Thailand if they fell over those countries backwards πŸ˜… Bunch of old farts πŸ’¨
@slashdot Good, those US congressmen are fucking idiots I swear to god 🀣 They don't know the difference between China, Taiwan, Singapore or Thailand if they fell over those countries backwards πŸ˜… Bunch of old farts πŸ’¨
[47Β°09β€²41β€³S, 126Β°43β€²55β€³W] Transponder malfunction
I _think_ I found the bug πŸ›
I _think_ I found the bug πŸ›
I just dropped another 124 useless accounts πŸ₯³
I just dropped another 124 useless accounts πŸ₯³
@movq I did indeed edit a Twt just now 🀣 probably from this thread IIRC (typo) πŸ˜…
@movq I did indeed edit a Twt just now 🀣 probably from this thread IIRC (typo) πŸ˜…
@movq I know right πŸ˜… This can't be true, I must be over reacting and something else is fucked up with some code somewhere 🀣
@movq I know right πŸ˜… This can't be true, I must be over reacting and something else is fucked up with some code somewhere 🀣
@prologic From the DOM? That can’t be right. 😳😳😳
@prologic From the DOM? That can’t be right. 😳😳😳
@prologic From the DOM? That can’t be right. 😳😳😳
@prologic From the DOM? That can’t be right. 😳😳😳
@prologic It always fetches the canonical feed URL and, when it can’t find the latest twt hash (that it saw in the previous run) it traverses the archived feeds until it does find it. Something along those lines.

I just got one such notification:

Date: Tue, 07 May 2024 15:56:01 +0200
From: me@pinguin
To: me@pinguin
Subject: [regularly] jenny

Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/1 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/2 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/3 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/4 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/5 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)

Now, your feed did *not* get archived, as far as I can tell. So why am I getting this then? Have you edited a twt just now? That would explain it. πŸ˜…
@prologic It always fetches the canonical feed URL and, when it can’t find the latest twt hash (that it saw in the previous run) it traverses the archived feeds until it does find it. Something along those lines.

I just got one such notification:

Date: Tue, 07 May 2024 15:56:01 +0200
From: me@pinguin
To: me@pinguin
Subject: [regularly] jenny

Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/1 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/2 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/3 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/4 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/5 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)

Now, your feed did *not* get archived, as far as I can tell. So why am I getting this then? Have you edited a twt just now? That would explain it. πŸ˜…
@prologic It always fetches the canonical feed URL and, when it can’t find the latest twt hash (that it saw in the previous run) it traverses the archived feeds until it does find it. Something along those lines.

I just got one such notification:

Date: Tue, 07 May 2024 15:56:01 +0200
From: me@pinguin
To: me@pinguin
Subject: [regularly] jenny

Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/1 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/2 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/3 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/4 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/5 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)

Now, your feed did *not* get archived, as far as I can tell. So why am I getting this then? Have you edited a twt just now? That would explain it. πŸ˜…
@prologic It always fetches the canonical feed URL and, when it can’t find the latest twt hash (that it saw in the previous run) it traverses the archived feeds until it does find it. Something along those lines.

I just got one such notification:

Date: Tue, 07 May 2024 15:56:01 +0200
From: me@pinguin
To: me@pinguin
Subject: \n jenny

Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/1 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/2 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/3 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/4 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/5 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)

Now, your feed did *not* get archived, as far as I can tell. So why am I getting this then? Have you edited a twt just now? That would explain it. πŸ˜…
@prologic It always fetches the canonical feed URL and, when it can’t find the latest twt hash (that it saw in the previous run) it traverses the archived feeds until it does find it. Something along those lines.

I just got one such notification:

Date: Tue, 07 May 2024 15:56:01 +0200
From: me@pinguin
To: me@pinguin
Subject: [regularly] jenny

Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/1 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/2 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/3 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/4 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/5 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)

Now, your feed did *not* get archived, as far as I can tell. So why am I getting this then? Have you edited a twt just now? That would explain it. πŸ˜…
Or maybe someone added some janky javascript into the codebase I can't find πŸ€”
Or maybe someone added some janky javascript into the codebase I can't find πŸ€”
@movq No it's stripping it from the DOM. The server is sending a document with fragments in the URI(s) of links that are 'Inreply-to" links (for context). Chrome is stripping them!
@movq No it's stripping it from the DOM. The server is sending a document with fragments in the URI(s) of links that are 'Inreply-to" links (for context). Chrome is stripping them!
@lyse Fair enough, I mean I have the same sets of problems too.
@lyse Fair enough, I mean I have the same sets of problems too.
@prologic Strip it from what? From requests being sent to the server? That’s always been the case, afaik. πŸ€”
@prologic Strip it from what? From requests being sent to the server? That’s always been the case, afaik. πŸ€”
@prologic Strip it from what? From requests being sent to the server? That’s always been the case, afaik. πŸ€”
@prologic Strip it from what? From requests being sent to the server? That’s always been the case, afaik. πŸ€”
@movq Noice πŸ‘Œ
@movq Noice πŸ‘Œ
@movq Oh, and then it switches to the new active feed? πŸ€”
@movq Oh, and then it switches to the new active feed? πŸ€”
@movq It appears to strip the #rafgment πŸ€¦β€β™‚οΈ
@movq It appears to strip the #fragment πŸ€¦β€β™‚οΈ
@movq It appears to strip the #fragment πŸ€¦β€β™‚οΈ
@prologic Huh? What does that look like in Chrome? πŸ€” (I only have Chromium.)
@prologic Huh? What does that look like in Chrome? πŸ€” (I only have Chromium.)
@prologic Huh? What does that look like in Chrome? πŸ€” (I only have Chromium.)
@prologic Huh? What does that look like in Chrome? πŸ€” (I only have Chromium.)
πŸ‘‹ Okay folks, let's startup the Yarn.social calls again.

- Event: Yarn.social Online Meetup
- When: 25th May 2024 at 12:00pm UTC (midday)
- Where: Mills Meet : Yarn.social
- Cadence: 4th Saturday of every Month

Agenda:

> Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you've been working on. chit-chat, whatever πŸ˜…

#Yarn.social #Meetup
πŸ‘‹ Okay folks, let's startup the Yarn.social calls again.

- Event: Yarn.social Online Meetup
- When: 25th May 2024 at 12:00pm UTC (midday)
- Where: Mills Meet : Yarn.social
- Cadence: 4th Saturday of every Month

#Yarn.social #Meetup
πŸ‘‹ Okay folks, let's startup the Yarn.social calls again.

- Event: Yarn.social Online Meetup
- When: 25th May 2024 at 12:00pm UTC (midday)
- Where: Mills Meet : Yarn.social
- Cadence: 4th Saturday of every Month

Agenda:

> Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you've been working on. chit-chat, whatever πŸ˜…

#Yarn.social #Meetup
@prologic My client tells me when it fetches archived feeds. That’s all.
@prologic My client tells me when it fetches archived feeds. That’s all.
@prologic My client tells me when it fetches archived feeds. That’s all.
@prologic My client tells me when it fetches archived feeds. That’s all.
@prologic Ah, yes, that’s better! πŸ‘
@prologic Ah, yes, that’s better! πŸ‘
@prologic Ah, yes, that’s better! πŸ‘
@prologic Ah, yes, that’s better! πŸ‘
Testing (please ignore)

https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MDJuM2hzNThvaWsydTdoa3B2ODl0dGxlZzFfMjAyNDA1MjVUMTIwMDAwWiBwcm9sb2dpY0BzaG9ydGNpcmN1aXQubmV0LmF1&tmsrc=prologic%40shortcircuit.net.au&scp=ALL">https://www.google.com/calendar/images/ext/gc_button1_en.gif">_
@movq Fixed πŸ‘Œ
@movq Fixed πŸ‘Œ
@lyse Anyway fixed πŸ‘Œ
@lyse Anyway fixed πŸ‘Œ
I just realized something that's completely fucked up.


$ curl -qssL https://twtxt.net/ | grep -E 'In-reply-to' | head
<a href="https://twtxt.net/conv/2tjsjuq?p=1#rlsxhsq" title="Show conversation for #2tjsjuq">In-reply-to</a>
<a href="https://twtxt.net/conv/bghmkra?p=1#dfnrbyq" title="Show conversation for #bghmkra">In-reply-to</a>
<a href="https://twtxt.net/conv/e24exeq?p=1#itft6wa" title="Show conversation for #e24exeq">In-reply-to</a>


For some reason the latest version of Chrome is stripped #fragment(s) from the HTML body being served.

da fuq?! When did this change, in what version? Did we (W3C and the community) agree that this behavior should change?! 😱 Fark'n hell Googleβ„’ Chrome 🀬
I just realized something that's completely fucked up.


$ curl -qssL https://twtxt.net/ | grep -E 'In-reply-to' | head
<a href="https://twtxt.net/conv/2tjsjuq?p=1#rlsxhsq" title="Show conversation for #2tjsjuq">In-reply-to</a>
<a href="https://twtxt.net/conv/bghmkra?p=1#dfnrbyq" title="Show conversation for #bghmkra">In-reply-to</a>
<a href="https://twtxt.net/conv/e24exeq?p=1#itft6wa" title="Show conversation for #e24exeq">In-reply-to</a>


For some reason the latest version of Chrome is stripped #fragment(s) from the HTML body being served.

da fuq?! When did this change, in what version? Did we (W3C and the community) agree that this behavior should change?! 😱 Fark'n hell Googleβ„’ Chrome 🀬
Pinellas County - Base: 4.69 miles, 00:09:21 average pace, 00:43:51 duration
psh, was supposed to be base but the damn heat and humidity really brought that heart rate up. the last mile i felt it and was done w/ only three minutes left on the timer.
#running
Pinellas County - Base: 4.69 miles, 00:09:21 average pace, 00:43:51 duration
psh, was supposed to be a base but the damn heat and humidity really brought that HR up. the last mile i felt it and was done with only three minutes left on the timer.
#running
Pinellas County - Base: 4.69 miles, 00:09:21 average pace, 00:43:51 duration
psh, was supposed to be a base but the damn heat and humidity really brought that HR up. the last mile i felt it and was done with only three minutes left on the timer.
#running
Pinellas County - Base: 4.69 miles, 00:09:21 average pace, 00:43:51 duration
psh, was supposed to be a base but the damn heat and humidity really brought that HR up. the last mile i felt it and was done with only three minutes left on the timer.
#running
@prologic Oh, was I? I don't recall any of that. But who knows. ;-)
@movq Wut?! 🧐 How do you get notified? πŸ€”
@movq Wut?! 🧐 How do you get notified? πŸ€”
@prologic I won't see any activity again, unless somebody else I follow interacts with them. Yep, fetching the feeds still happens with a patched version of the original twtxt client. tt is just a viewer of the database contents.
(Hmmm, I think I could add the time of the last twt to the output of jenny -l. πŸ€” Currently it only shows the last successful retrieval time.)
(Hmmm, I think I could add the time of the last twt to the output of jenny -l. πŸ€” Currently it only shows the last successful retrieval time.)
(Hmmm, I think I could add the time of the last twt to the output of jenny -l. πŸ€” Currently it only shows the last successful retrieval time.)
(Hmmm, I think I could add the time of the last twt to the output of jenny -l. πŸ€” Currently it only shows the last successful retrieval time.)
@prologic Every now and then, I get a notification about Yarn feeds getting archived/rotated. πŸ˜… Appears to work without issues. πŸ‘
@prologic Every now and then, I get a notification about Yarn feeds getting archived/rotated. πŸ˜… Appears to work without issues. πŸ‘
@prologic Every now and then, I get a notification about Yarn feeds getting archived/rotated. πŸ˜… Appears to work without issues. πŸ‘
@prologic Every now and then, I get a notification about Yarn feeds getting archived/rotated. πŸ˜… Appears to work without issues. πŸ‘
[47Β°09β€²11β€³S, 126Β°43β€²02β€³W] Storm recedes -- back to normal work
I _think_ the next cleanup I'll do is to delete any account that was created, and then used within some time window and never used again. Does that make sense? πŸ€”
I _think_ the next cleanup I'll do is to delete any account that was created, and then used within some time window and never used again. Does that make sense? πŸ€”
@lyse I _think_ you were the one that originally came up with this BUIDL thing. Was it always suppose to be the commit timestamp? πŸ€”
@lyse I _think_ you were the one that originally came up with this BUIDL thing. Was it always suppose to be the commit timestamp? πŸ€”
@lyse What if they see traffic again at some point? πŸ€” How do you fetch feeds again? You fork/exec out to the Python twtxt client right? πŸ€”
@lyse What if they see traffic again at some point? πŸ€” How do you fetch feeds again? You fork/exec out to the Python twtxt client right? πŸ€”
@lyse Since some time ago I automated the same feature in yarnd; I haven't really noticed when it happens. But I went and had a look just now, looks like it "just works"β„’ and no-one notices 🀣


$ dke -t f3fe6f03902e /bin/sh
/ # cd /data/feeds
/data/feeds # ls -lah prologic*
-rw-r--r--    1 yarnd    yarnd       7.9K May  7 05:16 prologic
-rw-r--r--    1 yarnd    yarnd     877.8K May  3 23:32 prologic.1
-rw-r--r--    1 yarnd    yarnd     515.1K Mar 24  2023 prologic.2
-rw-r--r--    1 yarnd    yarnd     963.7K Nov 19  2022 prologic.3
-rw-r--r--    1 yarnd    yarnd     995.6K Mar 10  2022 prologic.4
-rw-r--r--    1 yarnd    yarnd       1.9M Nov  7  2021 prologic.5
@lyse Since some time ago I automated the same feature in yarnd; I haven't really noticed when it happens. But I went and had a look just now, looks like it "just works"β„’ and no-one notices 🀣


$ dke -t f3fe6f03902e /bin/sh
/ # cd /data/feeds
/data/feeds # ls -lah prologic*
-rw-r--r--    1 yarnd    yarnd       7.9K May  7 05:16 prologic
-rw-r--r--    1 yarnd    yarnd     877.8K May  3 23:32 prologic.1
-rw-r--r--    1 yarnd    yarnd     515.1K Mar 24  2023 prologic.2
-rw-r--r--    1 yarnd    yarnd     963.7K Nov 19  2022 prologic.3
-rw-r--r--    1 yarnd    yarnd     995.6K Mar 10  2022 prologic.4
-rw-r--r--    1 yarnd    yarnd       1.9M Nov  7  2021 prologic.5
[47Β°09β€²03β€³S, 126Β°43β€²49β€³W] Weather forecast alert -- storm from S
Righto, it's time for a rotation into archive feeds again.
I just cleared my following list. Kicked out all the 26Β feeds that have not been updated for two years or more. This will reduce a bit of useless traffic.
@prologic I figured, yep.
@prologic Does one need a build timestamp anyway? That's an enemy to reproducible builds. Maybe just use the commit timestamp? That would work at least for official releases. It would be off for dirty working directories during development, though: git show -s --pretty=format:%cI
@aelaraji I think you'll find it simpler to use zs
@aelaraji I think you'll find it simpler to use zs
[47Β°09β€²28β€³S, 126Β°43β€²14β€³W] --interrupted--
@viktoridsl da fuq?!
@viktoridsl da fuq?!
@lyse Yeah but only 20 or so are actually active 🀣
@lyse Yeah but only 20 or so are actually active 🀣
Snikket is a front end to xmpp which does have e2e encryption through either pgp or omemo.