# 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/snshtcq
tkanos
twtxt.net
View Thread
For now I :
- follow in conf file (according to twtxt.txt config specification)
- follow in twtxt.txt local file (according to metadata specification)
- send a follow request to yarn server.

BUT maybe I should change the approach for something more like :

SendFollowRequestYarnServer(nick, url)
if err {
  // aka not using yarn or connection issue
  AddToLocalConf(nick, url)
  AddToTwxtFile(nick, url)
} else {
  SyncServerAndFile() // sync metadata + twts
}

Syncing about it .... I mean Thinking about it :D
What do you think @prologic ?
prologic
twtxt.net
View Thread
@tkanos I think this approach makes a lot of sense to be honest. It's probably what I'd do.
prologic
twtxt.net
View Thread
@tkanos I think this approach makes a lot of sense to be honest. It's probably what I'd do.
tkanos
twtxt.net
View Thread
Thnaks @prologic, it's always better to have 2 brains that one. I will do so. Thanks