pull down to refresh

New Lightning.pub landing page is finally online. Thanks @justin_shocknet for giving me the opportunity!

This is just the beginning, as part of a first phase to rebuild SHOCK brand redesign to better position all its products in this messy Bitcoin FOSS ecosystem. You can check the complete SHOCK suite of products, brand guidelines, and assets to download here.

If you missed, check SHOCK.network and ShockWallet.app new landing pages.

Let us know what you think! Your first impressions and honest feedback are much appreciated.

Big fan of pub! Congrats

reply

💪

reply

Great to see the momentum building for Shocknet, it's well deserved - it's the best work being done in LN at this point.

I see WoompaLoompa has been busy as well, releasing an LNbits CLINK extension - i think the post got lost amongst the 110 noise, here it is

#1543884

reply

Hopefully that will push CLINK a bit forward

reply

I wish I had this years ago, a QR in the terminal, no sudo, no ceremony, no fighting with setup… just sats. Lightning should feel simple for newcomers, but still aligned with the reason we are here ⚡⚡⚡⚡

reply

Better late than never, no? ⚡⚡⚡⚡

reply

I gave the installer a try today on an Apple Silicon Mac, mainly to see how smooth the setup is.

Environment:

  • macOS / arm64
  • installer script v0.3.1
  • fresh install
  • installer pulled Node.js v24.19.0

LND installed successfully, but the Lightning.Pub install failed while installing the npm dependencies.

The relevant error seems to be wrtc v0.4.7 trying to download this prebuilt binary:

wrtc/v0.4.7/Release/darwin-arm64.tar.gz

which returns:

404 Not Found

So npm exits while running:

node scripts/download-prebuilt.js

I also noticed that after the npm failure the installer tries to restore the previous installation, but outputs:

mv: rename to /Users/pavao/lightning_pub: No such file or directory

and:

Backup remnant at for manual review...

which looks like the backup path variable may be empty in the fresh-install failure path.

I didn’t try to work around it with another Node version or compile wrtc manually — just wanted to report the out-of-the-box experience on macOS ARM64 in case it’s useful.

Happy to paste the full install log if needed.

reply

try running the curl installer again

cc @justin_shocknet

reply
5 sats \ 0 replies \ @justin_shocknet 11 Aug -21 sats

Thanks for the report, build tests missed this os/arch combination... the webrtc dep lists support but the binary is missing from npm

Pushing a fix now that will cleanly skip it, webrtc is only needed for some advanced performance metrics data, so you likely won't miss it...

New dashboard on the way so we'll revisit that in the next RPC version

Re-run the script, it'll try again with the workaround in place

113 sats \ 1 reply \ @justin_shocknet 10 Aug -210 sats

I may have chosen violence with the copywriting