#[0] makes it obvious that clients need a mute function per thread/note, otherwise content shock will be near. #[1] & #[2]
Discussion
Otherwise we have to stay at the manual level and ask users to not respond to overwhelming thread like #[5] does here. And what users do is like the note from #[5] with his request for silence. 🤦
#[5] : Thank you for making an important client flaw obvious with your wonderful #[1] . 🧡
that's what i call a free speech paradox. we all need filters, but it's good to have the control on nostr
I wanted to Zap you for this post. But you don't have a LN address set in your profile. 😟
See here how to get going with Nip-57 Zaps: note1lclyv0qwplty97fn4u0k5ns7w0uw8u7tswsa42lrsa2hajqdwmzskm690v
Thanks I am still researhing aspects of lightning before I jump in and run a funded node. I set up a LND address. I heard, differently to running a bitcoin node, some skill is needed to run a good lightning node @darthcoin
If you self host you're having the hot wallet risk plus other risks. See here and DYOR: https://bitcoiner.guide/lightning/
But imo the advantage of instant, cash final settlements and economically sensible microtransactions due to tx volume based fees outweight the risks of funds in the range of pocket money in a lighning wallet many times.
And don't dox yourself. Sending is private (in most cases but receiving is not. The invoice and lnurl contains your node's pubkey and through your pubkey one can find out the utxo's you've used to open channels. So don't use the same lightning wallet/ node for receiving sats with different identities.
Have been noticing this last couple days. UI things like collapsing the list of usernames would be nice as well, sometimes taking 1/3 of the screen.
An "I'm out" button.
Yep, it's a problem even for me at user level, we need to redefine a little the note options, maybe I'll add something about it
For context, here's a discussion about the mute function on client level going on:
#[1]