# 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 43
# self = https://watcher.sour.is/conv/wkjlotq
quark
ferengi.one
View Thread
I am noticing that Yarn doesn't treat "outside" (that is, twts coming from a client other than Yarn) twts hashes right. Two examples:

- https://twtxt.net/twt/mwtnrna
- https://twtxt.net/twt/fl5dooq

There are many more, but those two will give you the gist. Yarn links the hash to the poster's twtxt.txt, so conversation matching will not work.
fastidious
twtxt.net
View Thread
@quark the same twts, as rendered by jenny:\n\n
prologic
twtxt.net
View Thread
Sorry I’m not sure what you’re saying here… Twt Hashes are very consistent
prologic
twtxt.net
View Thread
Sorry I’m not sure what you’re saying here… Twt Hashes are very consistent
fastidious
twtxt.net
View Thread
@prologic did you click/tap on one of the twts linked, then clicked/tapped on the #hash?
prologic
twtxt.net
View Thread
Hmmm I see 🤔 I’m not even sure where those links are coming from 😳 I’ll dig in to it tomorrow 👌
prologic
twtxt.net
View Thread
Hmmm I see 🤔 I’m not even sure where those links are coming from 😳 I’ll dig in to it tomorrow 👌
prologic
twtxt.net
View Thread
I’m only seeing this happen on replies from @movq and @quark 🤔
prologic
twtxt.net
View Thread
I’m only seeing this happen on replies from @movq and @quark 🤔
fastidious
twtxt.net
View Thread
@prologic @movq @quark that’s why I said twts from other clients were being treated as a second class citizen. 😂 How about @lyse?
prologic
twtxt.net
View Thread
Nope, not being treated as a 2nd class citizen at all 🤣 There it is right there in their feeds!

From @movq :


2021-10-16T12:12:18Z	@<quark https://ferengi.one/twtxt.txt> (#<nqde4uq https://ferengi.one/twtxt.txt>) No idea, sorry, I’ve never customized mutt’s colors to that extent. 🤔



From @quark :


2021-10-16T12:05:31Z	(#<nqde4uq https://ferengi.one/twtxt.txt>)
Oof! I found a bug on Yarn's Markdown rendering, @<prologic https://twtxt.net/user/prologic/twtxt.txt>. See OP.



I guess something has changed in jenny?
prologic
twtxt.net
View Thread
Nope, not being treated as a 2nd class citizen at all 🤣 There it is right there in their feeds!\n\nFrom @movq :\n\n
\n2021-10-16T12:12:18Z\t@<quark https://ferengi.one/twtxt.txt> (#<nqde4uq https://ferengi.one/twtxt.txt>) No idea, sorry, I’ve never customized mutt’s colors to that extent. 🤔\n
\n\nFrom @quark :\n\n
\n2021-10-16T12:05:31Z\t(#<nqde4uq https://ferengi.one/twtxt.txt>)\nOof! I found a bug on Yarn's Markdown rendering, @<prologic https://twtxt.net/user/prologic/twtxt.txt>. See OP.\n
\n\nI guess something has changed in jenny?
prologic
twtxt.net
View Thread
Nope, not being treated as a 2nd class citizen at all 🤣 There it is right there in their feeds!

From @movq :


2021-10-16T12:12:18Z	@<quark https://ferengi.one/twtxt.txt> (#<nqde4uq https://ferengi.one/twtxt.txt>) No idea, sorry, I’ve never customized mutt’s colors to that extent. 🤔



From @quark :


2021-10-16T12:05:31Z	(#<nqde4uq https://ferengi.one/twtxt.txt>)
Oof! I found a bug on Yarn's Markdown rendering, @<prologic https://twtxt.net/user/prologic/twtxt.txt>. See OP.



I guess something has changed in jenny?
prologic
twtxt.net
View Thread
@movq I _thought_ we were dropping the #<hash url> linking of Twt Subject Hashes now? 🙃
prologic
twtxt.net
View Thread
@movq I _thought_ we were dropping the #<hash url> linking of Twt Subject Hashes now? 🙃
prologic
twtxt.net
View Thread
@fastidious \n\n> How about @lyse ?\n\n@https://lyse.isobeef.org/twtxt.txt> 's client is doing the _right_ thing :\n\n
\n2021-10-15T23:30:00+02:00\t@<quark https://ferengi.one/twtxt.txt> (#lhi6wda) Sure. I'm currently just supporting Markdown links to include them in the URLs view so I can operate on them. Media still show the bang in front of them. But it's good enough for now. ;-)\n
prologic
twtxt.net
View Thread
@fastidious

> How about @lyse ?

@lyse 's client is doing the _right_ thing :


2021-10-15T23:30:00+02:00	@<quark https://ferengi.one/twtxt.txt> (#lhi6wda) Sure. I'm currently just supporting Markdown links to include them in the URLs view so I can operate on them. Media still show the bang in front of them. But it's good enough for now. ;-)

prologic
twtxt.net
View Thread
@fastidious

> How about @lyse ?

@lyse 's client is doing the _right_ thing :


2021-10-15T23:30:00+02:00	@<quark https://ferengi.one/twtxt.txt> (#lhi6wda) Sure. I'm currently just supporting Markdown links to include them in the URLs view so I can operate on them. Media still show the bang in front of them. But it's good enough for now. ;-)

lyse
lyse.isobeef.org
View Thread
@quark @fastidious @prologic Yeah, jenny's subject hash links seem to be off in regards to the URL.
quark
ferengi.one
View Thread
@prologic \nAh, I see! The format (or specification) for the twtxt.txt file hasn't changed as of late, right?
quark
ferengi.one
View Thread
@prologic
Ah, I see! The format (or specification) for the twtxt.txt file hasn't changed as of late, right?
movq
www.uninformativ.de
View Thread
@prologic Oh, the URL part is being dropped? I missed that. It makes a lot of sense to do that, so I’ll make the change in jenny soon. 👌

Right now, jenny sometimes has to make up those URLs, because there simply is no cross-platform way of creating them. URLs like https://twtxt.net/search?tag=gjt7pqa only exist on yarn.social, but there’s no equivalent on my web site … so, yeah, that’s probably where those bad links are coming from.

I guess we should update https://dev.twtxt.net/doc/twtsubjectextension.html accordingly. (Or maybe there’s a PR already, haven’t checked.)
movq
www.uninformativ.de
View Thread
@prologic Oh, the URL part is being dropped? I missed that. It makes a lot of sense to do that, so I’ll make the change in jenny soon. 👌

Right now, jenny sometimes has to make up those URLs, because there simply is no cross-platform way of creating them. URLs like https://twtxt.net/search?tag=gjt7pqa only exist on yarn.social, but there’s no equivalent on my web site … so, yeah, that’s probably where those bad links are coming from.

I guess we should update https://dev.twtxt.net/doc/twtsubjectextension.html accordingly. (Or maybe there’s a PR already, haven’t checked.)
movq
www.uninformativ.de
View Thread
@prologic Oh, the URL part is being dropped? I missed that. It makes a lot of sense to do that, so I’ll make the change in jenny soon. 👌\n\nRight now, jenny sometimes has to make up those URLs, because there simply is no cross-platform way of creating them. URLs like https://twtxt.net/search?tag=gjt7pqa only exist on yarn.social, but there’s no equivalent on my web site … so, yeah, that’s probably where those bad links are coming from.\n\nI guess we should update https://dev.twtxt.net/doc/twtsubjectextension.html accordingly. (Or maybe there’s a PR already, haven’t checked.)
movq
www.uninformativ.de
View Thread
@prologic Oh, the URL part is being dropped? I missed that. It makes a lot of sense to do that, so I’ll make the change in jenny soon. 👌

Right now, jenny sometimes has to make up those URLs, because there simply is no cross-platform way of creating them. URLs like https://twtxt.net/search?tag=gjt7pqa only exist on yarn.social, but there’s no equivalent on my web site … so, yeah, that’s probably where those bad links are coming from.

I guess we should update https://dev.twtxt.net/doc/twtsubjectextension.html accordingly. (Or maybe there’s a PR already, haven’t checked.)
lyse
lyse.isobeef.org
View Thread
@movq Exactly, @prologic told me in IRC about this the other day, so I adjusted tt. Prior to that I just generated twtxt.net/conv URLs for the subject hash link. If I feel like it tomorrow, I'll send a MR. But please, you can go for it as well. :-)
prologic
twtxt.net
View Thread
@lyse Yeah as discussed on IRC we don’t need to expand Twt Hashes into the feed anymore but just let clients linkify them client-side as some UX feature ; e.g link to a search instance
prologic
twtxt.net
View Thread
@lyse Yeah as discussed on IRC we don’t need to expand Twt Hashes into the feed anymore but just let clients linkify them client-side as some UX feature ; e.g link to a search instance
prologic
twtxt.net
View Thread
@quark No we haven’t changed it at all! 👌 But we have extended it wiyh backwards compatible extensions 👍
prologic
twtxt.net
View Thread
@quark No we haven’t changed it at all! 👌 But we have extended it wiyh backwards compatible extensions 👍
movq
www.uninformativ.de
View Thread
Should be fixed on jenny’s main now. 🥳
movq
www.uninformativ.de
View Thread
Should be fixed on jenny’s main now. 🥳
movq
www.uninformativ.de
View Thread
Should be fixed on jenny’s main now. 🥳
prologic
twtxt.net
View Thread
@movq Nice one 👌
prologic
twtxt.net
View Thread
@movq Nice one 👌
lyse
lyse.isobeef.org
View Thread
@movq Looking good.
quark
ferengi.one
View Thread
@movq \nDo I need to do a search and replace on my feed to fix old entries? Thanks for quick fix!
quark
ferengi.one
View Thread
@movq
Do I need to do a search and replace on my feed to fix old entries? Thanks for quick fix!
movq
www.uninformativ.de
View Thread
@quark Fixing old entries is tricky and I wouldn’t do it. If you change something in an old twt, it will change its hash sum – and thus, it will break threading if someone has replied to your old twt or otherweise referenced it. 😵
movq
www.uninformativ.de
View Thread
@quark Fixing old entries is tricky and I wouldn’t do it. If you change something in an old twt, it will change its hash sum – and thus, it will break threading if someone has replied to your old twt or otherweise referenced it. 😵
movq
www.uninformativ.de
View Thread
@quark Fixing old entries is tricky and I wouldn’t do it. If you change something in an old twt, it will change its hash sum – and thus, it will break threading if someone has replied to your old twt or otherweise referenced it. 😵
quark
ferengi.one
View Thread
@movq \nOh, OK, then not touching it. I will consider it part of history and, thus, unchangeable. 😊
quark
ferengi.one
View Thread
@movq
Oh, OK, then not touching it. I will consider it part of history and, thus, unchangeable. 😊