# 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 10
# self = https://watcher.sour.is/conv/jgi4ypa
prologic
twtxt.net
View Thread
Actually on second thoughts... I _think_ the "following" system is fine the way it is. A mapping of alias to url. I'm now following @eldersnake from three different sources 🤣
prologic
twtxt.net
View Thread
Actually on second thoughts... I _think_ the "following" system is fine the way it is. A mapping of alias to url. I'm now following @eldersnake from three different sources 🤣
prologic
twtxt.net
View Thread
I'm basically doing it like this:\n\n
\n$ curl -qso - https://twtxt.net/~prologic/twtxt.txt | grep '^# follow.*eldersnake'\n# follow = eldersnake@twtxt.net https://twtxt.net/user/eldersnake/twtxt.txt\n# follow = eldersnake@we.loveprivacy.club https://we.loveprivacy.club/user/eldersnake/twtxt.txt\n# follow = eldersnake@yarn.andrewjvpowell.com https://yarn.andrewjvpowell.com/user/eldersnake/twtxt.txt\n
\n\nSo I _think_ just prompting the user to rename a conflicting feed to another alias is probably fine....
prologic
twtxt.net
View Thread
I'm basically doing it like this:


$ curl -qso - https://twtxt.net/~prologic/twtxt.txt | grep '^# follow.*eldersnake'
# follow = eldersnake@twtxt.net https://twtxt.net/user/eldersnake/twtxt.txt
# follow = eldersnake@we.loveprivacy.club https://we.loveprivacy.club/user/eldersnake/twtxt.txt
# follow = eldersnake@yarn.andrewjvpowell.com https://yarn.andrewjvpowell.com/user/eldersnake/twtxt.txt


So I _think_ just prompting the user to rename a conflicting feed to another alias is probably fine....
prologic
twtxt.net
View Thread
I'm basically doing it like this:


$ curl -qso - https://twtxt.net/~prologic/twtxt.txt | grep '^# follow.*eldersnake'
# follow = eldersnake@twtxt.net https://twtxt.net/user/eldersnake/twtxt.txt
# follow = eldersnake@we.loveprivacy.club https://we.loveprivacy.club/user/eldersnake/twtxt.txt
# follow = eldersnake@yarn.andrewjvpowell.com https://yarn.andrewjvpowell.com/user/eldersnake/twtxt.txt


So I _think_ just prompting the user to rename a conflicting feed to another alias is probably fine....
prologic
twtxt.net
View Thread
In the meantime I can automatically create the keys for aliases to be @nick@domain so there is less chance of collision in the first place, improving the overall user experience.
prologic
twtxt.net
View Thread
In the meantime I can automatically create the keys for aliases to be @nick@domain so there is less chance of collision in the first place, improving the overall user experience.
eldersnake
we.loveprivacy.club
View Thread
I like it! Less work to refactor, I'm sure, and also Just Works. As you say, a prompt or something at least is probably all that is needed.
prologic
twtxt.net
View Thread
@eldersnake Yup ☺️
prologic
twtxt.net
View Thread
@eldersnake Yup ☺️