# 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 29
# self = https://watcher.sour.is/conv/ifphkga
@movq would it be possible to trim the subject to, say, 100 or 140 characters? Just the subject.
@quark Trim the subject? 🤔 Context?
@quark Trim the subject? 🤔 Context?
@prologic \nJenny populates Mutt's subject with the entire twt. That makes for very, very long subject lines.
@prologic
Jenny populates Mutt's subject with the entire twt. That makes for very, very long subject lines.
@quark Ahh I see 😁 Yeah maybe use the Twt Subject Hash and a plain text formatted version of the Twt truncated with ellipsis at say 140 like I’ve done with yarnd’s permalink titles? 🤔
@quark Ahh I see 😁 Yeah maybe use the Twt Subject Hash and a plain text formatted version of the Twt truncated with ellipsis at say 140 like I’ve done with yarnd’s permalink titles? 🤔
@prologic \nSounds like a good plan. It is, of course, up to the Master Crafter. 😋
@prologic
Sounds like a good plan. It is, of course, up to the Master Crafter. 😋
@quark True 😆
@quark True 😆
@quark That’s on purpose and probably won’t change, I think. 🤔\n\nIf Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager. I often do that. On the other hand, if they’re truncated, then the question is: Where do you truncate them? 72, 100, 140, 200? Some people have wide terminals, others don’t. So I decided: Okay, let’s have mutt do it. 🙃 (Or you could make it a user option, but I like to avoid those, because you quickly end up with a ton of options and things get very hard to test, because I myself don’t use most of them.)\n\nThe subject lines are already “compressed”, btw. For example, a full mention like “@” gets compressed to just “@foo”. Maybe it’d be possible to expand on that idea, like also strip the hashtags of conversation grouping. 🤔
@quark That’s on purpose and probably won’t change, I think. 🤔

If Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager. I often do that. On the other hand, if they’re truncated, then the question is: Where do you truncate them? 72, 100, 140, 200? Some people have wide terminals, others don’t. So I decided: Okay, let’s have mutt do it. 🙃 (Or you could make it a user option, but I like to avoid those, because you quickly end up with a ton of options and things get very hard to test, because I myself don’t use most of them.)

The subject lines are already “compressed”, btw. For example, a full mention like “@” gets compressed to just “@foo”. Maybe it’d be possible to expand on that idea, like also strip the hashtags of conversation grouping. 🤔
@quark That’s on purpose and probably won’t change, I think. 🤔

If Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager. I often do that. On the other hand, if they’re truncated, then the question is: Where do you truncate them? 72, 100, 140, 200? Some people have wide terminals, others don’t. So I decided: Okay, let’s have mutt do it. 🙃 (Or you could make it a user option, but I like to avoid those, because you quickly end up with a ton of options and things get very hard to test, because I myself don’t use most of them.)

The subject lines are already “compressed”, btw. For example, a full mention like “@” gets compressed to just “@foo”. Maybe it’d be possible to expand on that idea, like also strip the hashtags of conversation grouping. 🤔
@quark That’s on purpose and probably won’t change, I think. 🤔

If Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager. I often do that. On the other hand, if they’re truncated, then the question is: Where do you truncate them? 72, 100, 140, 200? Some people have wide terminals, others don’t. So I decided: Okay, let’s have mutt do it. 🙃 (Or you could make it a user option, but I like to avoid those, because you quickly end up with a ton of options and things get very hard to test, because I myself don’t use most of them.)

The subject lines are already “compressed”, btw. For example, a full mention like “@” gets compressed to just “@foo”. Maybe it’d be possible to expand on that idea, like also strip the hashtags of conversation grouping. 🤔
Just for some more background: I wrote a StatusNet client years ago which worked very similar to jenny, with mutt as a frontend. That program did indeed truncate the subject lines – but it turned out to be a bit annoying in practice. It was always cut off a little bit too early. 🤣 So I eventually removed truncation altogether.
Just for some more background: I wrote a StatusNet client years ago which worked very similar to jenny, with mutt as a frontend. That program did indeed truncate the subject lines – but it turned out to be a bit annoying in practice. It was always cut off a little bit too early. 🤣 So I eventually removed truncation altogether.
Just for some more background: I wrote a StatusNet client years ago which worked very similar to jenny, with mutt as a frontend. That program did indeed truncate the subject lines – but it turned out to be a bit annoying in practice. It was always cut off a little bit too early. 🤣 So I eventually removed truncation altogether.
@movq This is the same struggle I had when designing the permalink titles 😁
@movq This is the same struggle I had when designing the permalink titles 😁
@movq Hmmm 🤔
@movq Hmmm 🤔
Apparently I still haven't got it right 😢 Getting this _right_ is super hard 😥
Apparently I still haven't got it right 😢 Getting this _right_ is super hard 😥
@movq \n>If Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager\n\nYes, I do the same, true.\n\n>So I decided: Okay, let’s have mutt do it.\n\nAnd Mutt does it well. I agree it was/is a good idea.\n\n>The subject lines are already “compressed”\n\nI noticed, yes.\n\nI am not sure why I asked to begin with; in retrospect, in was a silly request. Perhaps the OCD in me got triggered while viewing rich headers, on a specific twt, when I saw the huge subject line that is, otherwise, always hidden.\n\nAnyway, don't mind me, move along. 😂
@movq
>If Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager

Yes, I do the same, true.

>So I decided: Okay, let’s have mutt do it.

And Mutt does it well. I agree it was/is a good idea.

>The subject lines are already “compressed”

I noticed, yes.

I am not sure why I asked to begin with; in retrospect, in was a silly request. Perhaps the OCD in me got triggered while viewing rich headers, on a specific twt, when I saw the huge subject line that is, otherwise, always hidden.

Anyway, don't mind me, move along. 😂
@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. 🤔