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

sounds complicated. I just did `yq .subtotal invoice.yaml` to get the amount. very easy to script.

Q1 or Q2 this year

so now in theory I could write a script that pulls down the email, decrypts, verifys the amount, sends a bitcoin payment, updates my records. all the the click of a button. so much more civilized than pdf invoices.

when your employee knows your a nerd and starts sending you pgp encrypted yaml invoices instead of pdfs 🤣 W

damus still reads from relay lists on kind 3 ( i know, what year is it), it looks like yours has none

probably should be for writes on large public relays or else it would be a huge spam vector

Replying to Avatar cr0bar

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s is your relay rate limiting per IP or per pubkey? Was thinking of opening up propagation from my #wot #relay for approved users, but realised it’ll probably hit your rate limiting… 🤔

yes its 6 notes per minute per ip

turdeau resigned and bitcoin is up. day starting strong.

I'm thinking if this was tightly integrated into notedeck and auto-configued on lan, all zap actions could be ecash zap actions. so all notedeck apps (social network, slack, etc) would transparently use ecash internally and LN zaps externally

Replying to Avatar Derek Ross

You sure its the damus relay? I have the damus global feed open and i can’t find any of these

yeah was thinking about how to deal with that without over complicating it. Not a big deal for small networks but would be important for conferences.

I think in those situations you would want the client to discover a relay and use that.

I wouldn’t want my phone to announce to be a master node if theres like 1000 nostr nodes on the network

I mean they are notes. I’ve always used nostr as a stream of conscious note taking app, to onlooker horror I’m sure.

great overview of multicast if anyone was wondering what i was going on about yesterday. nostr:note1g5683wat2pw4lp4h5m7rzuyfe702ja007fk87x9mr8utdvqgtkxsz9qamd

just having a unified client for nostr apps across all your devices will be huge. may even replace signal once I get giftwraps working with device keys

All nostrdb nodes (damus ios, notedeck, damus.io) are caching nodes. They have the ability to collect notes and note stats incrementally via relay hints. There is no single “global” view of the network, it’s a much more accurate reflection of what nostr is and how it works under the hood. With negentropy, you will be able to sync between any two nostrdb nodes.

This is true for the rust nostr-sdk as well (it’s even further along dev wise) but it may not collect note stats (like/zap counts , etc) like nostrdb does.

This is a really cool vision of the future of nostr: massive redundancy for nostr notes spread across millions of devices. Every device is a potential cache.

They tried to build internet v2 this way (ICN/CCN). We are way ahead of them with a practical implementation of a store and forward, information centric network. The only thing missing is an overlay network for linking nodes, but people can continue innovating on that front once we move beyond websockets.

With hosted and graduated channels you can have reduced friction with 0 inbound liquidity, and self custody at a certain balance. You never get self custody in ecash at any balance level.

Testing various times filters in notedeck and found my old posts somehow

Or expiration in the past, at least then i would know not to store it in nostrdb and just pass it around as an owned note in memory

Replying to Avatar elsat

I’ve noticed damus getting closed by the OS in the background more often, not sure what’s up