# 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 4
# self = https://watcher.sour.is/conv/r7orr6q
bender
twtxt.net
View Thread
@eapl.me I wouldn't call it natural, it is the way Bluesky decided to handle handles (not meaning to make a pun, or anything). There is no other way, but that.

The bottomline is, there are agreed upon "standards", right? From example, on Yarnd you show as "eapl.me", from "eapl.me". A kind of weird redundancy because on twtxt, ever since I started using it, one will expect to see a "*nick*" (equivalent to a person's first name), from "*a domain*" (like a surname).

There is nothing holding back someone from giving themselves the nick:


thisismyawesomenickforwhichiwillbeknownforeverandeveritsgreatisntit


But, do we really want that? 😅
lyse
lyse.isobeef.org
View Thread
@bender Great tits always makes for lovely nick names!

A pair of great tits, female on the left, male on the right
lyse
lyse.isobeef.org
View Thread
@bender Great tits always makes for lovely nick names!

A pair of great tits, female on the left, male on the right
bender
twtxt.net
View Thread
@lyse don't you go planting that seed around here, Mister! 😂