Avatar
Lyle Pratt
27f211f4542fd89d673cfad15b6d838cc5d525615aae8695ed1dcebc39b2dadb
Building vida.io.

Open networks will always have more spam problems than closed networks (think email). Fortunately we now have the power of Lightning’s instant digital settlement to protect Nostr. Here’s a discussion #[2] and I had on the topic. https://youtu.be/nqny85h27B8

Every day that passes, there is less bitcoin supply available and more bitcoin demand. Every day.

This is not complicated folks. Number is going to keep going up. Keep it simple and stay safe in cold storage for the long term.

75 degrees porch sitting weather is pretty nice for February. Cheers friends 🥃

https://void.cat/GkUY3KD4PqFZqjpG7NjM2F

Not sure this is correct, or perhaps only correct in some cases depending on the relay implantation. In Nostream (what Vida and most others are using for paid relays), a Zap is a posted/written event and a relay will only accept it from pubkeys in the relay’s whitelist.

#[2] I paid to add Vida’s pub key to a few relays. Clearly not a good long term solution.

normally an SSL Cert issue. Does it happen with 1 specific relay or are you seeing it happen across common relays that are apparently working in other contexts?

hmmm….I will look into this. it should only have a cap, not a minimum

we don’t have very good send/spend support from the Vida wallet as of now. working on that!

we have one, but honestly not the best experience as of now. working on improving it. there’s a link settings in the web to DL and provision it.

no, not required. normally that error is because the relay doesn’t have your profile information stored. try opening your client and re-saving your profile info while connected to that relay. or try another relay you’ve been connected to before. brb.io has been a little slow lately, so it might just be that.

Your Vida Lightning address supports it now!

ahh good point. you can trust your own zapper’s pubkey to send you correct events. 💯