# 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 196312
# self = https://watcher.sour.is?offset=161358
# next = https://watcher.sour.is?offset=161458
# prev = https://watcher.sour.is?offset=161258
🧮 USERS:1 FEEDS:2 TWTS:961 ARCHIVED:71927 CACHE:2437 FOLLOWERS:15 FOLLOWING:14
A Nokia Art Jam organizada pelo @Polyducks@Polyducks é até 30 de maio!

https://itch.io/jam/nokiaartjam-2 Promo da Nokia Art Jam 2023, com vários ecrãs nokia a mostrar diferentes ilustrações 1-bit
A Nokia Art Jam organizada pelo @Polyducks@Polyducks é até 30 de maio!

https://itch.io/jam/nokiaartjam-2 Promo da Nokia Art Jam 2023, com vários ecrãs nokia a mostrar diferentes ilustrações 1-bit
Viddy, a modern watch(1) alternative with paging, visual diffs, and history: https://github.com/sachaos/viddy
@prologic will miss the first couple, but will sure join when we return from vacations! 😊
@mckinley It’s probably a bit faster, but not much. Maybe 20-30 MByte/s (I watched one 40 GB file being copied and it took 20-30 minutes or something like that.)

I need to optimize this. 🥴
@mckinley It’s probably a bit faster, but not much. Maybe 20-30 MByte/s (I watched one 40 GB file being copied and it took 20-30 minutes or something like that.)

I need to optimize this. 🥴
@mckinley It’s probably a bit faster, but not much. Maybe 20-30 MByte/s (I watched one 40 GB file being copied and it took 20-30 minutes or something like that.)

I need to optimize this. 🥴
@mckinley It’s probably a bit faster, but not much. Maybe 20-30 MByte/s (I watched one 40 GB file being copied and it took 20-30 minutes or something like that.)

I need to optimize this. 🥴
@prologic Kehrwoche! :-)
@prologic I noted it in my calendar, looking forward to it. :-)
No fotos!
/https://duque-terron.cat/media/photos/photo_13907-05-2024_19-28-59.jpg) #catsoftwtxt
No fotos!
#catsoftwtxt
No fotos!
#catsoftwtxt
/https://duque-terron.cat/media/photos/photo_13807-05-2024_19-22-10.jpg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
@prologic Cool!
[47°09′43″S, 126°43′56″W] Transponder still failing
@movq I'm subscribed to 48 feeds at the moment. And only a fraction is actually active.
The “annoying” thing about hardware these days is that it basically keeps working “forever”. At least much, much longer that you’d expect.

Now that I think about it … I only remember *one* PC of mine actually dying because of a hardware failure – and that was probably because I did too much overclocking. 😂 If it wasn’t for changes in *software*, I could probably still use them all. I mean, why not, my Pentium 133 still works and I use it for gaming regularly.

So … my little NAS probably won’t die any time soon. Hmmm.
The “annoying” thing about hardware these days is that it basically keeps working “forever”. At least much, much longer that you’d expect.

Now that I think about it … I only remember *one* PC of mine actually dying because of a hardware failure – and that was probably because I did too much overclocking. 😂 If it wasn’t for changes in *software*, I could probably still use them all. I mean, why not, my Pentium 133 still works and I use it for gaming regularly.

So … my little NAS probably won’t die any time soon. Hmmm.
The “annoying” thing about hardware these days is that it basically keeps working “forever”. At least much, much longer that you’d expect.

Now that I think about it … I only remember *one* PC of mine actually dying because of a hardware failure – and that was probably because I did too much overclocking. 😂 If it wasn’t for changes in *software*, I could probably still use them all. I mean, why not, my Pentium 133 still works and I use it for gaming regularly.

So … my little NAS probably won’t die any time soon. Hmmm.
The “annoying” thing about hardware these days is that it basically keeps working “forever”. At least much, much longer that you’d expect.

Now that I think about it … I only remember *one* PC of mine actually dying because of a hardware failure – and that was probably because I did too much overclocking. 😂 If it wasn’t for changes in *software*, I could probably still use them all. I mean, why not, my Pentium 133 still works and I use it for gaming regularly.

So … my little NAS probably won’t die any time soon. Hmmm.
@mckinley Not really sure, to be honest. _Probably_ a couple hundred GB … ? 🤔 With the *changed* data, it might be half a TB to transfer? I’m just guessing.

Let’s see how it goes next time. I don’t expect to add much data any time soon. (On the other hand, I’ll swap the USB disks for the next run, so it’ll take the same ~9 hours, again. Meh.)

I think the solution is to have less data. 😈~
@mckinley Not really sure, to be honest. _Probably_ a couple hundred GB … ? 🤔 With the *changed* data, it might be half a TB to transfer? I’m just guessing.

Let’s see how it goes next time. I don’t expect to add much data any time soon. (On the other hand, I’ll swap the USB disks for the next run, so it’ll take the same ~9 hours, again. Meh.)

I think the solution is to have less data. 😈~
@mckinley Not really sure, to be honest. _Probably_ a couple hundred GB … ? 🤔 With the *changed* data, it might be half a TB to transfer? I’m just guessing.

Let’s see how it goes next time. I don’t expect to add much data any time soon. (On the other hand, I’ll swap the USB disks for the next run, so it’ll take the same ~9 hours, again. Meh.)

I think the solution is to have less data. 😈~
@mckinley Not really sure, to be honest. _Probably_ a couple hundred GB … ? 🤔 With the *changed* data, it might be half a TB to transfer? I’m just guessing.

Let’s see how it goes next time. I don’t expect to add much data any time soon. (On the other hand, I’ll swap the USB disks for the next run, so it’ll take the same ~9 hours, again. Meh.)

I think the solution is to have less data. 😈~
@lyse Yeah, only ~30 of the ~133 feeds I’m following have had a twt in the last month … 56 in the last year. Some had their last twt in 2016. 🫤
@lyse Yeah, only ~30 of the ~133 feeds I’m following have had a twt in the last month … 56 in the last year. Some had their last twt in 2016. 🫤
@lyse Yeah, only ~30 of the ~133 feeds I’m following have had a twt in the last month … 56 in the last year. Some had their last twt in 2016. 🫤
@lyse Yeah, only ~30 of the ~133 feeds I’m following have had a twt in the last month … 56 in the last year. Some had their last twt in 2016. 🫤
@aelaraji Ahh no worries! 😉 I _hope_ the docs are okay 👌
@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. ;-)