Jokes aside, I have been blocked many times by overzealous email validation. Yes, my email has a plus sign in it. This is allowed under RFC5322, so deal with it. It is better to have no validation at all than incorrect validation.
post
The issue this is referring to is because the user cannot paste into a text field. And the user was not rude about it either.
So instead of fixing the actual problem, the developer went nuclear and removed the validation. A dick move in my opinion given the developer’s attitude.
It’s more sad than funny. 🤷♂️
IMO as a developer this is a sane change. There's no telling when the format of the first-party api key will change. They may switch from reference tokens to JWT tokens tomorrow. The validation should be using the token and seeing if it works.
I don't know what that repo does. But, chances are the dude was just fucking tired of dealing with curseforge. Total garbage scum software.
I'm guessing removing the validation fixed the pasting, which means it did fix the actual problem?
I hate when websites have some weird rules for passwords, and show the rule when you are creating the password, but not when entering it. How am I supposed to remember the password must begin and end with a special character?
I can't recommend password managers enough, because you will never have this issue again.
Password creation will still be annoying for sites with special rules. You just don't have to remember them once you generated them.
I've literally never had an issue with password generation. Usually I generate 32 character passwords with all types of characters passwords on average expect. If a page has different rules, I just check the corresponding boxes in my password manager, and I get one that works for that site.
and when the rule is also wrong example: password must contain special charcters
the password in question contained : and ^
if those aren't special characters idk what is
maybe they were looking for extra special characters like 🁄 or ⶸ. Who am I kidding, RFC 1738 tells us that literally everything is unsafe and you know, we need to prepare for the inevitable occasion when the password somehow ends up inside an URL.
The characters "<" and ">" are unsafe because they are used as the delimiters around URLs in free text;
the quote mark (""") is used to delimit URLs in some systems.
The character "#" is unsafe
The character "%" is unsafe
It ends up with
Thus, only alphanumerics, the special characters
$ - _ . + ! * ' ( ) ,
are safe
I am going put null on my password and you aren't stopping me
If the password is going in URLs you already have a problem.
I never get bored of discovering yet another software that gets broken because someome put a dollar sign in their password...
Having to alter my one generic password I use for random ass website because there's a stupid extra rule is usually annoying me enough that I don't register lmao.
Password manager?
So the users realized their mistakes and stopped complaining……and other jokes public project maintainers tell themselves while laughing in tears
Prismlauncher! I remember browsing through the changelog and spotting this, made me chuckle internally.
If only I had a penny each time a user told something doesn't work when it shouldnt've.

top 50 comments