# 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 15372
# self = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=12075
# next = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=12175
# prev = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=11975
@bender Yeah, I switched to OpenBSD a couple of years ago when sysupgrade(8) became available. I like it a lot, requires very little maintenance. šŸ‘Œ
@bender I am considering it. šŸ˜… (I might end up being too lazy to set any of this up. 🤪)
@bender I am considering it. šŸ˜… (I might end up being too lazy to set any of this up. 🤪)
@bender I am considering it. šŸ˜… (I might end up being too lazy to set any of this up. 🤪)
@bender I am considering it. šŸ˜… (I might end up being too lazy to set any of this up. 🤪)
Thought: If the invocation including --only-twt-hash fails to find that twt, it could ask a couple of Yarn instances for it (if configured).

(All this needs polishing.)
Thought: If the invocation including --only-twt-hash fails to find that twt, it could ask a couple of Yarn instances for it (if configured).

(All this needs polishing.)
Thought: If the invocation including --only-twt-hash fails to find that twt, it could ask a couple of Yarn instances for it (if configured).

(All this needs polishing.)
Thought: If the invocation including --only-twt-hash fails to find that twt, it could ask a couple of Yarn instances for it (if configured).

(All this needs polishing.)
Honestly, the only thing I want to do on Mastodon is follow the #retrocomputing hashtag and sometimes post under that hashtag. That’s it. šŸ˜‚
Honestly, the only thing I want to do on Mastodon is follow the #retrocomputing hashtag and sometimes post under that hashtag. That’s it. šŸ˜‚
Honestly, the only thing I want to do on Mastodon is follow the #retrocomputing hashtag and sometimes post under that hashtag. That’s it. šŸ˜‚
Honestly, the only thing I want to do on Mastodon is follow the #retrocomputing hashtag and sometimes post under that hashtag. That’s it. šŸ˜‚
There was an outage of the Mastodon server I use this morning. A good reminder that this is a service that someone else hosts (and I don’t even pay for it). Could be gone tomorrow.

Now that I’ve got a server to spare (the Matrix one is gone), I might look into hosting a snac instance. šŸ¤”
There was an outage of the Mastodon server I use this morning. A good reminder that this is a service that someone else hosts (and I don’t even pay for it). Could be gone tomorrow.

Now that I’ve got a server to spare (the Matrix one is gone), I might look into hosting a snac instance. šŸ¤”
There was an outage of the Mastodon server I use this morning. A good reminder that this is a service that someone else hosts (and I don’t even pay for it). Could be gone tomorrow.

Now that I’ve got a server to spare (the Matrix one is gone), I might look into hosting a snac instance. šŸ¤”
There was an outage of the Mastodon server I use this morning. A good reminder that this is a service that someone else hosts (and I don’t even pay for it). Could be gone tomorrow.

Now that I’ve got a server to spare (the Matrix one is gone), I might look into hosting a snac instance. šŸ¤”
RIP, Matrix server. 🪦

$ doas rcctl stop synapse
synapse(ok)
RIP, Matrix server. 🪦

$ doas rcctl stop synapse
synapse(ok)
RIP, Matrix server. 🪦

$ doas rcctl stop synapse
synapse(ok)
RIP, Matrix server. 🪦

$ doas rcctl stop synapse
synapse(ok)
@prologic I would be so damned proud of that. šŸ’Ŗ
@prologic I would be so damned proud of that. šŸ’Ŗ
@prologic I would be so damned proud of that. šŸ’Ŗ
@prologic I would be so damned proud of that. šŸ’Ŗ
@falsifian I’ve pushed a *draft* into the git repo.

You can now do a ā€œoneshot fetchā€ for a URL:

jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest

This fetches the entire feed, which might be too much. So there’s also this, which only fetches a single twt:

jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest --only-twt-hash r6rbinq

Let me know what you think. šŸ¤”
@falsifian I’ve pushed a *draft* into the git repo.

You can now do a ā€œoneshot fetchā€ for a URL:

jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest

This fetches the entire feed, which might be too much. So there’s also this, which only fetches a single twt:

jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest --only-twt-hash r6rbinq

Let me know what you think. šŸ¤”
@falsifian I’ve pushed a *draft* into the git repo.

You can now do a ā€œoneshot fetchā€ for a URL:

jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest

This fetches the entire feed, which might be too much. So there’s also this, which only fetches a single twt:

jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest --only-twt-hash r6rbinq

Let me know what you think. šŸ¤”
@falsifian I’ve pushed a *draft* into the git repo.

You can now do a ā€œoneshot fetchā€ for a URL:

jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest

This fetches the entire feed, which might be too much. So there’s also this, which only fetches a single twt:

jenny oneshot-fetch --url https://feeds.twtxt.net/hacker-news-newest/twtxt.txt --nick hacker-news-newest --only-twt-hash r6rbinq

Let me know what you think. šŸ¤”
@quark It’s really only about the hash, isn’t it? šŸ¤” The user mention (@<quark …) should still be visible in full?
@quark It’s really only about the hash, isn’t it? šŸ¤” The user mention (@<quark …) should still be visible in full?
@quark It’s really only about the hash, isn’t it? šŸ¤” The user mention (@<quark …) should still be visible in full?
@quark It’s really only about the hash, isn’t it? šŸ¤” The user mention (@<quark …) should still be visible in full?
@prologic Ok, wow, yes, I really only do want that one single missing twt. The slashdot/hackernews feeds are *huge*. 🄓
@prologic Ok, wow, yes, I really only do want that one single missing twt. The slashdot/hackernews feeds are *huge*. 🄓
@prologic Ok, wow, yes, I really only do want that one single missing twt. The slashdot/hackernews feeds are *huge*. 🄓
@prologic Ok, wow, yes, I really only do want that one single missing twt. The slashdot/hackernews feeds are *huge*. 🄓
@prologic Where can I find Yarn’s API docs for that endpoint? šŸ¤” (If there is any. šŸ˜…)
@prologic Where can I find Yarn’s API docs for that endpoint? šŸ¤” (If there is any. šŸ˜…)
@prologic Where can I find Yarn’s API docs for that endpoint? šŸ¤” (If there is any. šŸ˜…)
@prologic Where can I find Yarn’s API docs for that endpoint? šŸ¤” (If there is any. šŸ˜…)
@mckinley That’s the file sharing stuff, right? I couldn’t care less about that. Frankly, I think it’s a shame that Usenet turned into that. 🫤
@mckinley That’s the file sharing stuff, right? I couldn’t care less about that. Frankly, I think it’s a shame that Usenet turned into that. 🫤
@mckinley That’s the file sharing stuff, right? I couldn’t care less about that. Frankly, I think it’s a shame that Usenet turned into that. 🫤
@mckinley That’s the file sharing stuff, right? I couldn’t care less about that. Frankly, I think it’s a shame that Usenet turned into that. 🫤
@prologic I’m so sorry, I just can’t muster up the social energy for that. šŸ˜‚ I’m sitting in video calls all week long and it’s … just … so … exhausting. I can’t, sorry. šŸ˜…
@prologic I’m so sorry, I just can’t muster up the social energy for that. šŸ˜‚ I’m sitting in video calls all week long and it’s … just … so … exhausting. I can’t, sorry. šŸ˜…
@prologic I’m so sorry, I just can’t muster up the social energy for that. šŸ˜‚ I’m sitting in video calls all week long and it’s … just … so … exhausting. I can’t, sorry. šŸ˜…
@prologic I’m so sorry, I just can’t muster up the social energy for that. šŸ˜‚ I’m sitting in video calls all week long and it’s … just … so … exhausting. I can’t, sorry. šŸ˜…
@lyse Oh, has this changed? Last time I checked, there was quite a bit of stuff going on. šŸ˜…
@lyse Oh, has this changed? Last time I checked, there was quite a bit of stuff going on. šŸ˜…
@lyse Oh, has this changed? Last time I checked, there was quite a bit of stuff going on. šŸ˜…
@lyse Oh, has this changed? Last time I checked, there was quite a bit of stuff going on. šŸ˜…
(The jenny code is getting a bit long and convoluted. I feel the need to refactor this quite a bit. That’s why I’m not implementing any of this right away.)
(The jenny code is getting a bit long and convoluted. I feel the need to refactor this quite a bit. That’s why I’m not implementing any of this right away.)
(The jenny code is getting a bit long and convoluted. I feel the need to refactor this quite a bit. That’s why I’m not implementing any of this right away.)
(The jenny code is getting a bit long and convoluted. I feel the need to refactor this quite a bit. That’s why I’m not implementing any of this right away.)
@lyse Ah, actually reading the spec helps. 🤦
@lyse Ah, actually reading the spec helps. 🤦
@lyse Ah, actually reading the spec helps. 🤦
@lyse Ah, actually reading the spec helps. 🤦
(Btw, I deliberately don’t join #yarn.social all the time. If I did, I suspect that a couple of development discussions would move over from twtxt to IRC. 🤪 Okay, and I often prefer slow asynchronous communication.)
(Btw, I deliberately don’t join #yarn.social all the time. If I did, I suspect that a couple of development discussions would move over from twtxt to IRC. 🤪 Okay, and I often prefer slow asynchronous communication.)
(Btw, I deliberately don’t join #yarn.social all the time. If I did, I suspect that a couple of development discussions would move over from twtxt to IRC. 🤪 Okay, and I often prefer slow asynchronous communication.)
(Btw, I deliberately don’t join #yarn.social all the time. If I did, I suspect that a couple of development discussions would move over from twtxt to IRC. 🤪 Okay, and I often prefer slow asynchronous communication.)
Btw, it’s kind of annoying that we have two syntax options for this. šŸ˜†

It can be

(#hash) @

or

@ (#hash)

The latter is from an earlier convention/spec. How about deprecating or even removing this?

https://dev.twtxt.net/doc/twtsubjectextension.html
Btw, it’s kind of annoying that we have two syntax options for this. šŸ˜†

It can be

(#hash) @

or

@ (#hash)

The latter is from an earlier convention/spec. How about deprecating or even removing this?

https://dev.twtxt.net/doc/twtsubjectextension.html
Btw, it’s kind of annoying that we have two syntax options for this. šŸ˜†

It can be

(#hash) @

or

@ (#hash)

The latter is from an earlier convention/spec. How about deprecating or even removing this?

https://dev.twtxt.net/doc/twtsubjectextension.html
Btw, it’s kind of annoying that we have two syntax options for this. šŸ˜†

It can be

(#hash) @

or

@ (#hash)

The latter is from an earlier convention/spec. How about deprecating or even removing this?

https://dev.twtxt.net/doc/twtsubjectextension.html
@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?