Oh man, can we hand out some annoying duck quacker toys? This has serious guerrilla marketing potential. 📣💥🪿 📣💥🪿🚀 nostr:note1qw52nhzltuc4hgad53zhv09gg4nls05zextpdy5xz68r5evsf26srryjeq
You don't need a fancy integration to take in-person Lightning payments #AlbyGo https://video.nostr.build/d32b6df95f923cc2a8b06fbb686f4ba0389eabea57b4e4289897ae9b459b0ce0.mp4
Me: Let's play a game where we explore power structures!
Claude: Hold my beer
[Ok, not really, but damn it made a beeline up the chain! I thought I was going to have to work harder]
Claude: I love this thought experiment! It's a fun way to explore power structures and dependencies, even if deliberately oversimplified. Let's trace this chain of "who can exert significant unilateral control over whom":
You (individual US citizen) →
Local Police (can arrest/detain citizens) →
City/County Government (controls police department) →
State Government (has authority over local governments) →
Federal Government (has supremacy over states) →
Voters (can vote out federal officials) →
Media/Social Media Companies (strong influence over voter opinions/information) →
Advertisers (major source of media company revenue/influence) →
Consumers (can boycott/choose products) →
Financial Institutions (control access to credit/banking) →
Federal Reserve (controls monetary policy/banking system) →
Congress (oversees Fed, can change its mandate) →
Lobbyists/Special Interests (influence over Congress) →
Wealthy Donors (fund lobbying efforts) →
...and here we might start seeing some interesting cycles and interconnections. Would you continue this chain differently? I'm particularly curious about where you think it leads - does it eventually circle back, or is there an "ultimate boss" in your view?
LOL, even hyperbitcoinization won't end the Fed
Ecash is "cloud" custody, and the cloud is always just someone else's computer. nostr:note1jfv3u6cyu8yvvrwwds7jx2qvey2dmv9fj2zk3y56s2agev8zngns5vg84w
Not really? Think of session management: there are many tokens sessions for one user. You use your credentials once to get a new credential with the same authority as the password, but if it stolen it can be revoked without compromising your password. All operations behave as if the session token is the same as the root identity, and the only work that happens when a session is disavowed is that messages signed by the session should be deleted.
I don't follow. My proposed NIP-102 uses one key to attest other keys, so it could be cold and offline. If one gets lost, you disavow it the same as NIP-22, and issue a new one. Your friends don't need to validate the rotation though.
Looks good, but I dont put much faith on this master key idea. I think a much simpler approach can be done with key rotations like on https://github.com/vitorpamplona/nips/blob/key-rotation/22.md
It's simpler, but with the same private key everywhere you'll end up burning more than you need to. Why not have a separate, cold, identity key?
You sure? https://github.com/getAlby/go/pull/250
Yeah, IIRC if you add the right entitlement to your app you can call intents on other apps, just like shortcuts does. The tread should explain what's going on, but everything is also in the AlbyGo PR. I don't personally want to maintain an app... I just want the functionality to be out there.
Nostr signer *and* in-person invoice generator? Maybe that's too many things for one app...
I was thinking of the same thing based on some recent work I did with AppIntents. It probably wouldn't work with the same URL scheme though.