# 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 196233
# self = https://watcher.sour.is?offset=174085
# next = https://watcher.sour.is?offset=174185
# prev = https://watcher.sour.is?offset=173985
What's going on?
What's going on?
Is there a bug on my side?
Is there a bug on my side?
@bender Who did that? 🤔🤣
@bender Who did that? 🤔🤣
[47°09′46″S, 126°43′29″W] Storm recedes -- back to normal work
@movq How hard would it be to implement something like (#<2024-10-25T17:15:50Z https://www.uninformativ.de/twtxt.txt>)in jenny as a replacement for (#twthash) and have it not care about if is http(s) or a g-protocol?
@movq How hard would it be to implement something like (#<2024-10-25T17:15:50Z https://www.uninformativ.de/twtxt.txt>)in jenny as a replacement for (#twthash) and have it not care about if is http(s) or a g-protocol?
@movq How hard would it be to implement something like (#<2024-10-25T17:15:50Z https://www.uninformativ.de/twtxt.txt>)in jenny as a replacement for (#twthash) and have it not care about if is http(s) or a g-protocol?
@movq How hard would it be to implement something like (#<2024-10-25T17:15:50Z https://www.uninformativ.de/twtxt.txt>)in jenny as a replacement for (#twthash) and have it not care about if is http(s) or a g-protocol?
@Codebuzz Speed is an issue for the client software, not the format itself, but yes I agree that it makes the most sense to append post to the end of the file. I'm referring to the definition that it's the first url = in the file that is the one that has to be used for the twthash computation, which is a too arbitrary way of defining something that breaks treading time and time again. And this is the case for not using url+date+message = twthash.=
@Codebuzz Speed is an issue for the client software, not the format itself, but yes I agree that it makes the most sense to append post to the end of the file. I'm referring to the definition that it's the first url = in the file that is the one that has to be used for the twthash computation, which is a too arbitrary way of defining something that breaks treading time and time again. And this is the case for not using url+date+message = twthash.=
@Codebuzz Speed is an issue for the client software, not the format itself, but yes I agree that it makes the most sense to append post to the end of the file. I'm referring to the definition that it's the first url = in the file that is the one that has to be used for the twthash computation, which is a too arbitrary way of defining something that breaks treading time and time again. And this is the case for not using url+date+message = twthash.=
@Codebuzz Speed is an issue for the client software, not the format itself, but yes I agree that it makes the most sense to append post to the end of the file. I'm referring to the definition that it's the first url = in the file that is the one that has to be used for the twthash computation, which is a too arbitrary way of defining something that breaks treading time and time again. And this is the case for not using url+date+message = twthash.=
@bender That broken mention *might* have the same cause as the other issue you mentioned. Changed URL and all that. 🤔
@bender That broken mention *might* have the same cause as the other issue you mentioned. Changed URL and all that. 🤔
@bender That broken mention *might* have the same cause as the other issue you mentioned. Changed URL and all that. 🤔
@bender That broken mention *might* have the same cause as the other issue you mentioned. Changed URL and all that. 🤔
@bender Well, I can't help it. I just saw the parse error popping up. ¯\_(ツ)_/¯

Oh, and the lang metadata field is indented with tabs, breaking the nice visual alignment._
@bender Well, I can't help it. I just saw the parse error popping up. ¯\\_(ツ)_/¯

Oh, and the lang metadata field is indented with tabs, breaking the nice visual alignment._
There might be a bug in jenny that causes it to re-fetch archived feeds on every run. Probably happens on edits/deletes. I’ll look into it soon-ish.
There might be a bug in jenny that causes it to re-fetch archived feeds on every run. Probably happens on edits/deletes. I’ll look into it soon-ish.
There might be a bug in jenny that causes it to re-fetch archived feeds on every run. Probably happens on edits/deletes. I’ll look into it soon-ish.
There might be a bug in jenny that causes it to re-fetch archived feeds on every run. Probably happens on edits/deletes. I’ll look into it soon-ish.
@lyse that's Lyse, doing god's work! :-P
@sorenpeter I like that. It pretty much matches what I already had in mind. (The implications of part two of point 0 are obviously controversial and I don’t know if we can ever agree on that. 😅)
@sorenpeter I like that. It pretty much matches what I already had in mind. (The implications of part two of point 0 are obviously controversial and I don’t know if we can ever agree on that. 😅)
@sorenpeter I like that. It pretty much matches what I already had in mind. (The implications of part two of point 0 are obviously controversial and I don’t know if we can ever agree on that. 😅)
@sorenpeter I like that. It pretty much matches what I already had in mind. (The implications of part two of point 0 are obviously controversial and I don’t know if we can ever agree on that. 😅)
@quark Oh dear. 😅 I’m one of the first around here, though. 🤪
@quark Oh dear. 😅 I’m one of the first around here, though. 🤪
@quark Oh dear. 😅 I’m one of the first around here, though. 🤪
@quark Oh dear. 😅 I’m one of the first around here, though. 🤪
@movq LOL, you are late! :-P Stores around started selling Christmas's decorations early September. Like, wow! Usually the earliest is after Halloween, more often after Thanksgiving.
@movq LOL, you are late! :-P Stores around started selling Christmas's decorations early September. Like, wow! Usually the earliest is after Halloween, more often after Thanksgiving.
Hey @Codebuzz, looks like your second twt has a broken timestamp. :-)
Time to put up the christmas decoration, I guess. 🤷✨
Time to put up the christmas decoration, I guess. 🤷✨
Time to put up the christmas decoration, I guess. 🤷✨
Time to put up the christmas decoration, I guess. 🤷✨
@quark At some point, Yarn must have fetched the feed and used the correct URL (otherwise it wouldn’t have gotten the correct hash). And at that point, it should have updated the uri field for this twt in its database, I guess? Disclaimer: I know nothing about the internals of Yarn. 😅
@quark At some point, Yarn must have fetched the feed and used the correct URL (otherwise it wouldn’t have gotten the correct hash). And at that point, it should have updated the uri field for this twt in its database, I guess? Disclaimer: I know nothing about the internals of Yarn. 😅
@quark At some point, Yarn must have fetched the feed and used the correct URL (otherwise it wouldn’t have gotten the correct hash). And at that point, it should have updated the uri field for this twt in its database, I guess? Disclaimer: I know nothing about the internals of Yarn. 😅
@quark At some point, Yarn must have fetched the feed and used the correct URL (otherwise it wouldn’t have gotten the correct hash). And at that point, it should have updated the uri field for this twt in its database, I guess? Disclaimer: I know nothing about the internals of Yarn. 😅
@movq interesting! So, what would the fix be, in this case, do you know? Aware of this, @prologic?
@movq interesting! So, what would the fix be, in this case, do you know? Aware of this, @prologic?
@quark That’s confusion on Yarn’s part, I’d say.

Yarn’s API says that twt comes from the URL http://twtxt.prismdragon.net/twtxt.txt – but when using that URL for hashing, I get the hash bjs6aua instead of mowsvgq. That’s not the correct hash, so jenny says the twt could not be found.

Inspecting the feed using jenny -D … yields the correct hash. When looking at the raw feed, we can see:


# nick = gallowsgryph
# description = Green living and permaculture enthusiast, writer, otherkin, weird.
# url = http://prismdragon.net/twtxt.txt
# url = https://dreamwidth.org/gallowsgryph/
# avatar = http://prismdragon.net/img/gallows.png#20241025


So it’s a different URL. When I use http://prismdragon.net/twtxt.txt for hashing, I get the correct hash.
@quark That’s confusion on Yarn’s part, I’d say.

Yarn’s API says that twt comes from the URL http://twtxt.prismdragon.net/twtxt.txt – but when using that URL for hashing, I get the hash bjs6aua instead of mowsvgq. That’s not the correct hash, so jenny says the twt could not be found.

Inspecting the feed using jenny -D … yields the correct hash. When looking at the raw feed, we can see:


# nick = gallowsgryph
# description = Green living and permaculture enthusiast, writer, otherkin, weird.
# url = http://prismdragon.net/twtxt.txt
# url = https://dreamwidth.org/gallowsgryph/
# avatar = http://prismdragon.net/img/gallows.png#20241025


So it’s a different URL. When I use http://prismdragon.net/twtxt.txt for hashing, I get the correct hash.
@quark That’s confusion on Yarn’s part, I’d say.

Yarn’s API says that twt comes from the URL http://twtxt.prismdragon.net/twtxt.txt – but when using that URL for hashing, I get the hash bjs6aua instead of mowsvgq. That’s not the correct hash, so jenny says the twt could not be found.

Inspecting the feed using jenny -D … yields the correct hash. When looking at the raw feed, we can see:


# nick = gallowsgryph
# description = Green living and permaculture enthusiast, writer, otherkin, weird.
# url = http://prismdragon.net/twtxt.txt
# url = https://dreamwidth.org/gallowsgryph/
# avatar = http://prismdragon.net/img/gallows.png#20241025


So it’s a different URL. When I use http://prismdragon.net/twtxt.txt for hashing, I get the correct hash.
@quark That’s confusion on Yarn’s part, I’d say.

Yarn’s API says that twt comes from the URL http://twtxt.prismdragon.net/twtxt.txt – but when using that URL for hashing, I get the hash bjs6aua instead of mowsvgq. That’s not the correct hash, so jenny says the twt could not be found.

Inspecting the feed using jenny -D … yields the correct hash. When looking at the raw feed, we can see:


# nick = gallowsgryph
# description = Green living and permaculture enthusiast, writer, otherkin, weird.
# url = http://prismdragon.net/twtxt.txt
# url = https://dreamwidth.org/gallowsgryph/
# avatar = http://prismdragon.net/img/gallows.png#20241025


So it’s a different URL. When I use http://prismdragon.net/twtxt.txt for hashing, I get the correct hash.
[47°09′12″S, 126°43′23″W] Automatic systems disengaged due to thunderstorm
I find it ironically amusing when people leaves twtxt, which anyone can, or could, read (no needs for sign ups, etc.), and move to Twitter. 🤦🏻‍♂️
@movq, having an issue fetching a twtxt context. I am getting:


Trying to fetch "#mowsvgq" from Yarn pod https://txt.sour.is ...
Trying to fetch "#mowsvgq" from Yarn pod https://twtxt.net ...
Twt could not be found


Yet, the twtxt is there: https://twtxt.net/twt/mowsvgq. Bug, or something else?
@movq, having an issue fetching a twtxt context. I am getting:


Trying to fetch "#mowsvgq" from Yarn pod https://txt.sour.is ...
Trying to fetch "#mowsvgq" from Yarn pod https://twtxt.net ...
Twt could not be found


Yet, the twtxt is there: https://twtxt.net/twt/mowsvgq. Bug, or something else?
Well, that mention didn't work. Yarn has been very unreliable on that front (amongst others). Hmm.
@gallowsgryph@gallowsgryph sometimes a fresh start is the best start!
@movq I see. If I edit it, is shows as @gallowsgryph@twtxt.prismdragon.net.
@movq I see. If I edit it, is shows as @gallowsgryph@twtxt.prismdragon.net.

WOAH! What happened here? I replied to https://twtxt.net/twt/rzuepoq, just now, and this twtxt shows "2h ago".
****
#WorldPastaDay #DiaMundialDeLaPastaRead more****
@doesnm like OP, that will not work, as it has wrong/incomplete information.
@bender This is true 🤣 I'd you don't specify one; one will be auto-generated 🤣
@bender This is true 🤣 I'd you don't specify one; one will be auto-generated 🤣
> The text parameters are percent-decoded before matching. Dash (-), ampersand (&), and comma (,) characters in text parameters are percent-encoded to avoid being interpreted as part of the text directive syntax.
> The text parameters are percent-decoded before matching. Dash (-), ampersand (&), and comma (,) characters in text parameters are percent-encoded to avoid being interpreted as part of the text directive syntax.
@doesnm "in TWTXT.net, avatars are set for you!" 😂
The specific syntax must (should) be followed as well: https://wicg.github.io/scroll-to-text-fragment/#syntax
[47°09′23″S, 126°43′48″W] Working impossible due to blizzard
Pretty bland without an avatar though 😢
Pretty bland without an avatar though 😢
@doesnm I never really thought about that to be honest 🤔
@doesnm I never really thought about that to be honest 🤔
What if i want to delete avatar? Im deleted avatar meta field but still see avatar on twtxt.net
Thanks as well @prologic 😃
Pinellas County - HM Tune Up: 6.25 miles, 00:09:31 average pace, 00:59:29 duration
hit all the paces i set out to and was not too tough. could have possibly done a longer warm up or cool down, or maybe another set, but it was all good. have not really been doing any speed work so it was a good test.
#running
Pinellas County - HM Tune Up: 6.25 miles, 00:09:31 average pace, 00:59:29 duration
hit all the paces i set out to and was not too tough. could have possibly done a longer warm up or cool down, or maybe another set, but it was all good. have not really been doing any speed work so it was a good test.
#running
Pinellas County - HM Tune Up: 6.25 miles, 00:09:31 average pace, 00:59:29 duration
hit all the paces i set out to and was not too tough. could have possibly done a longer warm up or cool down, or maybe another set, but it was all good. have not really been doing any speed work so it was a good test.
#running
@doesnm I did yes 👌
@doesnm I did yes 👌
Seems he want "get permanarely unfollowed and ignored". Btw did you unfollow him? I see follow in your feed
[47°09′01″S, 126°43′24″W] Wind speed: 56kph
Done
Done
[47°09′02″S, 126°43′00″W] Wind speed: N/A -- Cannot comunicate
@Codebuzz yarnd actually uses WebSub between pods for this reason:
@Codebuzz yarnd actually uses WebSub between pods for this reason:
@Codebuzz Yes! welcome yo the community 🙇‍♂️
@Codebuzz Yes! welcome yo the community 🙇‍♂️
@bender Maybe so but likely only recently formalized right?
@bender Maybe so but likely only recently formalized right?
@bender Same. I will also blaxklosy yhe domain shortly.
@bender Same. I will also blacklist the domain shortly.
@bender Same. I will also blacklist the domain shortly.
@Codebuzz Welcome to Twtxt 🤗
@Codebuzz Welcome to Twtxt 🤗
Ya know; Rather than being an asshole and getting all angry, just be reasonable and reach out to the community or folks fetching (or trying) your feed.

Most clients respect caching if your feed is transported I've HTTP.

Otherwise you can add the # refresh hint to clients on your feed.

No need to be an obnoxious ass and flood your own feed. That will just get you permanarely unfollowed and ignored.
Ya know; Rather than being an asshole and getting all angry, just be reasonable and reach out to the community or folks fetching (or trying) your feed.

Most clients respect caching if your feed is transported I've HTTP.

Otherwise you can add the # refresh hint to clients on your feed.

No need to be an obnoxious ass and flood your own feed. That will just get you permanarely unfollowed and ignored.
Welcome! Glad you found our little corner of the internet.
🧮 USERS:1 FEEDS:2 TWTS:1133 ARCHIVED:80031 CACHE:2456 FOLLOWERS:17 FOLLOWING:14
On my blog: Real Life in Star Trek, The Next Phase https://john.colagioia.net/blog/2024/10/24/next-phase.html #scifi #startrek #closereading