Or simply the problem like this will probably happen to the users when we need it π
#[4]
#[5]
It means we can receive zaps or lightning wallet directly to our own wallet (fully controlled and managed by ourself). π
Wallet of Satoshi, ln.tips bot, or similar wallet/services are custodial wallet. We don't fully control the funds in those wallet (similar like holding IOU balance in the bank or centralized exchange). Although unlikely to happen (currently they are quite trusted), in the worst case they can possibly seized our bitcoin.
Slowly, we better to learn how to manage our own wallet. Be our own bank. π
Preparing draft of tutorial about "How to Receive Non Custodial Zap and Self-Hosted NIP-05 in Mobile Phone (Zero Additional Cost)"
as long-form content (NIP-23).
This draft was written by using Markor Editor - https://www.f-droid.org/en/packages/net.gsantner.markor
Related Experiment:
#[0]
The draft is already 2/3 completed. It will be published soon in long-format content using habla.news or blogstack.io .
#[0]
This is your inner soul calling. You have to become strong dragon π
You need to be a strong dragon who protect fellow nostriches π
Yes, many kind people here, you're kind too π
Great works Mazin, you just need to quote or boost it several times for different timezone to get enough feedback π
Oh you want to update the code for CLN in satdress? It will be such a great update and already cover most case (LND, LNBits, CLN)
Zapping to ourself. Don't do it too much π
Yes, we won't likely see any spam by using paid relays as long as we enable them for reading nostr data and limit the data coming from free public relay.
Paid relays act like a wall that prevent spam from Bot coming. Basically, any paid relays will prevent the spam coming to those relay because spam actor won't likely spend money to spread their spam. Their main targets are free public relay which don't have any spam filter mechanism.
I like this idea, especially subscription model only for filter.nostr.wine extra service. I think this is mainly due to high server activity to aggregate from public relay for every unique public key member, right?
What about comment? π
Yes, confirmed. It seems my node doesn't get proper route to your node. Using different wallet can works properly π
12 char? π
Btw, what happened to your LN address ser, is it just me that i can't zap you? π
Well, it seems really weird issue. Maybe you can give the detail and report this issue to #[5] or #[6] . Hopefully this issue can be solved soon for you.
Have you try fully cleared all data, cookie, and cache?