@thezerobit Counter point to this. Adding a "no" option also requires you to have some kind of settings panel where the user can later change that "no" to a "yes". It can actually be a lot more work than just showing the thing once every few days.
@thezerobit "NO" sends a signal to not bother me anymore with this. "maybe later" allows the company to continue to beg me to say yes, hoping I eventually get tired (or make mistaje) and press "yes". The fact that everyone does it likely point to it working for a larger percentage of people who eventually say yes, than those who compain about it.
Can't wait for:
Have you stopped beating your wife?
@thezerobit Lack of "No" or "No! I said you, NO, b@stard!!!" button is not about being adult, it just about considering people as "users", some kind of slavery, similar to relationship between dealer and "user" of an abusive instance, like heroine or crack.
@aral Looks like another example happened of what you said about, when people seen as "users".
@aral It was not deleted, so I guess there is some federation issue between servers.
In shortly, that post is critique of that practice of using "Yes" and "May be later", without any option of say "No" to something, as common practice of today "user experience"
@koteisaev Ah, right. Just went on the profile and saw it. And yeah, agree 100%. In fact, it’s the one gripe I have with @signalapp – the “turn on notifications” prompt does not have a “no” option. It says “We’ll remind you again later.” That’s a dark pattern that I’m assuming was an oversight or the work of an rogue overzealous developer that I’d love to see rectified (CC @Mer__edith)
@thezerobit Yeah, I think I saw Jira doing this. And the dialog was covering the part of the UI I needed to close my ticket, which made me think that it'd moved, which was even more annoying.
Add comment