Avatar
jb55
32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245
I made damus, npubs, and zaps ⚡️ Independent bitcoin core and lightning dev.

I may have just made the fastest lnurl server based on lnsocket-rust

it keeps a lightning/noise connection open from my VPS to my computer at home.

fetching invoices as fast as lightning...

https://cdn.jb55.com/s/fast-lnurl-lnsocket.mp4

remember cents?

I bought this pin with coinos over nwc via damus, with zaps from nostr. thanks guys!

this never gets old. we must keep building to make instant, non-custodial, decentralized payments a reality for everyone.

nostr:note19m4zh70pas6gyuvu7m7fnhfwsdfqfzh6ssy5wrcu4s4amwh37x9q3n8uw0

eventually, but it wouldn't be called delete, it would be called request delete, since clients could cache notes and ignore delete requests (like damus currently does)

i mean if every node is re-broadcasting to the nodes its connected to then in theory it should mesh ok, but i haven't looked at the code.

we hit 20 peers! worked great.

nostr:note1emv7cgw0jvd59yr9a8gt9j3y8x7ed0h32jq9j6896tcse6y5fe3q2m6000

protests, festivals, talks, schools. lots of cool use cases.

nostr:note1snza5cq6w8peslsxssaaswxphfssw22qhq39jfx9292tpz5qwg6qx80wgd

just released the rust lnsocket crate, the easiest way to connect to lightning nodes to send custom messages like commando rpc.

this is more opinionated than LDK, uses tokio+async, does way less. all it does it connect to nodes so you can send custom messages. It's great for building custom protocols on top of the lightning network.

My usecase is fetching invoices from the damus lightning node for dave and other applications. Also going to look into this for fetching bolt12 invoices in damus clients.

check it out!

https://docs.rs/lnsocket

I have had phone calls with reviewers and at no point did they say what primal is doing is a solution to their issues with my app

the amount of time I want to spend thinking about inbox or outbox relays:

you shouldn't see a repost more than once... otherwise not yet

minibits nwc barely works. We’ve been getting lots of reports on this

this is like the nostrdb binary note format but a bit more space efficient and network friendly. great for transferring notes over the wire. An 74kb contact list crunches to about 37kb. About half the size!

sizes of strings are varint encoded, but it gets better. The first bit in the encoded varint size is used to signify that it is a binary string.

It will detect any hex strings and encode them as binary and encode this hint in the size byte. You can encode the type (string/binary) and length up to 126 in a single byte (aka most things in tags).

This means large contact lists are efficiently compressed: 1 byte for length + type and 32 bytes for pubkeys in tags.

nostr:note1m9uh77q0xfavvxz40nhufrmn9n6298hs4tlzzlhuh2flw5nv3afqwqv6ra

nostr is pretty much ideal for vibe coding. you can rapidly test product ideas, and if they are good they can quickly be integrated into the wider network.

it doesn't matter if the vibe coded app is good client, what matters is the experience it showcases and the data it generates.

nostr:note1uq8t0jwmcwpz63gnj0zqavxuj27ka9t3gnymzrxfmlp6crtepmnsez4t6z

even if/when eternal September comes you can always partition yourself into private relays

nostr:note19d78gvymrdvh3uqnu5706syx3pl4tqzauffheudvp4e6qmkn3dvsq99c4c

finish the apps you build

basic idea:

systems can generate these threads via some automated process, like when someone opens a PR.

Then you can open it up in a nostr AI frontend like notedeck_dave to continue the review without losing any context

nostr:note12aqvwekqrwulx9etu57qlpl2xyn2lan8rmqje67ejwh0xpxe3zaqs5k9d2