# 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 30
# self = https://watcher.sour.is?uri=https://twt.nfld.uk/user/support/twtxt.txt&offset=30
Pod upgrade, to 0.10.0, in a few minutes.
And we're back. There was a conflict with the default dark mode, so I ended up removing it for now. If you find yourself blinded by the light theme, you can enable dark mode under your user settings. Give me a shout if you get stuck!
Upgrading to yarn.social 0.6.2 shortly. Shouldn't be down long.
Apologies for the extended downtime. Normal service is now restored.
SYSTEM NOTICE: Pod going down for maintenance. I'm going to attempt moving it over to my Pi 3A, so this outage will be longer than usual.
SYSTEM NOTICE: Pod going down for upgrade in five minutes
Service restored
Apologies for the downtime; there were a few complications, but all should be well now. Please comment on this conversation if you notice any issues. Ta!
Pod going down for upgrade at 15.45 BST (five minutes from now)
And, we're back.
Note that the new branding for the project will begin to creep in over time. If you see a *yarn* or *yarn.social* here or there, don't be alarmed: that's our new name for the *twt.social* project.
Pod is going down for an upgrade in a few minutes, at 17.00 UTC.
My apologies for the recent downtime. It's still related to the reverse proxy (#schwesa); but I've now taken the additional step of configuring a restart parameter in the system service for it, so, hopefully, things will run relatively smoothly, without manual intervention.
Service restored at approximately 7am BST. Apologies for the downtime. The problem was with my Internet service provider. I'm not sure how long things were down -- I was asleep -- but they seem to have been rather prompt in correcting the issue, on this occasion.
@support OK, I've updated the reverse proxy configuration in a manner that I hope will be more tolerant of upstream flakiness; we'll see. Side note: this is the first easily-pronounceable conversation hashtag I can recall seeing. :-D
FYI, there's an outside chance that nfld may become unreachable periodically. It's a bug in the reverse proxy configuration. It only crops up occasionally, and I am investigating. Sorry for any inconvenience. I'll keep you all updated.
UPGRADE COMPLETE. Please reply to this post if you notice any issues. Ta!
UPGRADE NOTICE. Pod going down in five minutes (17.15 BST).
Another pod update. Please reply to this yarn if you notice any issues. Ta!
Sorry nfld: didn't give notice of the downtime. The good news is... We're back! Any issues, please reply to this yarn.
@support Sorry: that merge didn't go smoothly. But we're back! :-D
ATTN: pod update in a few minutes. We'll be on the master branch again now, but, as always, please reply to this twt if you notice anything unusual. Thanks!
@support And... we're back. :-) Again, this is an experimental branch of the code, so please reply to this conversation if you notice anything unusual. Thanks!
ATTN: Another pod update is imminent. This one is experimental, testing out custom pod logos.
@support Update complete. Please reply to this if youโre experiencing any issues.
ATTN: Pod going down at approximately 12.30am UTC (for a significant update).
@support Update complete. Please reply to this if you're experiencing any issues.
ATTN: Pod going down at 2pm UTC (to apply the latest updates)\nShouldn't be down too long ๐ค
Well, not a flawless update, but it *is* in hand. (Follow title, if you're curious.) Things may be unstable for a bit, folks. I'll take the pod down (again, briefly, hopefully) once a fix is ready.
(BIG sigh of relief) ๐ Certbot upgrade, from 0.40 to 1.11.0, complete. All three certificate renewal dry-runs, successful. OK, nfld pod will be down -- for a very short time, I hope -- while I get a certificate for it and reconfigure its base URL. ๐ค