Avatar
BlackCoffee
683211bd155c7b764e4b99ba263a151d81209be7a566a2bb1971dc1bbd3b715e

seriously, i've put hundreds of hours into this. don't just take it and profit off someone else's hard work. contribute or gtfo.

Free as in libre, not gratis!

who has a lilygo t display s3 and would be up for alpha testing and contributing to this hardware nostr connect project?

"why AI didn't live up to the hype"

To be fair, it's very useful for many things and I use it frequently.

i'll have a look but I've never touched haskell and expect my head would actually explode

It's to avoid having to open multiple channels to increase liquidity. It's an onchain tx so AFAIK no difference in cost to a std onchain tx.

Correct, it's non custodial. When you need a larger channel to receive more sats, there's an onchain fee to splice in more liquidity. Phoenix does automatically, the user gets a warning in the UI if the fees will be large.

Nearly. I want to clean a few things up and then I'll open up the repo. This first version is going to need loads more work and will need to be configured from the ide but hopefully it'll get some feedback and contributors.

Receiving an email reply that's obviously ai generated makes me cringe so hard. If you want to communicate with me, at least spend the 5 seconds and mental energy to write what you mean rather than making me decrypt the ai content you sent me.

Gm. Here is a 6 second demo of how much better the hardware nostr connect signer is now I've killed some hours in performance optimisations.

Feels good man. https://video.nostr.build/e71a138f7375b41b144422625ae098f6444fca89bd3e514989746bf0adaecfbb.mp4

Sometimes it feels like the esp32 isn't enough and then I realise just how powerful it is and just how bad my c++ is.