š ļø If you haven't yet, please read the introduction and check out the bug tracker to see what weāre working on. Now onto the patch notes!
this weekās patch notes are a little bit of a format change, since weāve got few real ādeliverablesā and more of a vibe check. hereās a peek into the inner workings of anti software software club!
from the desk of @aidan
eggbug production continues apace; many new eggbugs are being discovered every single day on cohost dot org. who knows how many there are to find? not me!
as cohost dot orgās premiere influencer and tastemaker, itās been my job to design the page that youāll all see when we announce publicly and posters the world over flock to our little website. this week has been a little bit of a refactor on that front, because a lot of features and ideas weāve had over the course of development have been added, changed, or fleshed out in meaningful ways.

a few of the landing page layouts weāve been messing with
most of the above text is a placeholder, but that said, weād be happy to hear any feedback on my improvised tagline up there. what do you, the Cohost Poster, think needs to be in our elevator pitch? (rest assured, thereās a lot more website to see. thatās a secret still, though.)
from the desk of @jkap
you can give us money now! right now you donāt get anything in return, but that will be changing Soon as we finish up the first batch of actual features for cohost Plus!. the first round will mostly be smaller cosmetic things, but weāll be expanding the feature set over time to include Larger Cosmetic Things. our goal is for cohost Plus! to always have features that, while not essential to using the website, make the experience more Fun.
also, itās my birthday. no working on my birthday (besides writing this)

birthday bug
from the desk of @vogon
when jae and I started working on cohost, I was coming off a job where I worked often but not closely with react, and foolishly resolved that I wouldnāt work with react again; at the time react didnāt do server-side rendering very well, and we both hated the culture of single-page applications, so it was honestly a fairly reasonable choice.
through a circuitous route, we started using react again (for real, this time) right around the time we launched, and Iāve been paying the piper over the past week learning how to use parts of the react ecosystem that hadnāt filtered down to me when we started.
Iāve also been building out the internal APIs that allow us to add and remove editors to pages, which are implemented using tRPC, a typescript library for type-safe APIs, which Iām also new to. still making progress, though, and hope to land the moderator tooling by next tuesday.
thanks for using (and paying for, in numbers larger than we expected) cohost 
