staff
@staff

happy thursday! patch notes were delayed a day this week as jae was out sick yesterday and we were dealing with some serious performance issues caused by a load-bearing vendor having nearly a full day of downtime (#hugops to them). we also had some pretty serious performance issues overnight, which we’ve resolved and are figuring out some Permanent Lessons from.

given all this, patch notes are light this week; lots of time is being spent on infrastructure changes and improvements in response to recent downtime and performance issues. the company has also been collectively hit by a bad case of Havana Syndrome, meaning our overall availability has been low. cohost is a marathon, not a sprint, and we need to stay healthy and rested for the long haul.

here’s what’s new:

  • many assorted infrastructure changes
  • fixed a bug where resetting your password would return an error that the password was not changed, even when the password was changed
  • internal moderation and support tooling improvements

we’ve decided to stop including a “coming up on cohost” section for the time being. our priorities have been shifting into more ad-hoc work recently in response to performance issues, and it’s not great for anyone to list features that get continuously pushed back.

that said, nothing we’ve talked about has been cancelled, just delayed a bit. two-factor authentication, the public API, and other features we’ve talked about are still happening, just more slowly than we’d like. additionally, the new financial update should be out tomorrow; jae still has to write it and they’ve been having serious difficulty with their chronic hand pain lately.

also, our support backlog is shrinking by the day and is likely to be cleared up soon! kara wrote a few words and shared a cool graph about it here: https://cohost.org/kaara/post/1144579-support-backlog

that’s all for this week! thanks, as always, for using cohost.


You must log in to comment.

in reply to @staff's post: