Hello Zapreaders.
After some careful consideration, I've removed the user-to-user tipping function. I plan on replacing that functionality with a non-custodial implementation in the future (probably using something like keysend).
Why?
There are several reasons why I thought it best to do this.
First: Zapread is now owned by a legal corporation. This means that the platform will be transitioning to a legal entity, and this means growth but also becoming under more regulatory monitoring. For this reason, it is important that we do not appear to be a money service business.
Second: tips are implemented with a custodial solution. This is not ideal! I'm not happy about it. If we can move to a non-custodial solution then we can avoid many security and counter-party risks as well.
Third: Encourage more spending on content. Use those sats to vote up (or down) content. This injects more life into the platform. Tips were fully parallel to the mission of zapread.
I hope this doesn't cause anyone concern. Please comment about your thoughts on this.
Why don't you use Nostr protocol on Zapread? https://github.com/fiatjaf/nostr
Thanks for sharing that. Very interesting. I might look into this. Also, I like that it is public domain. One of the things I want to balance is the the prevention of censorship, while still managing spam and nuisances. For tips - I'm going to start by adding the ability for users to insert their lightning node public key to enable keysend. This means that tip transactions will all be peer to peer, and also fully anonymous. Zapread would just be a bulletin board of addresses and not have any key role in the transaction itself.
So Nostr is very good. You can see in action a twitter close using Nostr protocol here: https://branle.netlify.app/
Why don't you wait bolt12 instead of use keysend?
bolt12 is very promising. It's still in draft, and if it becomes standard it will be absolutely supported.
Read this too: https://github.com/rajarshimaitra/rust-nostr/blob/main/VISION.md
I tried it out but no content appears for me. I'm still interested in the protocol, but a bit concerned about the inefficiency of the approach. It may be bad for UX.