# 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 16
# self = https://watcher.sour.is/conv/ibw66va
@prologic something seems to have gone wrong with twtxt.net's upload capabilities...
@marado Hmmm really? Lemme test...
@marado Hmmm really? Lemme test...
@marado Hmmm really? Lemme test...
@marado Hmmm really? Lemme test...
@marado Can you try again? I'm not completely sure what _could_ have happened there...
@marado Can you try again? I'm not completely sure what _could_ have happened there...
@marado Can you try again? I'm not completely sure what _could_ have happened there...
@marado Can you try again? I'm not completely sure what _could_ have happened there...
@prologic now it worked 🤷‍♂️
@prologic now it worked 🤷‍♂️
@marado Yeah sorry I have no idea, the _only_ thing I'm aware of that can _actually_ cause a missed 404 is when the deployment in my infra is updating, but I sort-of solved that by adding a fallback service (a sort of catch-all) that returns a 503 Service Unavailable and a maintenance page instead, so I'm not sure and looking at the deployment my pod hasn't re-deployed in over 2 days so I don't get it :/


$ dks ps twtxt_twtxt
ID             NAME                IMAGE                   NODE           DESIRED STATE   CURRENT STATE         ERROR     PORTS
wy9g3gvcfc8r   twtxt_twtxt.1       prologic/yarnd:latest   dm4.mills.io   Running         Running 2 days ago
lvur2y5kshv9    \_ twtxt_twtxt.1   prologic/yarnd:latest   dm4.mills.io   Shutdown        Shutdown 2 days ago
b3lnmd6rc3lt    \_ twtxt_twtxt.1   prologic/yarnd:latest   dm4.mills.io   Shutdown        Shutdown 2 days ago
@marado Yeah sorry I have no idea, the _only_ thing I'm aware of that can _actually_ cause a missed 404 is when the deployment in my infra is updating, but I sort-of solved that by adding a fallback service (a sort of catch-all) that returns a 503 Service Unavailable and a maintenance page instead, so I'm not sure and looking at the deployment my pod hasn't re-deployed in over 2 days so I don't get it :/


$ dks ps twtxt_twtxt
ID             NAME                IMAGE                   NODE           DESIRED STATE   CURRENT STATE         ERROR     PORTS
wy9g3gvcfc8r   twtxt_twtxt.1       prologic/yarnd:latest   dm4.mills.io   Running         Running 2 days ago
lvur2y5kshv9    \_ twtxt_twtxt.1   prologic/yarnd:latest   dm4.mills.io   Shutdown        Shutdown 2 days ago
b3lnmd6rc3lt    \_ twtxt_twtxt.1   prologic/yarnd:latest   dm4.mills.io   Shutdown        Shutdown 2 days ago
@marado Yeah sorry I have no idea, the _only_ thing I'm aware of that can _actually_ cause a missed 404 is when the deployment in my infra is updating, but I sort-of solved that by adding a fallback service (a sort of catch-all) that returns a 503 Service Unavailable and a maintenance page instead, so I'm not sure and looking at the deployment my pod hasn't re-deployed in over 2 days so I don't get it :/


$ dks ps twtxt_twtxt
ID             NAME                IMAGE                   NODE           DESIRED STATE   CURRENT STATE         ERROR     PORTS
wy9g3gvcfc8r   twtxt_twtxt.1       prologic/yarnd:latest   dm4.mills.io   Running         Running 2 days ago
lvur2y5kshv9    \\_ twtxt_twtxt.1   prologic/yarnd:latest   dm4.mills.io   Shutdown        Shutdown 2 days ago
b3lnmd6rc3lt    \\_ twtxt_twtxt.1   prologic/yarnd:latest   dm4.mills.io   Shutdown        Shutdown 2 days ago
@marado Yeah sorry I have no idea, the _only_ thing I'm aware of that can _actually_ cause a missed 404 is when the deployment in my infra is updating, but I sort-of solved that by adding a fallback service (a sort of catch-all) that returns a 503 Service Unavailable and a maintenance page instead, so I'm not sure and looking at the deployment my pod hasn't re-deployed in over 2 days so I don't get it :/


$ dks ps twtxt_twtxt
ID             NAME                IMAGE                   NODE           DESIRED STATE   CURRENT STATE         ERROR     PORTS
wy9g3gvcfc8r   twtxt_twtxt.1       prologic/yarnd:latest   dm4.mills.io   Running         Running 2 days ago
lvur2y5kshv9    \_ twtxt_twtxt.1   prologic/yarnd:latest   dm4.mills.io   Shutdown        Shutdown 2 days ago
b3lnmd6rc3lt    \_ twtxt_twtxt.1   prologic/yarnd:latest   dm4.mills.io   Shutdown        Shutdown 2 days ago
@marado Yeah sorry I have no idea, the _only_ thing I'm aware of that can _actually_ cause a missed 404 is when the deployment in my infra is updating, but I sort-of solved that by adding a fallback service (a sort of catch-all) that returns a 503 Service Unavailable and a maintenance page instead, so I'm not sure and looking at the deployment my pod hasn't re-deployed in over 2 days so I don't get it :/


$ dks ps twtxt_twtxt
ID             NAME                IMAGE                   NODE           DESIRED STATE   CURRENT STATE         ERROR     PORTS
wy9g3gvcfc8r   twtxt_twtxt.1       prologic/yarnd:latest   dm4.mills.io   Running         Running 2 days ago
lvur2y5kshv9    \_ twtxt_twtxt.1   prologic/yarnd:latest   dm4.mills.io   Shutdown        Shutdown 2 days ago
b3lnmd6rc3lt    \_ twtxt_twtxt.1   prologic/yarnd:latest   dm4.mills.io   Shutdown        Shutdown 2 days ago