Andreas Thomas

Will be fixed here, thanks for creating the issue to track it! https://github.com/unkeyed/unkey/blob/178797b7ae91327130d7299a21695c863d9abaee/apps/api/src/routes/v1_keys_createKey.ts#L49

Good point, we should expand the docs! Before we do, what do you mean by "wrapped" data? ___ and regarding this: > so a malicious customer could easily consume the...

This has been requested in the past and we probably need to find a good way to do it, that protects users as much as possible while offering a way...

Encryption per workspace is definitely good yeah. I'd maybe go as far and give the user the encryption key and not store it ourselves. Because if someone has access to...

This one is just a parent issue for multiple smaller ones, see above

#93 is indeed being worked on, but we'd love examples in any framework/tool tbh what's your favourite one?

using buf? sounds cool

Sure sounds good

can you create one please

I have never used svelte, but you could use the `Receiver` manually, right? ```ts import { Receiver } from "@upstash/qstash" const receiver = new Receiver({ currentSigningKey: "...", nextSigningKey: "...", });...