Stefan Mai
Stefan Mai
This package is huge and leaving us with wondering whether posthog is worthwhile given we're eating very real consequences from Google on mobile LCP. Any updates on this?
@corywatilo Tags would be awesome. If each insight can select tags, and the annotations are assigned a tag, that fills my need!
There are indeed lots of options! There's several use-cases buried so I think working backwards from them makes sense: 1. Multiple Hydration - In these use cases, we may have...
I threw together some of these ideas in #4489 @helmturner . It's pretty messy but I think it touches on several of the same ideas you mention above. In particular,...
> I think you might be getting a little to preoccupied with the implementation details (which are quite fun I agree, it's not every day that we have a genuine...
This is great @helmturner , basically what I had in mind. Returning a Promise rather than AsyncGenerator in the resolver makes sense but I ran into typing challenges in implementation...
My 2 cents here: don't over-engineer it. The missing use-case is a `stream` not an `infinite stream` (which is solved by subscription). Doing some sort of delta encoding or sending...
@NielsRogge you are amazing. Thank you for this!
Super, super cool! Some high-level thoughts from running this in prod: 1) I needed to add some sort of heartbeat which was sent every few seconds and just ignored by...
Another thing I found useful was retaining the `query` and `mutation` methods in the client, but having them instead just use the *last value*. This meant I could re-use the...