I wanted to make it clear in the UI that the person doesn’t receive likes, hiding the like button on their posts accomplishes this. Why do you want to like their post if they won’t see it?
Discussion
I’m a bit concerned it will further confuse new users but I don’t get this particular complaint at all. How could not being able to like someone else’s note (who can’t see your reaction) bother you?
Yeah I don’t understand it either 🤷♂️ it seems to be upsetting a lot of people.
People don’t like change?
nostr:note1txw7mrv4mrquz7jwq9mrs0f38rp785z82jtejgch6ydu297ce3usg6ex6r
I’m not opposed to the change but on Twitter I used the heart button as a simpler bookmarking tool (in addition to showing support or agreement).
Both Twitter and Damus have bookmarking features but they’re nested in the menu and require more steps to complete.
some people use likes to catalog tweets to go back and look at in the future. most clients have a “liked” history where you can go back and look at them so it’s convenient to know you will have the same liking ability and history across clients
i’m all for onlyZaps btw(:⚡️
I used the like button to explore other users that I may want to follow. By using that feature I could see everyone that agreed with that note and to further determine if I may be interested in following them.
Having said that, like most change, I’m willing to step out of my comfort zone and see what this new experience offers and where it may lead. 🤘
I don't know what client someone else is using. I'm typing this from Amethyst. I can like all posts. I don't know who is using Damus, much less who has #OnlyZaps enabled.
Additionally, many people use multiple clients. They would see the like on clients other than your own.
This creates much more confusion than it solves.
If the change only affected a Damus user's own feed, this issue wouldn't need to exist.
Other clients should support this feature! A few do already, I think amethyst is working on it as well. Respect users wishes to not be liked ✌️
Respect my freedom to use Nostr however I like. If I want to like something, I will. If I want to zap something, I will. The two serve different functions to me and many others.
You also missed my point where I directly answered your question. Even if other clients support it in the exact same way yours does, if I choose to use a client that doesn't, I don't know who is using it.
Many people also use multiple clients, and may have different devices set up in different ways, hence may see (for example) a like on their desktop even if they don't see it on their iPhone.
This is a flawed analogy. I can setup my lightning node to block zaps from your pubkey. Is it really “your right” to send something to someone that they don’t want? For what reason?
Is it “your right” to send to a thread when it has been marked “xanny can’t reply to this”. Sure, go do that in another client then. Clients that respect users individual preferences don’t need to show it.
Its not black and white though. damus still allows you to reply to people who have muted you, which I think is fine, a blocking feature could prevent you altogether, but like you said it would be pointless because other clients who don’t implement this could still show it.
I don’t feel like I’m not taking away anything that actually matters. We’re talking about likes that they don’t want and will never see, and it’s opt in. Is this really a hill to die on?
Isn’t setting up the lightning node to block zaps the same thing as you saying you don’t want to “see” them? Someone still can try to send out the zap. Maybe it won’t go through but you can’t prevent someone from trying.
I love the idea of you choosing what you see in your UI, but once you put a note out there, it’s not yours anymore. You prove it came from you, but someone else can put in on a website and other people can interact with it in all the wierd ways they want to.
I think as soon as you’re trying to control what other people do, you’re trying to censor - if you don’t want to see something, just hide it, like with muting, etc.
This feels like the same argument as trying to tell someone they can’t say something because it might offend you. You’re only responsible for listening by and reacting, but you can’t control what someone else says.
If you still disagree, what do you think I’m missing here?
Thank you.
This gets to the crux of why it's a strange implementation to me.
Instead of changing the user's UX, it forces a change on everyone else's.
To me that's backwards.
Exactly. The author of a post has a preference (say, not to see nor receive likes). That preference can be expressed to the reader, but (IMO) should not curtail the reader’s options.
> Maybe it won’t go through but you can’t prevent someone from trying.
If my lightning address endpoint has “blocked pubkeys” in the data, why would I show a button that would be guaranteed to fail ?
> you’re trying to control what people do
No I’m giving individuals the power to control the types of interactions they have on the network. I am not forcing this on anyone. I actually have no problem enabling the like button for people who dont have OnlyZaps on for OnlyZaps profiles, I am just really trying to understand why people care about sending zaps to people who will never get it and why they feel this strongly about it. For me I just see it as a ux flaw.
I thought this was more of a protocol discussion than a just a damus UX discussion… 😅
I personally wouldn’t want other peoples profiles to show a zap button if they wouldn’t/couldn’t receive it…
Liking seems maybe a little different because even if the person posting doesn’t want to see the likes, I can see how other may still want to like a post and posts that gets lots of likes is a way for people to find good content. So while the person posting would never see it, it could still be really useful for others.
First of all you're being way more defensive than you need to be. I'm giving feedback on a beta feature in your client. That's literally what beta testing is for. If you think I'm fuming with anger because of this, you're mistaken.
I simply feel your implementation makes too many assumptions and creates a worse UX for the broader Nostr ecosystem. I have explained my reasoning very clearly.
Not everyone uses Damus.
Not every client will implement your idea.
Not everyone uses Nostr the same way.
Most people who don't opt in won't even know if someone else has unless they exclusively access Nostr through your app.
Many people opt to use multiple Nostr clients and will see likes on others even if they don't on yours.
Removing the option to like only creates more noise in the feed as people reply/quote instead of just hitting a like button.
Wills way nicer than me. I’d just tell you to shut the fuck up or fork
What's the point of open beta testing if your reaction to polite user feedback is "shut the fuck up"?
I rarely find “rights” discussions helpful/useful. If I don’t want likes, or even zaps, that’s my preference. More options are more better.
Some users may prefer not to be replied to or quoted, but they don’t have the power to stop others from doing those things.
Aside from you and #[6] who are making a lot of noise about this, few seem to care.
I am sorry that you get offended by a like or a reaction. I will use a client that allows me to send whatever message I want and doesn't censor me.
Zaps are cool, but there is no need to force them. Forcing is not cool.
Unfollowing for now. This is clogging my feed.
🫡
Faz sentido!