@jamespotter@GregRay42 I just had a quick look at the support ticket from March (25919), looks like we ended up solving it for you at the time anyway (and you seemed happy). anything else that went wrong?
@jamespotter@GregRay42 honestly we’ve invested a ton on quality in the last year and it’s gotten way better, you should give us another try! i’ll have a look at the tickets
@whereischarly@djkesu1 we thought the tabs would make posthog feel more powerful/useful to do real work in but sounds like the feedback is the opposite!
Introducing PostHog Code, the product editor that:
- Understands your product
- Identifies usage patterns
- Triages bugs and errors for you
- Creates PRs to fix them
- Continuously monitors and improves your product
Join the waitlist: https://t.co/pTuwqCzo1I
@vectorpunks@BenLeaPH@posthog Of all the emails that this attacker sent, only 0.04% had existing PostHog accounts and there are no other signs of a breach, so I can confirm that your email address being hit here was a coincidence
we're working on fixing the abuse path. sorry!