Nostr Web Client

Notice that my complaints could be solved with a text box telling me the requirements. That costs like 3 minutes and a line of HTML. Maybe some CSS if you want it to look pretty. I'm not saying every product should allow me to store whatever I want in its password database, just don't have limits and not tell me what they are. This is especially true when you already went through the effort to validate the input form to some degree. All you have to do at that point is share with the class. Lol

This isn't a broad hatred of technology or any particular era. This is a highly specific issue with requiring something of the user without telling them what it is you want. That would be retarded in any era of tech. So I agree that "what year is it" could be ditched.

Matt 6mo ago 💬 3

I feel like I'm asking for the minimum user respect on this one lol

Reply to this note

Please Login to reply.

Discussion

ChipTuner 6mo ago

My only objection to this, is well for example, I helped manage a small eCommerce business and we weren't developers or in charge of the code. If a bug like that appeared, someone would have to tell us, and then we'd have to ask our development company to bill us for support to fix that bug. So it cost a support staff to field the email, coordination with the development company, and then billing, when, In this particular scenario, affects maybe 1/6000 people. I can say for certain we had the same issue on our software, and over 7 years never had a customer bring it to our attention. I found it by accident, it may have been possible that customers had the issue but forgot their password anyway, so we reset them for the customer. You could say "yeah this would save support staff time" but support staff fields these issues regularly for a dozen other reasons anyway, it's still easier/cheaper than coordinating with the software company, because they usually bill a few $100/hour.

This is just one of many issues that appear like this XD

Matt 6mo ago

I just don't view not telling people password requirements you decide as a bug. That isn't an accident or code error. It's just a complete omission of information that anyone above 90 IQ should think to include.

"I expect something of you."

"What?"

"Figure it out."

I can almost see it if the requirements changed and someone forgot to update the front end alert. Or if they mistyped the requirements. That's a bug. Maybe your case makes sense. But to just never put it there isn't a bug. It's awful engineering and UX by choice.

If you have a specific requirement, the user should be told. I'm not disagreeing that developers and companies have reasons for being shitty at what they do. I totally get that. My point is that there's no excuse for it that I accept. I'm calling them out as shit. Entirely subjective.

Matt 6mo ago 💬 1

I'll be a little more fair and say that this issue (for me) has largely been on websites of large companies. So it isn't like it's just small ass one off examples here. It's a widespread issue that shouldn't exist anymore. Especially for modern websites that are getting updated.

ChipTuner 6mo ago

It's so big they probably don't know where, in the 10x forked codebase that issue even resides or where to fix it, or whos responsible for it XD