iris
cmd
cmd
cmd@proof0.work
proof0.work
noisyeagle2@primal.net
I build cool stuff on bitcoin and nostr.
User Avatar
Followed byNunyaBidness, Petite Fish, Vitor Pamplona and 13 others you follow
PostsRepliesMediaLikes
User Avatar
Uneven Mammal
Isn't that what NWC is for? Just because it's RPC doesn't mean everything has to go through the signer interface. I'm also not sure what the use case for a bidirectional session would be. Maybe key migration? But even then, it seems like that would be better served by a method that explicitly does t
... show more
0
0
cmd
DLCs and mints come to mind.
0
0
0
User Avatar
Uneven Mammal
The JSON RPC stuff is nasty, but it is what it is for interop reasons now. How would bunker/nostrconnect be unified? They're two completely different flows (imo nostrconnect is much nicer than pasting a bunker in most cases). Interested to see what you come up with.
0
0
cmd
I don't think they are that different. Both strings are using URI schemes and share many of the same arguments. It's just a matter of who initiates the authentication flow. If everyone runs something like NIP-46 (including client sites) then it essentially becomes sessions + permissions managment f
... show more
0
0
0
User Avatar
Big Barry Bitcoin
Why are you saying this? We have been through the ringer already with people crying that ecash is not an L3, that all layers should have unilateral exists, even calle has said that ecash is not a L3, it is a custodial system that can work on top of bitcoin. Are you trying to start shit?
0
0
cmd
why does a layer need to have a unilateral exit?
0
0
0
cmd
NIP-46 could use some love. It's on the precipice of being something great. The bunker and nostrconnect stuff can be unified into a single token for establishing authenticated sessions between peers. The JSON-RPC stuff can be fleshed out more, with proper types and interfaces for request, response
... show more
0
0
0
cmd
I think ecash can market itself as "layer 3" in the magic internet money tech stack: Layer 1: Bitcoin (on-chain final settlement). Layer 2: Lightning (off-chain payment channels). Layer 3: Ecash (private banking). I feel like in this framing it makes a lot of sense, is easy to explain, and scales
... show more
0
0
0
cmd
this is absolutely wild! being able to transfer entangled quantum states across existing fiber-optic cables is a game-changer. There's a lot of interesting things you can do with entanglement and tweaking the phase of qbits if you have access to a quantum computer (like IBM and quikset). But I diwww.nature.com/articles/s41586-025-08801-w
... show more
0
0
0
User Avatar
semisol
Has been for me as well. Bunkers are still in disarray. There is no solution for ensuring bunker uptime too. Not everyone has a server to put it on, or wants to run an app that drains their battery. Connecting new apps is a pain, requiring copying a string over from your bunker (which requires you
... show more
0
0
cmd
I get that you are mad about bunkers, but let's not pretend that extensions are somehow unable to load arbitrary code at runtime (they can), or that you some-how can't build and side-load PWAs (you can). I agree with you that nsecbunker sucks. I have been building rpc-like interfaces over nostr lon
... show more
0
0
0
User Avatar
semisol
the service worker will always be updated from the backend
0
0
cmd
I have done offline installs before, I think you can just keep it local with no remote host. Both PWAs and extensions can fetch packages dynamically anyway
0
0
0
User Avatar
semisol
okay so what? I can audit what they are doing not to mention chrome and firefox have features to click-to-enable extensions on websites
0
0
cmd
click to approve code injection 😂 alright I am going to cook up a tasty PWA signing flow for you, with a nip-7 bridge for dessert. if you like it, you can help me make a safari version 😁
0
0
0
User Avatar
semisol
so all users should be beholden to one centralized signing app? also, one invisible code update can exfiltrate your nsec, and then could be removed. and you wouldn’t know
0
0
cmd
where I'm going, there won't be an nsec to exfiltrate :-) but I get your point. I think you can disable updates for installed PWAs (via the service worker)
0
0
0