Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.
I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!
It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means: -No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
7. Content should match the theme of this community.
-Content should be Mildly infuriating.
-At this time we permit content that is infuriating until an infuriating community is made available.
...
8. Reposting of Reddit content is permitted, try to credit the OC.
-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.
...
...
Also check out:
Partnered Communities:
Reach out to LillianVS for inclusion on the sidebar.
All communities included on the sidebar are to be made in compliance with the instance rules.
I also reached out to them on Twitter but they directed me to this form. I followed up with them on Twitter with what happened in this screenshot but they are now ignoring me.
When you insist on implementing your own email address validation...
I have my own domain that uses a specific 2-letter ccTLD - it's a short domain variation of my surname (think "goo.gl" for Google). I've been using it for years, for my email.
Over those years, I have discovered an astonishing number of fuckheaded organisations whose systems insist I should have an email address with a "traditional" TLD at the end.
A few years back I bought a .family domain for my wife and I to have emails at ourlastname.family That lasted a week because almost every online service wouldn’t accept it. Now we have a .org
Doesn't surprise me one bit. I've noticed that a lot of websites will only accept .com and a few will only accept email addresses from popular providers (Gmail, Hotmail, outlook, etc.)
My guess is that it's trying to reduce spam and fake account generation.
My guess is that it's trying to reduce spam and fake account generation.
Thus preventing the growth of any small providers and further entrenching Microsoft, Google, Apple, and a handful of others as the only "viable" options.
The only useful email validation is "can I get an MX from that" and "does it understand what I'm saying in that SMTP". Anything else is someone that have too much free time.
It's easier to Google "email regex [language]" and copy the first result from stack overflow.
Definitely a timesaver. Much faster to get incorrect email validation that way then to try building it yourself.
I've encountered this because my domain has a hyphen in it. Very irritating.
but they are now ignoring me.
Hmm. Did you try giving them your email address?
Yes, now my twitter dms are stuck in an infinite loop
Somebody made a shitty regex.
Probably, from what I can see the address in question isn't really that exotic. but an email regex that validates 100% correctly is near impossible. And then you still don't know if the email address actually exists.
I'd just take the user at their word and send an email with an activation link to the address that was supplied. If the address is invalid, the mail won't get delivered. No harm done.
Actually, one of our customers found out the hard way that there is harm in sending emails to invalid addresses. Too many kickbacks and cloud services think you're a bot. Prevented the customer from being able to send emails for 24 hours.
This is the result of them "requiring" an email for customers but entering a fake one if they didn't want to provide their email, and then trying to send out an email to everyone.
Our software has an option to disable that requirement but they didn't want to use it because they wanted their staff to remember to ask for an email address. It was not a great setup but they only had themselves to blame.
Smells like bad regex
Exactly. After the @ they should just confirm there's at least one period. The rest is pretty much up in the air.
Which would still be technically wrong. There does not need to be a dot.
The best way to validate an email address is to sent it an email validation link.
Anything outside of that is a waste of effort.
That is 100% a chatbot using a regex email validator someone wrote as a meme that the chipotle dev copied from stack overflow without context.
That is 100% a bot, and whoever made the bot just stuck in a custom regex to match “user@sld.tld” instead of using a standardized domain validation lib that actually handles cases like yours correctly.
Edit: the bots are redirecting you to bots are redirecting you to bots. This is not a bug. This is by design.
Modern customer service is about willfully designed layers of broken system engineered specifically to frustrate the majority of people that can't regulate their emotions. It's always a series of about "12 doors" you have to cross through that are exceedingly difficult to pass through. They are designed to sap your energy with the hope that you eventually reach a boiling point, hang up, get distracted, go on with your day and never follow up out of fear of starting the same process again.
Chipotle is telling you they don’t want your money
I would sure like the free stuff they promised me after my past purchases
I work for Chipotle Corporate. Please send me your email address. I'll make sure it gets fixed.
Nice try I've heard that before
There should be an '@,' followed by a domain (name@email.com).
What is your email address?
If that's their standard, you can probably just edit the html to make the login button active and then sign-in.
You're talking to a bot that has a crappy parser and doesn't understand what a subdomain is.
This is why you never attempt to validate an email address beyond requiring an @ followed by a period, and send a verification email
Technically you don't need a period for a valid address. "a@a" is a valid email address.
Clearly AI.
Nah, it's just a old school chat bot following a predefined flow chart. And in this flowchart someone implemented an improper email check.
It's pretty much the same as if there was just a website with an email field which then complains about a non valid email which in fact is very valid. And this is pretty common, the official email definition isn't even properly followed by most mail providers (long video but pretty funny and interesting if you're interested in the topic).
You can use symbols like [ ] . { } ~ = | $ in the local-part (bit before the @) of email addresses. They're all perfectly valid but a lot of email validators reject them. You can even use spaces as long as it's using quotation marks, like
"hello world"@example.com
A lot of validators try to do too much. Just strip spaces from the start and end, look for an @ and a ., and send an email to it to validate it. You don't really care if the email address looks valid; you just care whether it can actually receive email, so that's what you should be testing for.
Have you tried giving them your email address?
My Ameriprise account has its own email address because the fuckers don't believe any email starting with email@ is a real email. I've called them a million times and got them to file a bug, which they did, and then closed as won't fix.
Sounds like they don't want your business anymore.
Why are you keeping track of the age of your Chipotle account?
Because those points add up, playa.
Reply, that you'd be happy to provide your e-mail. but first, you must verify them, my having them provide an e-mail.