# 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/y5mliwq
Missed the Artemis launch due to a big outage at work. 🫤
Missed the Artemis launch due to a big outage at work. 🫤
Missed the Artemis launch due to a big outage at work. 🫤
@movq Oh, I didn't think of that. Cool logo animation: https://www.nasa.gov/specials/artemis/

Did you have a power or network outage?
@movq ohh you can rewatch it. It was nice. SO MUCH FIRE!
@lyse Nice logo indeed. 😁 It was a network outage. Well, the root cause was not in *our* network, but we had to find ways to avoid the broken path. It would have been a trivial task, if we didn’t need said broken path to reconfigure some routers … Chicken and egg. In the end, someone went into a server room and we instructed him via video chat on what to do. In situations like these, it’s really bad if the more experienced network guys all work from home. 🥴

(Please don’t ask why we have such a single point of failure in the first place. It’s a sad story. 🙄)

@carsten Rocket goes whoosh! 😅 I did rewatch it by now. There’s nothing like following it live, though.
@lyse Nice logo indeed. 😁 It was a network outage. Well, the root cause was not in *our* network, but we had to find ways to avoid the broken path. It would have been a trivial task, if we didn’t need said broken path to reconfigure some routers … Chicken and egg. In the end, someone went into a server room and we instructed him via video chat on what to do. In situations like these, it’s really bad if the more experienced network guys all work from home. 🥴

(Please don’t ask why we have such a single point of failure in the first place. It’s a sad story. 🙄)

@carsten Rocket goes whoosh! 😅 I did rewatch it by now. There’s nothing like following it live, though.
@lyse Nice logo indeed. 😁 It was a network outage. Well, the root cause was not in *our* network, but we had to find ways to avoid the broken path. It would have been a trivial task, if we didn’t need said broken path to reconfigure some routers … Chicken and egg. In the end, someone went into a server room and we instructed him via video chat on what to do. In situations like these, it’s really bad if the more experienced network guys all work from home. 🥴

(Please don’t ask why we have such a single point of failure in the first place. It’s a sad story. 🙄)

@carsten Rocket goes whoosh! 😅 I did rewatch it by now. There’s nothing like following it live, though.
@lyse Nice logo indeed. 😁 It was a network outage. Well, the root cause was not in *our* network, but we had to find ways to avoid the broken path. It would have been a trivial task, if we didn’t need said broken path to reconfigure some routers … Chicken and egg. In the end, someone went into a server room and we instructed him via video chat on what to do. In situations like these, it’s really bad if the more experienced network guys all work from home. 🥴

(Please don’t ask why we have such a single point of failure in the first place. It’s a sad story. 🙄)

@carsten Rocket goes whoosh! 😅 I did rewatch it by now. There’s nothing like following it live, though.
@movq Oh dear. Well, luckily you got it resolved eventually. :-) +@carsten Didn't watch all of it, but that's quite cool. Suddenly, cables appearing, or pipes or whatever: https://www.youtube.com/watch?v=qxMqWHCTqGM#t=28m