@colinhacks.com can you cut a release on deno.land
latest release is 3.25
deno.land/x/zod@v3.25

Raise your hand if you would trade bank accounts with a former macromedia employee.

*Epstein goes to jail*

Wealthy businessman men: www.nbcnews.com/news/amp/ncn...

You’re absolutely right! That is annoying I will try to not use this in my future responses.

What about the anti JavaScript typescript club.

What if they were called collections and they were public and everyone could see your collections.

- Bsky product manager probably.

Tesla stock is too high should be $4.20 a share.

Are you saying that these pigs are in a blanket?

rsc is the hand basket that sends your components to hell

<marquee> comes before anything else. We can support <b> tags in q4

I also got a failing grade on this project because “my code wasn’t clear enough”

github.com/BLamy/ISTE-3...

I remember there was a beautiful period of time where electron had nodeIntegration on by default in the render process no preload script and I went wild with impossible components.

Then the haters (security team) got to me.

github.com/DiamondEleme...

Inside every senior engineer there is one wolf.

But then you will miss bangers like this.

bsky.app/profile/thel...

Could I use the same passkey to be both sent to the server for login and also use it to derive my client side encryption key?

Or does that mean my server would be able to decrypt the data making it no longer zero knowledge.

That’s fair. This was mostly just a POC but will definitely look into secure recovery options if I run with this idea further.

Right now the goal is to present it to the user as a 2 factor auth step so the user experience is the same.

The fact that I’m encrypting their data is abstracted away.

The argument being that if users loose their passkey they lose access to their encrypted data?

Or is this approach some how insecure?

Apple keychain and other password managers will sync your passkeys so you can easily encrypt your data on any of your devices.