If any part of this stream on how threading works was interesting, don’t miss @dzwdz finding several more ridiculously fiddly bugs in every ‘clever’ piece of this code. It’s not just because this code is bug-prone, but I noted in a GitHub comment that maybe we want to redo how Lobsters sorts comments.

On a meta note, we should probably figure out some rule of posting these streams to the site. I have planned that they’ll all have relevant meta discussion and the code itself is generally topical. But two posts a week is a lot, especially because streaming is low density compared to other site content, even compared to other video content like talks and interviews. I especially don’t want to turn the homepage into The Pushcx Show, yeeesh. (This has also been why I’ve blogged less the last couple years.)

I was offline this Monday so I didn’t post to the weekly thread as planned, but maybe that’s a good place for links to the stream archive. Each Monday I’ll post what I plan to stream and then link back to the previous week’s streams. Then to prevent submissions I’d ban my blog domain or links that start https://push.cx/stream (that’d be a custom Story validation, but it’d allow a clear message explaining the practice). And then for site health, if a user feels a stream has something worth a top-level meta discussion, we’ll say it’s ok to make a meta post with the link in the text. I dunno, this is fairly complicated. Maybe someone can come up with a very different approach that’s better here?