Tracked on the status page now posthogstatus.com/us?inciden…

@posthog It seems like us.i.posthog.com may be having issues? Seeing timeouts and flag compute failure flags in responses. No notes on status page yet.

One of these days, someone is going to craft a supply chain compromise to trigger on and infect a widely adopted package being updated to patch a critical vulnerability. It's the logical way to maximize uptake as people panic to upgrade. That day will be a very bad day.

Is the emerging cybersecurity wave going to be this generation of engineer's Y2K?

First you want to have some kind of data capture in place, there are a lot of commodity tools that can do that for you already (sales email logging, call transcription, etc). With that then you basically need something that "reads" all the unstructured data to recover missing records. The hard part is mostly how you do that at very high scale in a cost effective, reliable, accurate way while still applying a level of reasoning and judgement to what is relevant to recover, and then how important that was to the deal in question in context. We've spent a long time working on those problems, with more to go, but what we see already is that many orgs have most of the data the need somewhere but it needs that reconstructive process to be legible.

I've lived in the CLI for so long... also pure text / TUI is less distracting.