I'm building that, but it takes longer than i thought. I've been fighting many subtle bugs, race conditions, web quirks etc. Not blossom but dev's outbox relays (files are small and chunked if needed), any static website works but can't use service worker (cause it would require a server). An app is unable to auto-update itself. Sooner than later.. é verdade esse bilete

Yes, I'm gonna use passkeys to help simplify nostr key management when accessing nostr apps. The will be importable/exportable. All the pieces are almost in place to put it online for everyone to test. I just need to go back to drinking coffee or someone to whip my back. Passkeys have become better with time. We don't need Apple/Google/MS/some-linux-distro-support anymore. E.g. Bitwarden (can be self-hosted) has a browser extension and native apps, supports passkeys and syncs keys across devices no matter the OS.

This is 10/10

Ok I guess no1 tested it.. back to finishing other views

oh hooo dude, let me tell you: bending passkeys for storing and retrieving nostr keys does work! browser extensions no more. very soon!

What if an app was able to embed another app specialized on loading all kinds of nostr events by just adding an iframe set to "44billion.net/+/whatever-inner-route/kind-2653?primary-color=purple"? Soon tm I think that the one that builds such nostr "special app" to load event kinds, if well done thus used by other apps, kinda will dictate what is the "official" event structure for each nostr kind.

This week I tested it with Jumble's source code and after some bug fixes... it works perfectly! Yeah you can upload anyone else's code easily or just use official Jumble, if the Jumble's dev chooses to upload it. Later, there will even be a 'draft' release channel if say a vibe coding platform wants to upload and show a preview before really publishing a vibe coded app to the 'main' channel. 1 or 2 weeks tops to finish and integrate the signer module and it's ready for demo. \o\

oh the web! a popover is opened with a custom longpress event. when the touch/click is released, the browser-controlled backdrop receives a pointerup event and immediately auto-closes the popover. All cool, except that the pointerup event isn't exposed to the js, thus can't be canceled. damn, these kinds of unimportant problems keep slowing me down.