just a basic fileserver, in our case it’s implemented in Go but you could use an S3 bucket or whatever. just needs to be accessible over http
🔥 we implemented HLS for streaming audio in #[7] for a couple reasons:
- chunked audio encoding doesnt send full sourcefile to browser. enables monetization (no right click save)
- works across devices and browsers
- same protocol used by e.g. soundcloud
- open standard
- scales extremely well, just static files
- also supports video
would love if the eventual NIP for audio had support for robust streaming like this. I’m no expert but I’ve spent a good amount of time on our HLS implementation - happy to answer questions or contribute!
I love this! have you thought about streaming protocols or is that outside of scope? looking forward to the nip!
knucks 👊 👊
P A P A M I L F
I will be basic in your honor 🫡
interesting idea! wonder if a crowdfunded greeter bot would be feasible or if it would just get gamed 🤔
ie make payments frictionless and intuitive for folks new to btc/ln. this is the power of the nostr network and deserves critical design thinking
zap/payment components!
damn. it worked for me but disclaimer I only used it for a day or two. if you find a good solution lmk!
I was posting a ‘developer update’, based on what I’ve worked on today.
The project is here: https://github.com/hugomd/lnd-nostr-zapper
The TL;DR; is: lnd-nostr-zapper is an application you can self-host to receive nostr zaps to your self-hosted Lightning Network Daemon (LND) node.
E.g. if you run an Umbrel node (https://umbrel.com), you could run this to receive zaps directly.
this is awesome and the go code looks great! TIL sjson. looking forward to giving this a try 🤙
it’s sunny in the pnw! hope everyone has a wonderful weekend 🌞
box on the cursor. this looks dope cant wait to try
