On #3 it would also be great to be able to mute notifications from a certain note. Like if you get mentioned and it is getting a lot of activity - I guess this falls under messy so you may already have it planned
Are you serious?
The only way to get the total chaos is if you are pulling from completely unfiltered public relays. Most that have started filtering have been transparent about it on nostr, but there isn’t really an established way to see how they are modifying content through relay metadata as far as I know.
I guess the latter question is about inscriptions. Ordinals at just an L2 outcome of UXTOs not being fungible.
Whoever you talk to I want to know why more people aren’t talking about bitcoin fungibility (or lack thereof) being a root symptom of “the problem”
Also would like to hear what solutions would be in order to fix any odd economic incentives introduced by taproot - not saying we should, but what does the actual implementation of a fox look like technically and socially.
The LN wallet would really need to be interoperable and be able to trust that the client isn’t sending bogus invoices to extract sats from its user. I bet someone can and will figure out a way to do it. Would be much better UI!
I have not read the NIP in detail, but the receiving wallet does actually post a sort of “read receipt” event that it got zaps. These could be aggregated by a relay for sorting (right now it just displays on the post).
I haven’t read enough about the NIP to understand how the zap gets communicated to the wallet - if that somehow happens in the lightning transaction or if the sending nostr client is also publishing a send event that the receiving wallet has to look for.
So definitely more going on than a standard tip, but I can’t say I fully understand it yet
Only the receiving party needs a NIP57 wallet - I don’t have one and I can see zaps I send to people who do. Someone described it as a read receipt posted to nostr, which seems like a good description
One click wont exists until you have a wallet integrated directly into a nostr client. It is possible, but for now they are two separate entities and your wallet is always going to want to confirm the invoice for security reasons. Even if 1-click can exist I don’t know if it should without A LOT of safeguards
That was it. Makes sense. Thanks!
Hmm I figured just the receiver needed a compatible wallet, or maybe the sender. I don’t see why a random viewer would need it. My wallet shouldn’t be talking to nostr for every post…
Am I the only one still not seeing zap tallies in the new Damus update?
