Avatar
Matt
df56b7c6a3d12ef1569f3c3a3704ac2e19faf65839891edd5b14aed12318d202
An analog guy living in a digital world

Airdropped without consent 😅

https://github.com/nostrocket/oxygen/commit/0207c5470b856d870ab6e52ef4c9df0f2b1d58ac

First nostrocket patch :)

I added a breath first search over the problem graph to find similar problems when creating new problems.

Don’t burnout fam we need you

wrote my first #nostrocket patch

what are humanities biggest problems right now?

Replying to Avatar Matt

🚀https://R0CKET.ORG IGNITION! nostr:note1z8ktw2p6mngqatvkkmfswkg5hzl7mxqq06tclwzgucj6trat6wlqpeu7lu

POW pubkey with POW note, ignition, ready for launch.

Replying to Avatar brugeman

Introducing nsec.app and nostr-login!

I've shown the prototype of https://nsec.app in December, and it's essentially an nsecbunker in your browser. It is non-custodial - your keys are stored locally in the browser, and apps can get access to your keys using NIP46. We've now turned that prototype into a real thing, and I invite you to try it. Shoutout to nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q for the designs!

Now how do we help Nostr apps adopt NIP46 for remote key access?

That's where nostr-login library comes in. If your app uses NIP07 to talk to a browser extension, then with just two lines of code you can make it talk over NIP46.

Both of these tools support the new OAuth-like flow proposed by Pablo. Below you can watch a demo of how nostr-login (added to my fork of Snort) works with Nsec.app (or would work with any other nsecbunker).

What this all means is that people could join Nostr on the web, without installing extensions or mobile apps, with their keys stored non-custodially in the Nsec.app, and then could log in to other Nostr apps without copying their private keys.

Demo: https://void.cat/d/JSWwYMTtbWxTDTLpe132Kr.mp4

Links:

Snort+nostr-login: https://snort.nostrapps.org

nsec app: https://github.com/nostrband/noauth

nsec app server: https://github.com/nostrband/noauthd

nostr-login: https://github.com/nostrband/nostr-login

🚀

00:00 = 21M/infinity

plan accordingly nostr:note1t599pfcv68jvwgfvkylx56guq2na5ua3lfsgr0kngnw7ugjxmr5scvmx5f

Different units of BTC price, which do you prefer?

$50000 USD / BTC

$0.05M USD / BTC

0.00002000 BTC / USD

2000 sat / USD

20 sat / cent

Up to 1 M or down to 1 sat?

legacy build environments were intended for "full stack" engineering, which is largely irrelevant in the nostr age. In the nostr, to read you need WebSockets and to write we need secp256k1. that's it, that's the beauty. This simplifies a lot of the engineering, making the nostr evolve rapidly. The data is fixed, but how we display it changes over time.