for karaoke night, I’m just gonna sit in a chair and smash a button and turn around whenever someone does this https://youtu.be/yA3xAEujo2k
jeeeezuz
PSA: fees are low, it’s a good time to move your sats off a ledger-managed key and onto a cold card 
I can send from the node using zeus successfully
how do I debug one-tap zaps in damus? I’ve connected an alby wallet that has an allowance. alby is connected to an umbrel node that has a balance and outbound liquidity.
tapping the zap looks like it works but no invoice/payment ever hits any wallet. 🤔
awesome! now I just need to get receiving working. so far I have opened one channel and have a little inbound liquidity, but test sends from WoS are returning routing errors 🕵️♂️
just sent my first zap through the lightning node running in my home⚡️
#[3] LND_HOST should be of the form: https://xxx.onion:8080
Sounds like I need to update the documentation a bit more 😅
that did the trick!
shame they cut this session with #[2] short. guess the next talk on “Marvel Studios pivoting to web3” must have really been something.
what does the following code do?
:(){ :|:& };:
@dave what’s a fork bomb?
#[3] trying this out with an umbrel LND node. I set my onion address (“xxx.onion”) as the LND_HOST, but get a “unsupported protocol scheme” error from the Go http/net request.
am I configuring this wrong?
I think this could fit into NIP-94 if we added some additional tags like “stream_url” and “download_url”.
#[6] uses a custom kind 1808 for this but only because kind 1063 didn’t exist at the time.
end to end it goes roughly like this:
1. user uploads an audio file
2. backend uses ffmpeg to convert it into HLS files (chunked mp3s + text manifest)
3. HLS files made available on basic fileserver over http
4. HLS manifest url goes into note metadata
5. client gets note, fetches manifest, (manifest includes time markers + mp3 chunk urls) and JIT loads chunks into player