# 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 12
# self = https://watcher.sour.is/conv/3evndzq
movq
www.uninformativ.de
View Thread
Hmm, @prologic / @lyse: Should we remove the section “Traditional Human-Readable Topics” from the spec? Or mark is as deprecated? I haven’t seen this being used in the wild for years. 🤔
movq
www.uninformativ.de
View Thread
Hmm, @prologic / @lyse: Should we remove the section “Traditional Human-Readable Topics” from the spec? Or mark is as deprecated? I haven’t seen this being used in the wild for years. 🤔
movq
www.uninformativ.de
View Thread
Hmm, @prologic / @lyse: Should we remove the section “Traditional Human-Readable Topics” from the spec? Or mark is as deprecated? I haven’t seen this being used in the wild for years. 🤔
prologic
twtxt.net
View Thread
@movq I _think_ we should because:

- it doesn't scale
- it doesn't make a terrible lot of sense anymore

It started out to be useful, but generally is probably considered "small scale" and "legacy" IMO.
prologic
twtxt.net
View Thread
@movq I _think_ we should because:

- it doesn't scale
- it doesn't make a terrible lot of sense anymore

It started out to be useful, but generally is probably considered "small scale" and "legacy" IMO.
darch
neotxt.dk
View Thread
@prologic if it to be removed, then yarn should not hide the (tags) in these posts as well as collapsing them into treads as is the case now:
- https://neotxt.dk/twt/jouh5xa
- https://neotxt.dk/twt/yy3cr5q
- https://neotxt.dk/twt/dja53eq
- https://neotxt.dk/twt/wovpq6a
lyse
lyse.isobeef.org
View Thread
@movq I need to think about it a bit. But I tend to deprecation rather than removal.
lyse
lyse.isobeef.org
View Thread
@movq @prologic I just reread the spec and it seems to be even a bit outdated regarding machine-parsable conversation grouping. We long dropped the need to specify a whole hash tag with URL (#<hash url>), the simplified version without the URL (#hash) is enough.

The hash tag extension specification is kind of missing the same. However, I'm not sure if that short form is considered supported in general (as opposed to be a special case for subjects only) by the majority of the twtxt/yarn community.

Now the question arises, in order to keep things simple, should we even only allow the simplified twt hash tag for subjects and forbid the long version? This would also save quite a bit of space. The URL is probably not shown anyways in most clients. And if so, clients might rewrite URLs to their own instances. On the other hand, there's technically nothing wrong with the long version in current parser implementations. And deprecating stuff without very good reason isn't cool.
prologic
twtxt.net
View Thread
@lyse I definitely think we should drop the longer form that involved a full url.

Also given that there's a growing number of clients that support this, I'd consider it pretty accepted nowadays.
prologic
twtxt.net
View Thread
@lyse I definitely think we should drop the longer form that involved a full url.

Also given that there's a growing number of clients that support this, I'd consider it pretty accepted nowadays.
xuu
txt.sour.is
View Thread
Agree. we should parse the form but not output to feeds.
xuu@dev.txt.sour.is
dev.txt.sour.is
View Thread
Agree. we should parse the form but not output to feeds.