Hello! I run a node here: https://amboss.space/node/02c83f5d0b495919c4a6ac6f5fc3310ae894b374d3deb611cc3cbfb0c39057d7b6
I'm lacking a bit of inbound liquidity and I'm also struggling to recuperate the costs of rebalancing, opening new channels etc. Suggestions?
I've been running a lightning node for years now, just started rebalancing to add liquidity to the network. I have collected 635 sats by routing and today I paid over 4000 sats in rebalance fees to keep my main channels from zeroing out.
I did a bit of research and I realized that I've got channels with people who have fee rates set at 1000x what I'm charging - looking at you, nostr:nprofile1qyv8wue69uhk6mmwv9jzu6nzx56jucm0d5arsvpcxqqs6amnwvaz7tmwdaejumr0dsqzqvhpsfmr23gwhv795lgjc8uw0v44z3pe4sg2vlh08k0an3wx3cj9zs5e6s - and I'm left unsurprised that there are people who don't believe in Lightning as a workable solution.
If you're really just getting started, open the simplest text editor available on your computer and make a file called "index.html"
Write "
Hello World
" in that file and save it. You should be able to open it up with your web browser. You should be able to start building from there.If you want to dive right into the nostr world you can add the code linked here and start scripting stuff. Nostr is a couple levels above basic HTML though.
For my project #nostr #safebox I am developing an authentication protocol which I am calling #nauth. The reason I developed this new protocol is so that either party, name initiator and recipient can initiate the protocol. I wanted to address a situation where only one party might have the ability to scan a QR code, either the patient or the physician. The QR code is merely an out-of-band initiation method, it could be a text or whatever. So here goes,
1. Initiator prepares and sends a #nauth request consisting of:
a. Initiator npub
b. nonce
c. auth kind
d. auth relays
e. transmittal kind
f. transmittal relays
2. Recipient receives #nauth request (usually by scanning a QR code). The recipient inspects the #nauth request and returns another #nauth request as a NIP-59 gift wrapped message using the specified auth kind and auth relays
a. Recipient npub
b. nonce (should be the nonce provided)
c. auth kind (may be the same or different)
d. auth relays (may be the same or different)
e. transmittal kind (may be the same or different)
f. transmittal relays (may be the the same or different)
3. The initiator, upon receiving the #nauth , inspects to see if the nonce is ok, and that the parameters are satisfactory. If so, it may provide an acknowledgment via an out-of-band indication, or through the auth kind/ relays channel proposed.
4. All secure transmittals are sent as giftwrapped messages as kind=transmittal kinds. Any subsequent authentication control messages are sent as gift wrapped messages of kind=auth kind.
BTW, I have this all implemented in #nostr #safebox for #mednostr and it is working like a charm so far. With this scheme I have 99.99999% confidence that health data records are being transmitted with no third party surveillance or model training.
nostr:npub1healthsx3swcgtknff7zwpg8aj2q7h49zecul5rz490f6z2zp59qnfvp8p
Does the nAuth scheme accomplish the same patterns of Single Sign On that OAuth has established? I've never done much work to understand the latter system, it's always seemed kind of bloated to me
What do you do with dried asparagus? It sounds like it would be good in a soup
Currently planning my 5th major revision to SOLAR. It can be really frustrating to go through this process time and again before I'm at the stage where I can start getting other people involved, but once there's multiple people standing on the foundation it gets a lot more difficult to make these sort of sweeping changes - even when it's for the best.
My current target is finding a consistent way to address nostr notes with a human readable path so that they can be stored in the correct place on a filesystem. I will be focusing mostly on addressable events, converting the
I think that the nostr community is still missing a sense of data ownership. Like yes, it's cool that everything is cryptographically signed, but at the end of the day if people aren't holding onto their own data it still leaves the door open for relays to become centralized and for people to lose sight of the wider network.
Did you manage to roll down the windows and let the wind blow back your hair while driving on an open road in the countryside? It's pretty much the only way to do it