# 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 15588
# self = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=12106
# next = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=12206
# prev = https://watcher.sour.is?uri=https://www.uninformativ.de/twtxt.txt&offset=12006
@aelaraji lol 😅🙈
@aelaraji lol 😅🙈
@aelaraji lol 😅🙈
@aelaraji lol 😅🙈
I think I’m not going to query Yarn pods for the moment. Let’s first see how often I’d actually need that. 🤔
I think I’m not going to query Yarn pods for the moment. Let’s first see how often I’d actually need that. 🤔
I think I’m not going to query Yarn pods for the moment. Let’s first see how often I’d actually need that. 🤔
I think I’m not going to query Yarn pods for the moment. Let’s first see how often I’d actually need that. 🤔
@quark Yay 🥳
@quark Yay 🥳
@quark Yay 🥳
@quark Yay 🥳
@lyse That is one crazy looking mushroom. 😳 How about tasting it? 🤪

I’m so glad the temperatures were down a bit. Went on a long walk as well, first time in weeks. And there were so few cars yesterday! It was surprisingly quiet.
@lyse That is one crazy looking mushroom. 😳 How about tasting it? 🤪

I’m so glad the temperatures were down a bit. Went on a long walk as well, first time in weeks. And there were so few cars yesterday! It was surprisingly quiet.
@lyse That is one crazy looking mushroom. 😳 How about tasting it? 🤪

I’m so glad the temperatures were down a bit. Went on a long walk as well, first time in weeks. And there were so few cars yesterday! It was surprisingly quiet.
@lyse That is one crazy looking mushroom. 😳 How about tasting it? 🤪

I’m so glad the temperatures were down a bit. Went on a long walk as well, first time in weeks. And there were so few cars yesterday! It was surprisingly quiet.
There was a garbage bag incident last night and I had to clean up the kitchen for two hours. 😂 Now I’m sore as fuck. Good thing I have a day off today, huh? 🤪
There was a garbage bag incident last night and I had to clean up the kitchen for two hours. 😂 Now I’m sore as fuck. Good thing I have a day off today, huh? 🤪
There was a garbage bag incident last night and I had to clean up the kitchen for two hours. 😂 Now I’m sore as fuck. Good thing I have a day off today, huh? 🤪
There was a garbage bag incident last night and I had to clean up the kitchen for two hours. 😂 Now I’m sore as fuck. Good thing I have a day off today, huh? 🤪
@falsifian @bender I pushed an alternative implementation to the fetch-context branch. This integrates the whole thing into mutt/jenny.

You will want to configure a new mutt hotkey, similar to the “reply” hotkey:

macro index,pager C "\\
set my_pipe_decode=\\$pipe_decode nopipe_decode\\
jenny -c\\
set pipe_decode=\\$my_pipe_decode; unset my_pipe_decode" \\
"Try to fetch context of current twt, like a missing root twt"

This pipes the mail to jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If there’s no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)

The whole thing looks like this:

https://movq.de/v/0d0e76a180/jenny.mp4

In other words, when there’s a missing root twt, you press a hotkey to fetch it, done.

I think I like this version better. 🤔

(This needs a lot of testing. 😆)
@falsifian @bender I pushed an alternative implementation to the fetch-context branch. This integrates the whole thing into mutt/jenny.

You will want to configure a new mutt hotkey, similar to the “reply” hotkey:

macro index,pager C "\
set my_pipe_decode=\$pipe_decode nopipe_decode\
jenny -c\
set pipe_decode=\$my_pipe_decode; unset my_pipe_decode" \
"Try to fetch context of current twt, like a missing root twt"

This pipes the mail to jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If there’s no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)

The whole thing looks like this:

https://movq.de/v/0d0e76a180/jenny.mp4

In other words, when there’s a missing root twt, you press a hotkey to fetch it, done.

I think I like this version better. 🤔

(This needs a lot of testing. 😆)
@falsifian @bender I pushed an alternative implementation to the fetch-context branch. This integrates the whole thing into mutt/jenny.

You will want to configure a new mutt hotkey, similar to the “reply” hotkey:

macro index,pager C "\
set my_pipe_decode=\$pipe_decode nopipe_decode\
jenny -c\
set pipe_decode=\$my_pipe_decode; unset my_pipe_decode" \
"Try to fetch context of current twt, like a missing root twt"

This pipes the mail to jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If there’s no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)

The whole thing looks like this:

https://movq.de/v/0d0e76a180/jenny.mp4

In other words, when there’s a missing root twt, you press a hotkey to fetch it, done.

I think I like this version better. 🤔

(This needs a lot of testing. 😆)
@falsifian @bender I pushed an alternative implementation to the fetch-context branch. This integrates the whole thing into mutt/jenny.

You will want to configure a new mutt hotkey, similar to the “reply” hotkey:

macro index,pager C "\
set my_pipe_decode=\$pipe_decode nopipe_decode\
jenny -c\
set pipe_decode=\$my_pipe_decode; unset my_pipe_decode" \
"Try to fetch context of current twt, like a missing root twt"

This pipes the mail to jenny -c. jenny will try to find the thread hash and the URL and then fetch it. (If there’s no URL or if the specific twt cannot be found in that particular feed, it could query a Yarn pod. That is not yet implemented, though.)

The whole thing looks like this:

https://movq.de/v/0d0e76a180/jenny.mp4

In other words, when there’s a missing root twt, you press a hotkey to fetch it, done.

I think I like this version better. 🤔

(This needs a lot of testing. 😆)
@prologic Yeah, I need to clean this up in jenny. It still supports a ton of old formats that aren’t used anymore at all. 🧟
@prologic Yeah, I need to clean this up in jenny. It still supports a ton of old formats that aren’t used anymore at all. 🧟
@prologic Yeah, I need to clean this up in jenny. It still supports a ton of old formats that aren’t used anymore at all. 🧟
@prologic Yeah, I need to clean this up in jenny. It still supports a ton of old formats that aren’t used anymore at all. 🧟
@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 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 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 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