# 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 14
# self = https://watcher.sour.is/conv/grm3u6a
sorenpeter
darch.dk
View Thread
hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt
sorenpeter
darch.dk
View Thread
hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt
sorenpeter
darch.dk
View Thread
hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt
sorenpeter
darch.dk
View Thread
hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt
bender
twtxt.net
View Thread
@soren you reach out and tell them to set a nick? Or parse the URL, and use the word right after the tilde as the nick?
prologic
twtxt.net
View Thread
@sorenpeter I think the use of ~ is so commonly used as a <username> that we should just suppose that out of the box by all clients for display purposes.
prologic
twtxt.net
View Thread
@sorenpeter I think the use of ~ is so commonly used as a <username> that we should just suppose that out of the box by all clients for display purposes.
lyse
lyse.isobeef.org
View Thread
@sorenpeter @bender @prologic Right. Also, generally speaking, if you come across a new feed URL, it's probably either via some mention in another feed or the User-Agent in your access log. Both cases typically advertise also a display name. So, you just reuse whatever you've seen there.
aelaraji
aelaraji.com
View Thread
@sorenpeter Here are two more cases:
- nick = subdomain: https://aelaraji.com/timeline/profile?url=https://lyse.isobeef.org/twtxt.txt -> lyse.isobeef.org
- nick = second level domain: https://aelaraji.com/timeline/profile?url=https://aelaraji.com/twtxt.txt -> aelaraji.com
aelaraji
aelaraji.com
View Thread
@sorenpeter Here are two more cases:
- nick = subdomain: https://aelaraji.com/timeline/profile?url=https://lyse.isobeef.org/twtxt.txt -> lyse.isobeef.org
- nick = second level domain: https://aelaraji.com/timeline/profile?url=https://aelaraji.com/twtxt.txt -> aelaraji.com
prologic
twtxt.net
View Thread
@aelaraji domains/subdomains I _think_ are much harder to "standardize" hmmm 🤔
prologic
twtxt.net
View Thread
@aelaraji domains/subdomains I _think_ are much harder to "standardize" hmmm 🤔
aelaraji
aelaraji.com
View Thread
@prologic No I'm not trying to standardize the domains themselves xD I was just hinting at filtering cases where nick is identical to a level of a domain; in order to show shorter format nicks within clients, i.e: @nick.domain.ltd or @nick.ltd instead of a @nick@nick.domain.ltd or @nick@nick.ltd. Just like what @sorenpeter already did with the nick = domain case. _(unless I'm missing the point)_
aelaraji
aelaraji.com
View Thread
@prologic No I'm not trying to standardize the domains themselves xD I was just hinting at filtering cases where nick is identical to a level of a domain; in order to show shorter format nicks within clients, i.e: @nick.domain.ltd or @nick.ltd instead of a @nick@nick.domain.ltd or @nick@nick.ltd. Just like what @sorenpeter already did with the nick = domain case. _(unless I'm missing the point)_