# 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 196323
# self = https://watcher.sour.is?offset=161399
# next = https://watcher.sour.is?offset=161499
# prev = https://watcher.sour.is?offset=161299
@jo
comam.es
View Thread
[47°09′52″S, 126°43′28″W] Bad satellite signal -- switching to analog communication
movq
www.uninformativ.de
View Thread
@prologic Doesn’t matter. Far, far away! From everything! That’s where I’d go. 😂
movq
www.uninformativ.de
View Thread
@prologic Doesn’t matter. Far, far away! From everything! That’s where I’d go. 😂
movq
www.uninformativ.de
View Thread
@prologic Doesn’t matter. Far, far away! From everything! That’s where I’d go. 😂
movq
www.uninformativ.de
View Thread
@prologic Doesn’t matter. Far, far away! From everything! That’s where I’d go. 😂
movq
www.uninformativ.de
View Thread
Ran a few tests.

Copying data from the NAS’s encrypted ZFS pool to the USB disk’s encrypted btrfs runs at ~20 MByte/s. That is for a single 1 GB file of random data. Cold caches, sync included.

That same USB disk with the same btrfs can sustain ~75 MByte/s when I use it on my workstation (i7-3770).

And indeed, the aes flag does not show up in the output of lscpu on the NAS.

I’ll try to tweak some things about this, but it might be time for an upgrade … 🫤 (Or I’ll have to re-think the entire thing somehow.)
movq
www.uninformativ.de
View Thread
Ran a few tests.

Copying data from the NAS’s encrypted ZFS pool to the USB disk’s encrypted btrfs runs at ~20 MByte/s. That is for a single 1 GB file of random data. Cold caches, sync included.

That same USB disk with the same btrfs can sustain ~75 MByte/s when I use it on my workstation (i7-3770).

And indeed, the aes flag does not show up in the output of lscpu on the NAS.

I’ll try to tweak some things about this, but it might be time for an upgrade … 🫤 (Or I’ll have to re-think the entire thing somehow.)
movq
www.uninformativ.de
View Thread
Ran a few tests.

Copying data from the NAS’s encrypted ZFS pool to the USB disk’s encrypted btrfs runs at ~20 MByte/s. That is for a single 1 GB file of random data. Cold caches, sync included.

That same USB disk with the same btrfs can sustain ~75 MByte/s when I use it on my workstation (i7-3770).

And indeed, the aes flag does not show up in the output of lscpu on the NAS.

I’ll try to tweak some things about this, but it might be time for an upgrade … 🫤 (Or I’ll have to re-think the entire thing somehow.)
movq
www.uninformativ.de
View Thread
Ran a few tests.

Copying data from the NAS’s encrypted ZFS pool to the USB disk’s encrypted btrfs runs at ~20 MByte/s. That is for a single 1 GB file of random data. Cold caches, sync included.

That same USB disk with the same btrfs can sustain ~75 MByte/s when I use it on my workstation (i7-3770).

And indeed, the aes flag does not show up in the output of lscpu on the NAS.

I’ll try to tweak some things about this, but it might be time for an upgrade … 🫤 (Or I’ll have to re-think the entire thing somehow.)
sorenpeter
darch.dk
View Thread
echo chambers?
sorenpeter
darch.dk
View Thread
echo chambers?
sorenpeter
darch.dk
View Thread
echo chambers?
sorenpeter
darch.dk
View Thread
echo chambers?
@jo
comam.es
View Thread
[47°09′31″S, 126°43′35″W] --no signal--
@rlafuente@ciberlandia.pt
ciberlandia.pt
View Thread
A @aiscarvalho e eu aterramos agora em Nantes para seguir para Rennes, amanhã começa a #libregraphicsmeeting!

Nestes dias conto tootar sobre o evento a partir da minha conta anglófona @rlafuente@rlafuente. Até já*

https://libregraphicsmeeting.org/2024

#lgm2024
@rlafuente@ciberlandia.pt
ciberlandia.pt
View Thread
A @aiscarvalho e eu aterramos agora em Nantes para seguir para Rennes, amanhã começa a #libregraphicsmeeting!

Nestes dias conto tootar sobre o evento a partir da minha conta anglófona @rlafuente@rlafuente. Até já*

https://libregraphicsmeeting.org/2024

#lgm2024
prologic
twtxt.net
View Thread
@lyse Where to? 🤔
prologic
twtxt.net
View Thread
@lyse Where to? 🤔
prologic
twtxt.net
View Thread
What's that thing called when everyone on a social media platform (_hardly matters which one_) all post the same sort of thing. It all sounds oh so wonderful, or all so dramatic, everyone claps and cheers and thumbs up or whatever. What's that thing called? There's a term for it hmmm 🧐
prologic
twtxt.net
View Thread
What's that thing called when everyone on a social media platform (_hardly matters which one_) all post the same sort of thing. It all sounds oh so wonderful, or all so dramatic, everyone claps and cheers and thumbs up or whatever. What's that thing called? There's a term for it hmmm 🧐
lyse
lyse.isobeef.org
View Thread
All packed, ready to go.
prologic
twtxt.net
View Thread
> Use your energy 💪
prologic
twtxt.net
View Thread
> Use your energy 💪
@jo
comam.es
View Thread
[47°09′53″S, 126°43′46″W] Saalmi, retransmit, please
lyse
lyse.isobeef.org
View Thread
@mckinley That's a cool idea!
@jo
comam.es
View Thread
[47°09′47″S, 126°43′43″W] --white noise--
prologic
twtxt.net
View Thread
we'll just have to run another one in early June just for you 😅
prologic
twtxt.net
View Thread
we'll just have to run another one in early June just for you 😅
prologic
twtxt.net
View Thread
@bender LOL well I've scheduled it for the end of the month 😆
prologic
twtxt.net
View Thread
@bender LOL well I've scheduled it for the end of the month 😆
prologic
twtxt.net
View Thread
@dbucklin Nice quote 👌
prologic
twtxt.net
View Thread
@dbucklin Nice quote 👌
@jo
comam.es
View Thread
[47°09′32″S, 126°43′03″W] Transponder fixed
dave
davebucklin.com
View Thread
I don't pretend to have all the answers. I don't pretend to even know what the questions are. Hey, where am I? - wigums
dave
davebucklin.com
View Thread
I don't pretend to have all the answers. I don't pretend to even know what the questions are. Hey, where am I? - wigums
dave
davebucklin.com
View Thread
I don't pretend to have all the answers. I don't pretend to even know what the questions are. Hey, where am I? - wigums
bender
twtxt.net
View Thread
@prologic towards the end of the month.
prologic
twtxt.net
View Thread
@mckinley looks nice! 👌
prologic
twtxt.net
View Thread
@mckinley looks nice! 👌
prologic
twtxt.net
View Thread
When do you get back from your holiday? 🤔
prologic
twtxt.net
View Thread
When do you get back from your holiday? 🤔
stats
yarn.meff.me
View Thread
🧮 USERS:1 FEEDS:2 TWTS:961 ARCHIVED:71927 CACHE:2437 FOLLOWERS:15 FOLLOWING:14
@rlafuente@ciberlandia.pt
ciberlandia.pt
View Thread
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
@rlafuente@ciberlandia.pt
ciberlandia.pt
View Thread
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
mckinley-cc
mckinley.cc
View Thread
Viddy, a modern watch(1) alternative with paging, visual diffs, and history: https://github.com/sachaos/viddy
bender
twtxt.net
View Thread
@prologic will miss the first couple, but will sure join when we return from vacations! 😊
movq
www.uninformativ.de
View Thread
@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. 🥴
movq
www.uninformativ.de
View Thread
@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. 🥴
movq
www.uninformativ.de
View Thread
@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. 🥴
movq
www.uninformativ.de
View Thread
@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. 🥴
lyse
lyse.isobeef.org
View Thread
@prologic Kehrwoche! :-)
lyse
lyse.isobeef.org
View Thread
@prologic I noted it in my calendar, looking forward to it. :-)
terron
duque-terron.cat
View Thread
No fotos!
/https://duque-terron.cat/media/photos/photo_13907-05-2024_19-28-59.jpg) #catsoftwtxt
terron
duque-terron.cat
View Thread
No fotos!
#catsoftwtxt
terron
duque-terron.cat
View Thread
No fotos!
#catsoftwtxt
terron
duque-terron.cat
View Thread
/https://duque-terron.cat/media/photos/photo_13807-05-2024_19-22-10.jpg) #catsoftwtxt
terron
duque-terron.cat
View Thread
#catsoftwtxt
terron
duque-terron.cat
View Thread
#catsoftwtxt
lyse
lyse.isobeef.org
View Thread
@prologic Cool!
@jo
comam.es
View Thread
[47°09′43″S, 126°43′56″W] Transponder still failing
lyse
lyse.isobeef.org
View Thread
@movq I'm subscribed to 48 feeds at the moment. And only a fraction is actually active.
movq
www.uninformativ.de
View Thread
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.
movq
www.uninformativ.de
View Thread
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.
movq
www.uninformativ.de
View Thread
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.
movq
www.uninformativ.de
View Thread
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.
movq
www.uninformativ.de
View Thread
@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. 😈~
movq
www.uninformativ.de
View Thread
@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. 😈~
movq
www.uninformativ.de
View Thread
@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. 😈~
movq
www.uninformativ.de
View Thread
@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. 😈~
movq
www.uninformativ.de
View Thread
@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. 🫤
movq
www.uninformativ.de
View Thread
@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. 🫤
movq
www.uninformativ.de
View Thread
@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. 🫤
movq
www.uninformativ.de
View Thread
@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. 🫤
prologic
twtxt.net
View Thread
@aelaraji Ahh no worries! 😉 I _hope_ the docs are okay 👌
prologic
twtxt.net
View Thread
@aelaraji Ahh no worries! 😉 I _hope_ the docs are okay 👌
aelaraji
aelaraji.com
View Thread
@prologic Checking it out right away! Thanks!
aelaraji
aelaraji.com
View Thread
@prologic Checking it out right away! Thanks!
prologic
twtxt.net
View Thread
@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 💨
prologic
twtxt.net
View Thread
@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 💨
@jo
comam.es
View Thread
[47°09′41″S, 126°43′55″W] Transponder malfunction
prologic
twtxt.net
View Thread
I _think_ I found the bug 🐛
prologic
twtxt.net
View Thread
I _think_ I found the bug 🐛
prologic
twtxt.net
View Thread
I just dropped another 124 useless accounts 🥳
prologic
twtxt.net
View Thread
I just dropped another 124 useless accounts 🥳
prologic
twtxt.net
View Thread
@movq I did indeed edit a Twt just now 🤣 probably from this thread IIRC (typo) 😅
prologic
twtxt.net
View Thread
@movq I did indeed edit a Twt just now 🤣 probably from this thread IIRC (typo) 😅
prologic
twtxt.net
View Thread
@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
twtxt.net
View Thread
@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
www.uninformativ.de
View Thread
@prologic From the DOM? That can’t be right. 😳😳😳
movq
www.uninformativ.de
View Thread
@prologic From the DOM? That can’t be right. 😳😳😳
movq
www.uninformativ.de
View Thread
@prologic From the DOM? That can’t be right. 😳😳😳
movq
www.uninformativ.de
View Thread
@prologic From the DOM? That can’t be right. 😳😳😳
movq
www.uninformativ.de
View Thread
@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. 😅
movq
www.uninformativ.de
View Thread
@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. 😅
movq
www.uninformativ.de
View Thread
@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. 😅
movq
www.uninformativ.de
View Thread
@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. 😅
movq
www.uninformativ.de
View Thread
@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
twtxt.net
View Thread
Or maybe someone added some janky javascript into the codebase I can't find 🤔
prologic
twtxt.net
View Thread
Or maybe someone added some janky javascript into the codebase I can't find 🤔
prologic
twtxt.net
View Thread
@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!