Unfortunately not, love TAB but I've got a conflict locally

Nostr is natures way of healing the Lightning network

Review the PR!

https://github.com/nostr-protocol/nips/pull/1529

I'm pleased to announce that we've finally opened the pull request for NIP-68, Lightning Debit Requests.

These ad-hoc debit requests, when combined with NIP-69 offers, provide a more intuitive, secure, and scalable successor to NWC that actually leverages Nostr for identity of Apps and Services.

Pairing an app is now as simple as entering a Lightning-enabled NIP-05 address and clicking Approve or Deny in your wallet.

The implementation is live in ShockWallet's PWA and Android build with iOS coming later this week.

A temporarily forked nostr-tools is also available for ease of integration.

Check out this UX sample: https://m.primal.net/LPAk.mp4

Reject bolt12, embrace nip69

Stick Caddy on a cheap VPS, can then do lots of other things with it too

Yea and I actually recall someone making the point it should have been binary

Ultimately it's the implementations that make the rules, the idea of bouncing signed data off webservers is as old as the web itself... Nostr just made it simple for midwits to understand so they could feel like contributors... that came at the cost of a larp army obsessed with retarded specs, not implementing shit that actually works

Nostr can only succeed if there's a broadly useful SDK, which imo has to have commercial motives

Both nostr-tools and strfry have less stars than the NIPs, that's the inversion to watch for, because they are what provide actual utility

Specs are meaningless without implementations, particularly nostr specs where they're generalized json and websocket schemas that are indistinguishable from every other app on the Internet

I believe that's a limitation of their node software not nwc itself, we so things differently with lightning.pub so each user wallet can have there own or multiple nip69 offers/lightning addresses

That's how we use it in ShockWallet, but it makes NWC redundant, the lightning address bridge server uses it to get the invoice from the node

Example implemented here:

GitHub.com/shocknet/bridgelet

Thanks, investigating...

It's supposed to but is also very new, what are you experiencing?

actually looks like there was a nav regression... just merged a fix, will have a build shortly

Under notifications there will be a reminder to back up credentials once you receive sats, click this it will take you to auth... otherwise there should be an auth link in the hamburger menu

You're not the first to point out this is unintuitive... trying to design something cleaner...

Yes, use the backup/recover screen to auth and that will enable sync over Nostr

ShockWallet.app

Can use it to onboard noobs to your own lightning.pub

Relays are no different than postgres in a traditional stack, they "relay" data across time in (conjunction with middleware)

Ditto is right because it introduces proper middleware rather than clients speaking equivalent to SQL directly, and relegates the relay back to its core database functionality.

The mastodon influence im not a fan of, but it's directionally correct to have application middleware between clients and the database (relay)

performance and scalability are coming

Nostr is literally websockets and json, things that make up the web already.

Relays are just databases, things that make up applications already.

Just because you don't know how to scale them doesn't make them not scalable, and as far as I know there's only one developer actually working on scaling it nostr:npub1yxprsscnjw2e6myxz73mmzvnqw5kvzd5ffjya9ecjypc5l0gvgksh8qud4

Scale will come quickly ones its made a priority.

Yea thats fine for short-term rate-limiting defense against DoS, but doing anything reputational with IP's beyond that will hurt new users even worse in the long run

Tiering works well in many environments, for example you can still allow new users with no friction but also impose a basic rate limit (or kind restrictions), with upgrades to those permissions achievable either via a PoW flow, WoT-invite flow, or just good behavior heuristics over time