# 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 17
# self = https://watcher.sour.is/conv/gxh3f7a
@quark Nothing wrong with asking. 😊 I think I might actually implement more aggressive subject “compression”. We should be able to remove those subject hashtags, they’re just noise. 🤔
@quark Nothing wrong with asking. 😊 I think I might actually implement more aggressive subject “compression”. We should be able to remove those subject hashtags, they’re just noise. 🤔
@quark Nothing wrong with asking. 😊 I think I might actually implement more aggressive subject “compression”. We should be able to remove those subject hashtags, they’re just noise. 🤔
@movq \n>We should be able to remove those subject hashtags, they’re just noise.\n\nYes! I would say they are not even needed on the web UI. You click conversations, and that's done by Yarn. No need for humans to see it.
@movq
>We should be able to remove those subject hashtags, they’re just noise.
Yes! I would say they are not even needed on the web UI. You click conversations, and that's done by Yarn. No need for humans to see it.
@quark I tend to agree less emphasis or hiding the Twt Subject Hash altogether is doable and perhaps a nicer experience 👌
Escept when it’s not and someone uses an old client and does the old by-convention thing of (re foonar) 😂
@quark I tend to agree less emphasis or hiding the Twt Subject Hash altogether is doable and perhaps a nicer experience 👌
Escept when it’s not and someone uses an old client and does the old by-convention thing of (re foonar) 😂
@quark I tend to agree less emphasis or hiding the Twt Subject Hash altogether is doable and perhaps a nicer experience 👌\n\nEscept when it’s not and someone uses an old client and does the old by-convention thing of (re foonar) 😂
@prologic\n\n> Escept when it’s not and someone uses an old client […]
\n\nOther clients will see the hash, this is not about removal but hiding it here, on the web interface.
@fastidious Yes as I said, I _think_ it's quite doable. I was just merely pointing out that the whole Twt Subject was _actually_ derived from an observed convention, so we formalized it. Most things we've done were either done out of an observation of common use in the wild by Twtxt users or a way to extend the very limited Twtxt spec in the first place to _actually_ be useful 😂
@fastidious Yes as I said, I _think_ it's quite doable. I was just merely pointing out that the whole Twt Subject was _actually_ derived from an observed convention, so we formalized it. Most things we've done were either done out of an observation of common use in the wild by Twtxt users or a way to extend the very limited Twtxt spec in the first place to _actually_ be useful 😂
Without breaking old clients or humans just reading a twtxt.txt file 😂
Without breaking old clients or humans just reading a twtxt.txt file 😂
Maybe I am not clear. Hiding the hash would not break anything, because it would still be there, as it is today. When, and if, @movq hides it in jenny it will still be there, we just will not see it.