# 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 3
# self = https://watcher.sour.is/conv/mldsula
Every now and again Chrome (on macOS on my iMac) gets to a point where basically no hostname resolves, like at all. Everything times out, as-if something is wrong with my network or the internet or DNS or something. But, a quick restart fixes that. Seems like there is a bug in Chrome whereby having Chrome running for long periods of time exhibits and exposes this bug.

Anyone else observe this? 🤔
Every now and again Chrome (on macOS on my iMac) gets to a point where basically no hostname resolves, like at all. Everything times out, as-if something is wrong with my network or the internet or DNS or something. But, a quick restart fixes that. Seems like there is a bug in Chrome whereby having Chrome running for long periods of time exhibits and exposes this bug.

Anyone else observe this? 🤔
Only time something like that has happened on my end is if browser got updated while its running (trough package manager). But I only run firefox..