wednesday wednesday wednesday. we’ve done 50 of these and i’m running out of ways to introduce them. whatever, you know the format by now.
quick note before we continue: we’ve disabled the ability to “pause collection” on cohost plus subscriptions. we misunderstood the function and it turns out several of you have been getting plus for free! whoops! that’s our bad. no one’s in trouble (except eggbug, who gave us bad financial advice) but we will be cancelling the subscriptions of everyone with paused collection. you can resubscribe whenever you want.
patch notes time for real now.
- finalized funding for the first half of the year!
- our growth has been so spiky lately that we opted to only fund the first 6 months in this pass so that we have more data on how growth will stabilize by the time we need to revisit.
- same funder as before, same terms as before (it’s a bond, they do not have any ownership stake in the company.)
- afaik, they still want to be anonymous (to y’all. we obviously know who they are) but they are active on the website enjoying the fruits of their funding.
- we’ll talk more about this in the next financial update
- i just remembered that i forgot to write the january financial update. whoops. gonna get that out soon.
- Fixed a bug where .beat timestamps were off by one
- Also added centibeats.
- Fixed a bug where things that look like mentions would be processed as mentions, even when they were part of links.
- This created invalid HTML (nested anchors! you can’t do that!) and made it impossible to link to things like https://internet-ti.me in a way that didn’t require weird hacks
- lots of .beat related changes this week
- we’re seeing some bugs related to this where occasionally normal mentions won’t be detected. we’re looking into the cause of this and should have a fix out soon.
- Fixed some bugs related to the post render cache we launched last week
- Namely, we were accidentally caching the content that would be seen by the first person to attempt to view a post, regardless of if they were allowed to see it. Due to some extra double-checking we do to keep from accidentally leaking posts who people who shouldn’t be able to see them, this could cause posts to be incorrectly cached as empty when they contained content.
coming up on cohost
- jae: finishing touches on the new HTML and markdown guide, silencing individual posts, some assorted bug fixes, and the first bits of our public API authentication system
- on PWYW cohost plus: we’ve made the decision to push this back a bit to line up its release with some new cohost plus features we have in the works. we’ll have more to say here once it’s closer.
- colin: 2fa!
- at this exact moment: backporting some changes to our general login and session management structure so that jae can use it as a base for API authentication
- aidan: also 2fa and Other Things
- kara: still burning away at the ticket stack. the number is getting smaller every day. it was a pretty fuckin big backlog.
that’s all for this week! we shifted our sprints to be wednesday aligned to make writing these much easier going forward. can’t wait to reap the rewards of that change.
thanks for using cohost! 
