Way to own the mistake @scott.hanselman.com , appreciate you for actually being serious about it and report it as it is. I think we all know there was a main instigator here which made some quick bucks out of this, regardless of the author behaviour.

Wanderer, Half Life Alyx, A Fisherman’s Tale!

Well said! But where the shit posting, come on! This isn’t LinkedIn!!! 😝😝😝 Take care Simon 😎

First things first! Make a webxr browser that has passthrough access!

Yep! Actually yours are good. It gave me a hard time as I’m now more used to English than Italian!

Italian: Impara a creare stupende interazioni e ritocchi straordinari usando la magia di CSS, JavaScript, SVG e Canvas.

Qui condivido tutti i miei segreti!

Oh I see, than you’d filter, and the filter option in useMutationState now makes sense! Thanks for helping!

Ohh that’s interesting, does that mean the state will be different for each of the mutate calls? If I call it twice with different arguments I mean, would I get individual caches, or would the second override the first (given same mutationKey)?

On my Vision Pro, I scrolled to this post on the native app and it crashed 🥹🥹 @danabra.mov

You would think this could be done by AI by now 🤔

This for me was everything that put me off on caring about web3 at all. 100% agree with you there. Always users first!

Hey there! I’m a Lead Engineer with experience working on web platform / i18n / performance / frontend architecture / full stack development / principal engineering.

I’d love to connect!

I miss it a lot, it’s what kept me on Twitter for that long and it has helped me too in learning more and becoming better indirectly.