Custodial services providing a zap (NIP-57) compatible LNaddress I know of:
Bitcoin Beach Wallet - #[5] support Zaps also.
Bitcoin Jungle - #[6]
LightningTipBot - https://ln.tips
Good point! Added the zapper pubkey to NIP-05 and broadcasted the identifier and relays with iris.to
Added these steps to the guide to be done manually for now.
If you click my profile should see the latest LNaddress set: ligess@diynodes.com
Experimented with a few others lately.
Could be a stuck relay or browser cache. Also ligress is requesting the invoice over Tor so can be flaky.
My best betvis to try in a new browser.
Other can zap ok as shown on the post.
Ligess is a self-sovereign Lightning Address and Zap (NIP-57) server: https://github.com/Dolu89/ligess/
To use it you need:
* an always on lightning node (eg. a Raspiblitz)
* a (sub)domain under your control
* a VPS with a public IP address to avoid exposing the location of your node
A 5 minute guide to set up with your own node: https://github.com/openoms/bitcoin-tutorials/blob/master/nostr/ligess.md
H/t #[0] for adding the Zap support
You can try it by zapping this post ;)
Found you #[1] , thanks for this!
Ligess is a self-sovereign Lightning Address and Zap (NIP-57) server: https://github.com/Dolu89/ligess/
To use it you need:
* an always on lightning node (eg. a Raspiblitz)
* a (sub)domain under your control
* a VPS with a public IP address to avoid exposing the location of your node
A 5 minute guide to set up with your own node: https://github.com/openoms/bitcoin-tutorials/blob/master/nostr/ligess.md
H/t #[0] for adding the Zap support
You can try it by zapping this post ;)
Thanks to CLN most of these options are easily available and probably easier to configure f not using Docker.
Plus you already added the database replication which can be done parallel to the backup plugin.
The biggest difference is that the backup plugin does the save append-only so better suited for an SDcard (if using an RPi), but also needs compacting (can be done without CLN restart as it is only done on the backup).
Enter #Raspiblitz
CLN:
- the backup plugin replicates the channel database realtime to the OS disk (SDcard on RPi)
- the emergency.recover file (same as LND SBC) is synced to the OS disk and backed up to Nextcloud/Dropbox/Telegram
optionally. The last CLN release can backup with peers as an experimental feature.
LND:
- has no database replication option.
- The SBC is treated as above.
I like using a highly redundant ZFS volume as my data disk.
2 out of 4 disks can fail and be changed on the fly + regular snapshots can be synced to another server or NAS.
Ah found it, awesome! note1dduuvaykvge8euucllegtr79krtwm8csre7hxlh6vqg5ssgf5gysr3hgps
All right, thought it is not that simple. What's the setup?
The base fee is not paid for the destination node unless you have a (possibly virtual) node behind yours.
Are we getting ⚡ competition with #FedNow?
(Don't think so, it looks like just another quick wire system like UK Faster Payments or SEPA instant in the EUR zone)
That name though 🤣
Android (at least GrapheneOS) has a lockdown option when pressing the power button which deactivates the by nature insecure biometric login amlnd forces the PIN for the next unlock.
I always use it when give the phone out of my hand. The alternative is to switch off.
The stupidest kid can hold a phone to your face to unlock.
I hope this term catches on especially for the Hungarian speakers.
Maybe from snort:
Nice one, thanks https://nostgram.co brought back everything! 
I always wonder why clients don't offer a JSON export and import feature for the replaceable events.
This sounds exactly what I need!
I realized now that jumping between clients something made me loose my follow list.
Is there a good way to back the list up once I get it together again?
Know about nost.directory to add the twitter contacts, but woul like something I can keep locally.