# 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 15589
# self = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=12006
# next = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=12106
# prev = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=11906
@prologic @falsifian This just popped up in my head: How about adding a “fetch context” feature? Point jenny to some mail file that contains a twt (or pipe it to stdin) and it will try to auto-discover and fetch all related things. Like, if it sees something like (#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔

It won’t always work. There’s no guarantee that tkjafka will be present in the given URL.

Hmm. 🤔
@prologic @falsifian This just popped up in my head: How about adding a “fetch context” feature? Point jenny to some mail file that contains a twt (or pipe it to stdin) and it will try to auto-discover and fetch all related things. Like, if it sees something like (#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔

It won’t always work. There’s no guarantee that tkjafka will be present in the given URL.

Hmm. 🤔
@prologic @falsifian This just popped up in my head: How about adding a “fetch context” feature? Point jenny to some mail file that contains a twt (or pipe it to stdin) and it will try to auto-discover and fetch all related things. Like, if it sees something like (#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔

It won’t always work. There’s no guarantee that tkjafka will be present in the given URL.

Hmm. 🤔
@prologic @falsifian This just popped up in my head: How about adding a “fetch context” feature? Point jenny to some mail file that contains a twt (or pipe it to stdin) and it will try to auto-discover and fetch all related things. Like, if it sees something like (#tkjafka) @<falsifian https://www.falsifian.org/twtxt.txt>, then it will look in https://www.falsifian.org/twtxt.txt for a twt with hash tkjafka. Maybe even do this recursively until there are no new references anymore. This process *could* include explicitly querying some user-configurable Yarn pods as well. 🤔

It won’t always work. There’s no guarantee that tkjafka will be present in the given URL.

Hmm. 🤔
@bender No idea, but I haven’t used GNOME since 2008. 😅 I, too, like Xfce much better. Xfce (and KDE to some degree) look and feel rather “traditional”, though. You get a standard taskbar and that’s it. Maybe that’s too oldfashioned? 🤷 I’m just speculating.
@bender No idea, but I haven’t used GNOME since 2008. 😅 I, too, like Xfce much better. Xfce (and KDE to some degree) look and feel rather “traditional”, though. You get a standard taskbar and that’s it. Maybe that’s too oldfashioned? 🤷 I’m just speculating.
@bender No idea, but I haven’t used GNOME since 2008. 😅 I, too, like Xfce much better. Xfce (and KDE to some degree) look and feel rather “traditional”, though. You get a standard taskbar and that’s it. Maybe that’s too oldfashioned? 🤷 I’m just speculating.
@bender No idea, but I haven’t used GNOME since 2008. 😅 I, too, like Xfce much better. Xfce (and KDE to some degree) look and feel rather “traditional”, though. You get a standard taskbar and that’s it. Maybe that’s too oldfashioned? 🤷 I’m just speculating.
You might have seen me popping up on IRC. This is how it looks:

https://movq.de/v/3a4f9833f3/

That’s EZirc from the 1990ies. (It says it needs Warp 4, but runs fine on Warp 3.)

Lots of this old stuff still works (technically), but as @lyse said: A lot of it really is dead. There’s not much going on anymore in Usenet.
You might have seen me popping up on IRC. This is how it looks:

https://movq.de/v/3a4f9833f3/

That’s EZirc from the 1990ies. (It says it needs Warp 4, but runs fine on Warp 3.)

Lots of this old stuff still works (technically), but as @lyse said: A lot of it really is dead. There’s not much going on anymore in Usenet.
You might have seen me popping up on IRC. This is how it looks:

https://movq.de/v/3a4f9833f3/

That’s EZirc from the 1990ies. (It says it needs Warp 4, but runs fine on Warp 3.)

Lots of this old stuff still works (technically), but as @lyse said: A lot of it really is dead. There’s not much going on anymore in Usenet.
You might have seen me popping up on IRC. This is how it looks:

https://movq.de/v/3a4f9833f3/

That’s EZirc from the 1990ies. (It says it needs Warp 4, but runs fine on Warp 3.)

Lots of this old stuff still works (technically), but as @lyse said: A lot of it really is dead. There’s not much going on anymore in Usenet.
@aelaraji What terminal are you using? 🤔
@aelaraji What terminal are you using? 🤔
@aelaraji What terminal are you using? 🤔
@aelaraji What terminal are you using? 🤔
@lyse Stell dir vor, es wären NaN Grad! 😱
@lyse Stell dir vor, es wären NaN Grad! 😱
@lyse Stell dir vor, es wären NaN Grad! 😱
@lyse Stell dir vor, es wären NaN Grad! 😱
This has become quite a large thread. 😅

https://movq.de/v/5c51be2cd3/s.png
This has become quite a large thread. 😅

https://movq.de/v/5c51be2cd3/s.png
This has become quite a large thread. 😅

https://movq.de/v/5c51be2cd3/s.png
This has become quite a large thread. 😅

https://movq.de/v/5c51be2cd3/s.png
@quark I once decided against that, didn’t I? 🤔 I don’t remember why anymore. I’ll think about it. 🤔
@quark I once decided against that, didn’t I? 🤔 I don’t remember why anymore. I’ll think about it. 🤔
@quark I once decided against that, didn’t I? 🤔 I don’t remember why anymore. I’ll think about it. 🤔
@quark I once decided against that, didn’t I? 🤔 I don’t remember why anymore. I’ll think about it. 🤔
@bender Yes, I see the same. Right-to-left Unicode breaks mutt (and apparently neomutt). It was once reported as an issue:

https://gitlab.com/muttmua/mutt/-/issues/131

They closed it because the solution was supposed to be implemented in terminals … Apparently, that never happened?
@bender Yes, I see the same. Right-to-left Unicode breaks mutt (and apparently neomutt). It was once reported as an issue:

https://gitlab.com/muttmua/mutt/-/issues/131

They closed it because the solution was supposed to be implemented in terminals … Apparently, that never happened?
@bender Yes, I see the same. Right-to-left Unicode breaks mutt (and apparently neomutt). It was once reported as an issue:

https://gitlab.com/muttmua/mutt/-/issues/131

They closed it because the solution was supposed to be implemented in terminals … Apparently, that never happened?
@bender Yes, I see the same. Right-to-left Unicode breaks mutt (and apparently neomutt). It was once reported as an issue:

https://gitlab.com/muttmua/mutt/-/issues/131

They closed it because the solution was supposed to be implemented in terminals … Apparently, that never happened?
@falsifian Ah, I see. 🤔 Maybe I’ll add that. To be honest, I have the same “problem” regarding the slashdot feed. 😅 It’s mostly stuff that I’m not interested in – but from time to time someone replies and then I want to see what it’s about.
@falsifian Ah, I see. 🤔 Maybe I’ll add that. To be honest, I have the same “problem” regarding the slashdot feed. 😅 It’s mostly stuff that I’m not interested in – but from time to time someone replies and then I want to see what it’s about.
@falsifian Ah, I see. 🤔 Maybe I’ll add that. To be honest, I have the same “problem” regarding the slashdot feed. 😅 It’s mostly stuff that I’m not interested in – but from time to time someone replies and then I want to see what it’s about.
@falsifian Ah, I see. 🤔 Maybe I’ll add that. To be honest, I have the same “problem” regarding the slashdot feed. 😅 It’s mostly stuff that I’m not interested in – but from time to time someone replies and then I want to see what it’s about.
@falsifian You mean fetching the feed temporarily and then discarding all its twts again? 🤔 I don’t think there’s an easy way to do that, other than filtering in your mail client, yeah. 🤔
@falsifian You mean fetching the feed temporarily and then discarding all its twts again? 🤔 I don’t think there’s an easy way to do that, other than filtering in your mail client, yeah. 🤔
@falsifian You mean fetching the feed temporarily and then discarding all its twts again? 🤔 I don’t think there’s an easy way to do that, other than filtering in your mail client, yeah. 🤔
@falsifian You mean fetching the feed temporarily and then discarding all its twts again? 🤔 I don’t think there’s an easy way to do that, other than filtering in your mail client, yeah. 🤔
@aelaraji That’s good to know. 🤔 Luckily, the phone wasn’t *full* of 3rd party stuff. There were so few of them actually, that I didn’t really bother looking. That’s why I only found out recently about that Meta stuff.
@aelaraji That’s good to know. 🤔 Luckily, the phone wasn’t *full* of 3rd party stuff. There were so few of them actually, that I didn’t really bother looking. That’s why I only found out recently about that Meta stuff.
@aelaraji That’s good to know. 🤔 Luckily, the phone wasn’t *full* of 3rd party stuff. There were so few of them actually, that I didn’t really bother looking. That’s why I only found out recently about that Meta stuff.
@aelaraji That’s good to know. 🤔 Luckily, the phone wasn’t *full* of 3rd party stuff. There were so few of them actually, that I didn’t really bother looking. That’s why I only found out recently about that Meta stuff.
The soundtrack of World of Goo 2 is amazing. It’s quite epic and melancholic at times.

https://www.youtube.com/watch?v=sAUwyCOaGoc

It doesn’t fit the “cuteness” of the game at all – but there are a lot of contradictions in that game anyway, it’s an important aspect.
The soundtrack of World of Goo 2 is amazing. It’s quite epic and melancholic at times.

https://www.youtube.com/watch?v=sAUwyCOaGoc

It doesn’t fit the “cuteness” of the game at all – but there are a lot of contradictions in that game anyway, it’s an important aspect.
The soundtrack of World of Goo 2 is amazing. It’s quite epic and melancholic at times.

https://www.youtube.com/watch?v=sAUwyCOaGoc

It doesn’t fit the “cuteness” of the game at all – but there are a lot of contradictions in that game anyway, it’s an important aspect.
The soundtrack of World of Goo 2 is amazing. It’s quite epic and melancholic at times.

https://www.youtube.com/watch?v=sAUwyCOaGoc

It doesn’t fit the “cuteness” of the game at all – but there are a lot of contradictions in that game anyway, it’s an important aspect.
@lyse 4.75 seconds, are you kidding me? 🤯
@lyse 4.75 seconds, are you kidding me? 🤯
@lyse 4.75 seconds, are you kidding me? 🤯
@lyse 4.75 seconds, are you kidding me? 🤯
@prologic Yep. ✅
@prologic Yep. ✅
@prologic Yep. ✅
@prologic Yep. ✅
@xuu Ahhhh, ohhhh, ouch. 🫤
@xuu Ahhhh, ohhhh, ouch. 🫤
@xuu Ahhhh, ohhhh, ouch. 🫤
@xuu Ahhhh, ohhhh, ouch. 🫤
@lyse Hmmm, the user agents indicate two different pods. 🤔 Most of them are twtxt.net, though, only one user is something else. 🤔
@lyse Hmmm, the user agents indicate two different pods. 🤔 Most of them are twtxt.net, though, only one user is something else. 🤔
@lyse Hmmm, the user agents indicate two different pods. 🤔 Most of them are twtxt.net, though, only one user is something else. 🤔
@lyse Hmmm, the user agents indicate two different pods. 🤔 Most of them are twtxt.net, though, only one user is something else. 🤔
@lyse Yeah, indeed, but still. 😂
@lyse Yeah, indeed, but still. 😂
@lyse Yeah, indeed, but still. 😂
@lyse Yeah, indeed, but still. 😂
@mckinley Uhhh, I bet the support people at Lenovo love this. (Assuming it’s accurate.)
@mckinley Uhhh, I bet the support people at Lenovo love this. (Assuming it’s accurate.)
@mckinley Uhhh, I bet the support people at Lenovo love this. (Assuming it’s accurate.)
@mckinley Uhhh, I bet the support people at Lenovo love this. (Assuming it’s accurate.)
@lyse Ahh, good old Senfglastradition. Looks delicious. 👍
@lyse Ahh, good old Senfglastradition. Looks delicious. 👍
@lyse Ahh, good old Senfglastradition. Looks delicious. 👍
@lyse Ahh, good old Senfglastradition. Looks delicious. 👍
Speaking of web server logs: Unless someone posts one of my blog posts on HackerNews (I never do that myself, don’t even have an account), my twtxt.txt file is always *the most requested resource*. 😂 It easily gets several thousand hits, way more than the blog’s Atom feed. 😂
Speaking of web server logs: Unless someone posts one of my blog posts on HackerNews (I never do that myself, don’t even have an account), my twtxt.txt file is always *the most requested resource*. 😂 It easily gets several thousand hits, way more than the blog’s Atom feed. 😂
Speaking of web server logs: Unless someone posts one of my blog posts on HackerNews (I never do that myself, don’t even have an account), my twtxt.txt file is always *the most requested resource*. 😂 It easily gets several thousand hits, way more than the blog’s Atom feed. 😂
Speaking of web server logs: Unless someone posts one of my blog posts on HackerNews (I never do that myself, don’t even have an account), my twtxt.txt file is always *the most requested resource*. 😂 It easily gets several thousand hits, way more than the blog’s Atom feed. 😂
@prologic I didn’t want to hijack @bender’s thread: There’s two things that feel a bit unexpected regarding the requests of 159.196.9.199 in my logs:

1. It doesn’t respect HTTP 301 and instead asks for the same URL every time, thus needing a redirect.
2. Is this *one* Yarn pod or several? I’m seeing multiple requests from this same IP with *different user agents*. It’s not a lot, just about 5 different ones (every couple of minutes), but I thought that Yarn only issued *one* such request? 🤔 You know, when several users follow the same feed, Yarn would only fetch that feed once?
@prologic I didn’t want to hijack @bender’s thread: There’s two things that feel a bit unexpected regarding the requests of 159.196.9.199 in my logs:

1. It doesn’t respect HTTP 301 and instead asks for the same URL every time, thus needing a redirect.
2. Is this *one* Yarn pod or several? I’m seeing multiple requests from this same IP with *different user agents*. It’s not a lot, just about 5 different ones (every couple of minutes), but I thought that Yarn only issued *one* such request? 🤔 You know, when several users follow the same feed, Yarn would only fetch that feed once?
@prologic I didn’t want to hijack @bender’s thread: There’s two things that feel a bit unexpected regarding the requests of 159.196.9.199 in my logs:

1. It doesn’t respect HTTP 301 and instead asks for the same URL every time, thus needing a redirect.
2. Is this *one* Yarn pod or several? I’m seeing multiple requests from this same IP with *different user agents*. It’s not a lot, just about 5 different ones (every couple of minutes), but I thought that Yarn only issued *one* such request? 🤔 You know, when several users follow the same feed, Yarn would only fetch that feed once?
@prologic I didn’t want to hijack @bender’s thread: There’s two things that feel a bit unexpected regarding the requests of 159.196.9.199 in my logs:

1. It doesn’t respect HTTP 301 and instead asks for the same URL every time, thus needing a redirect.
2. Is this *one* Yarn pod or several? I’m seeing multiple requests from this same IP with *different user agents*. It’s not a lot, just about 5 different ones (every couple of minutes), but I thought that Yarn only issued *one* such request? 🤔 You know, when several users follow the same feed, Yarn would only fetch that feed once?
@xuu I don’t even have a WhatsApp password, it never asked me? 🤔
@xuu I don’t even have a WhatsApp password, it never asked me? 🤔
@xuu I don’t even have a WhatsApp password, it never asked me? 🤔
@xuu I don’t even have a WhatsApp password, it never asked me? 🤔
@prologic Maybe one day I’ll have the motivation to learn enough about JPEG, so I can understand the reason behind this. But not today. 😅
@prologic Maybe one day I’ll have the motivation to learn enough about JPEG, so I can understand the reason behind this. But not today. 😅
@prologic Maybe one day I’ll have the motivation to learn enough about JPEG, so I can understand the reason behind this. But not today. 😅
@prologic Maybe one day I’ll have the motivation to learn enough about JPEG, so I can understand the reason behind this. But not today. 😅


> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time

So this kind of works in stock Android, too. You have to reboot after switching back to the main profile, then the second profile won’t get loaded at all.

(I bet that this stops working in the future. It feels like the second profile doesn’t get loaded as a means to save CPU power. Once those smartphones get even more powerful, there’s no need to do that anymore …)


> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time

So this kind of works in stock Android, too. You have to reboot after switching back to the main profile, then the second profile won’t get loaded at all.

(I bet that this stops working in the future. It feels like the second profile doesn’t get loaded as a means to save CPU power. Once those smartphones get even more powerful, there’s no need to do that anymore …)


> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time

So this kind of works in stock Android, too. You have to reboot after switching back to the main profile, then the second profile won’t get loaded at all.

(I bet that this stops working in the future. It feels like the second profile doesn’t get loaded as a means to save CPU power. Once those smartphones get even more powerful, there’s no need to do that anymore …)


> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time

So this kind of works in stock Android, too. You have to reboot after switching back to the main profile, then the second profile won’t get loaded at all.

(I bet that this stops working in the future. It feels like the second profile doesn’t get loaded as a means to save CPU power. Once those smartphones get even more powerful, there’s no need to do that anymore …)
(I tend to post all that retrocomputing stuff on Mastodon lately. 🤔)
(I tend to post all that retrocomputing stuff on Mastodon lately. 🤔)
(I tend to post all that retrocomputing stuff on Mastodon lately. 🤔)
This morning’s task: Making the thumbnails in my blog compatible with IBM WebExplorer 1.0 on OS/2 Warp 3. 🤪

Before:

https://movq.de/v/b7443c8873/a.jpg

After:

https://movq.de/v/b7443c8873/b.jpg

And the fix was using -define jpeg:sampling-factor=2x1 when creating the thumbnails using ImageMagick.

I’m not really sure, though, what’s going on. 🤔

More context: https://tilde.zone/@movq/112981572946464025