# 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 196314 # self = https://watcher.sour.is?offset=170699 # next = https://watcher.sour.is?offset=170799 # prev = https://watcher.sour.is?offset=170599
--fetch-context doesn’t go back into archived feeds … 🤦
--fetch-context doesn’t go back into archived feeds … 🤦
--fetch-context doesn’t go back into archived feeds … 🤦
--fetch-context doesn’t go back into archived feeds … 🤦
jenny renders this:
jenny:
From: quark <quark>
Subject: (#o) @prologic this was your first twtxt. Cool! :-P
Date: Mon, 16 Sep 2024 12:42:27 -0400
Message-Id: <k7imvia@twtxt>
X-twtxt-feed-url: https://ferengi.one/twtxt.txt
(#o) @<prologic https://twtxt.net/user/prologic/twtxt.txt> this was your first twtxt. Cool! :-P
jenny:
From: quark <quark>
Subject: (#o) @prologic this was your first twtxt. Cool! :-P
Date: Mon, 16 Sep 2024 12:42:27 -0400
Message-Id: <k7imvia@twtxt>
X-twtxt-feed-url: https://ferengi.one/twtxt.txt
(#o) @<prologic https://twtxt.net/user/prologic/twtxt.txt> this was your first twtxt. Cool! :-P
From: prologic <prologic>
Subject: Hello World! 😊
Date: Sat, 18 Jul 2020 08:39:52 -0400
Message-Id: <o6dsrga>
X-twtxt-feed-url: https://twtxt.net/user/prologic/twtxt.txt
Hello World! 😊
From: prologic <prologic>
Subject: Hello World! 😊
Date: Sat, 18 Jul 2020 08:39:52 -0400
Message-Id: <o6dsrga>
X-twtxt-feed-url: https://twtxt.net/user/prologic/twtxt.txt
Hello World! 😊
# prev = ... line. To do so, I naively wrote something along these lines:
for line in content.splitlines():
if line.startswith('# prev = '):
...
\n.
# prev = foo bar
# prev = *twice* (once in the actual header, once in a twt), didn’t know what to do, and thus did not fetch the archived feeds. 🤦# prev = ... line. To do so, I naively wrote something along these lines:
for line in content.splitlines():
if line.startswith('# prev = '):
...
\n.
# prev = foo bar
# prev = *twice* (once in the actual header, once in a twt), didn’t know what to do, and thus did not fetch the archived feeds. 🤦# prev = ... line. To do so, I naively wrote something along these lines:
for line in content.splitlines():
if line.startswith('# prev = '):
...
\n.
# prev = foo bar
# prev = *twice* (once in the actual header, once in a twt), didn’t know what to do, and thus did not fetch the archived feeds. 🤦# prev = ... line. To do so, I naively wrote something along these lines:
for line in content.splitlines():
if line.startswith('# prev = '):
...
\\n.
# prev = foo bar
# prev = *twice* (once in the actual header, once in a twt), didn’t know what to do, and thus did not fetch the archived feeds. 🤦~/.cache/jenny and my maildir_target when I tried to reset things. Still got wrecked 😅 maildir_target and give it a try with an empty directory?
~/.cache/jenny and my maildir_target when I tried to reset things. Still got wrecked 😅 maildir_target and give it a try with an empty directory?
~/.cache/jenny and my maildir_target when I tried to reset things. Still got wrecked 😅 maildir_target and give it a try with an empty directory?
~/.cache/jenny should reset everything, it doesn’t store any other state. 🤔
~/.cache/jenny should reset everything, it doesn’t store any other state. 🤔
~/.cache/jenny should reset everything, it doesn’t store any other state. 🤔
~/.cache/jenny should reset everything, it doesn’t store any other state. 🤔
--fetch-context on replays to them. your oldest is the one from 2024-06-14 18:22 ... I can see lyse's tho! but I doubt this is related the edit issue but this helps with something.
--fetch-context on replays to them. your oldest is the one from 2024-06-14 18:22 ... I can see lyse's tho! but I doubt this is related the edit issue but this helps with something.
--fetch-context on replays to them. your oldest is the one from 2024-06-14 18:22 ... I can see lyse's tho! but I doubt this is related the edit issue but this helps with something.
D tag. D tag. D tag. (r:https://...). 😅
(r:https://...). 😅
(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)#weadxga, I have no idea what that could possibly refer to.(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) has all the information you need. This could simplify twt/feed discovery quite a bit, couldn’t it? 🤔 That thing that I just implemented – jenny asking some Yarn pod for some twt hash – would not be necessary anymore. Clients could easily and automatically fetch *complete* threads instead of requiring the user to follow all relevant feeds.(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) is *so long*. Clients would have to try harder to hide this. 😅
(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)#weadxga, I have no idea what that could possibly refer to.(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) has all the information you need. This could simplify twt/feed discovery quite a bit, couldn’t it? 🤔 That thing that I just implemented – jenny asking some Yarn pod for some twt hash – would not be necessary anymore. Clients could easily and automatically fetch *complete* threads instead of requiring the user to follow all relevant feeds.(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) is *so long*. Clients would have to try harder to hide this. 😅
(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)#weadxga, I have no idea what that could possibly refer to.(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) has all the information you need. This could simplify twt/feed discovery quite a bit, couldn’t it? 🤔 That thing that I just implemented – jenny asking some Yarn pod for some twt hash – would not be necessary anymore. Clients could easily and automatically fetch *complete* threads instead of requiring the user to follow all relevant feeds.(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) is *so long*. Clients would have to try harder to hide this. 😅
(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z)#weadxga, I have no idea what that could possibly refer to.(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) has all the information you need. This could simplify twt/feed discovery quite a bit, couldn’t it? 🤔 That thing that I just implemented – jenny asking some Yarn pod for some twt hash – would not be necessary anymore. Clients could easily and automatically fetch *complete* threads instead of requiring the user to follow all relevant feeds.(replyto:http://darch.dk/twtxt.txt,2024-09-15T12:06:27Z) is *so long*. Clients would have to try harder to hide this. 😅