pull down to refresh
688 sats \ 4 replies \ @justin_shocknet 26 Jun \ parent \ on: BOLT 12 User Stories lightning
lol, yea i'm convinced these bxlt12 people are worse than shitcoiners
All marketing, none of the understanding of why what they're pushing for is completely retarded... but somehow Lightning needs it
For those that don't know:
- It's a reinvention of Tor for invoices, too slow and unreliable for real world usage
- The privacy benefits are a hoax, Lightning has all the privacy features without it
- It's shitcoin compliant, being pushed by ECash neobanker spooks wanting to sell you EDollars
To make matters worse, they cite Nostr as a usecase when Nostr itself already obviates LNURL and Bxlt12 Offers via Kind 21000
Complete bozo's...
At least the retro-futurism theme makes sense for their marketing materials... retro like the shitty Tor implementation that it is, futurisim because it's destined for the same fate.
This is the spiciest take I've seen all month lol
https://c.tenor.com/JJCQq0eUvT0AAAAd/tenor.gif
Interestingly, your unique spelling of Bolt 12 is very search engine friendly. I found a github.
Tor as a workaround has proven too slow and unreliable, and a dead-end for clearnet-web usecases. Bxlt12, being a re-implementation of Tor, appears destined for the same fate.
reply
Shocknet FTW !
Incidentally, how do you look at other Nostr stuff for LN, such as Nostr Wallet Connect, or that recently announced Nostr Pay thing ?
Are they complimentary to what you guys are pushing towards, competition, or problematic, or what ?
reply
It's good validation that we've been on the right track, keeping in mind Nostr itself is an iteration of what we attempted with GUN for those who've been around long enough to remember Lightning.page (as is LNC for that matter), so it's all working out as expected
NWC is actually a direct response to Pub because we wouldn't implement WebLN on Lightning.Video, which is fine, I'm glad the imitators have proven our architectural concepts ;)
NWC isn't bad perse, its just a nerfed higher time preference version of kind 21000 that we could easily accommodate with an adapter if it becomes sticky.
The reason we're not just expanding on NWC is the lived experience of having implemented LNURL in the wild. Everyone implements specs in their services just a little wrong, any proposed changes to specs are bikeshed to hell, and actually writing specs before seeing how things work in a live implementation is just backwards imo.
Nostr only works to the degree it does because everyone uses nostr-tools in their projects, if every service implemented NIP's from spec, it'd be a disaster. That's a problem because more logic is required in Lightning node middleware than is in-scope for nostr-tools.
For this reason, Lightning.Pub and kind 21000 are a https://github.com/shocknet/Lightning.Pub/tree/master/proto, from which you can autogenerate a client for any language. New working methods can then be PR'd to the proto rather than the bureaucracy of higher level NIP, and work consistently across clients.
That all said, whether its our stuff or more collaborative protocols, the fusion of web relays and Lightning is the future of the internet.
My vision since 2018 first playing with lightning has been that of an open-source decentralized censorship-resistant WeChat-like stack be built around it, and that is now most definitely happening.
reply
thx for the reply - it's great to have the opportunity to learn from those with insight into all this stuff here on SN.
reply