this post was submitted on 25 Aug 2026
69 points (93.7% liked)

Mildly Infuriating

47313 readers
2460 users here now

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that. Please post actually infuriating posts to !actually_infuriating@lemmy.world

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/ExplicitContent


-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. If your post better fits !Actually_Infuriating put it there.

-The Community !actuallyinfuriating has been born so that's where you should post the big stuff.

...


8. Reposting of Reddit content is permitted, but attribution is not required in any way. No links to Reddit in post body


-If you would like to provide a source link, do so in the comments but not in the post body.

...

...


Also check out:

Partnered Communities:

1.Lemmy Review

2.Lemmy Be Wholesome

3.Lemmy Shitpost

4.No Stupid Questions

5.You Should Know

6.Credible Defense


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.

founded 3 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] tal@lemmy.today 28 points 1 day ago (3 children)

Hmm. Could be.

searches

https://www.msn.com/en-us/society-culture-and-history/social-issues/nj-woman-baffled-by-hurtful-birthday-dessert-message-at-weehawken-restaurant/ar-AA2aMzua

A spokesperson for Blu On The Hudson sent CBS News New York the following statement:

"We at Blu on the Hudson are aware of the recent video circulating on social media, and we are deeply saddened by what occurred. We sincerely apologize to the guest and to everyone who was hurt or offended by this incident which took place on June 20, 2026. Treating every guest with dignity, respect, and care is fundamental to who we are as a company.

"We want to provide some context regarding what happened, not as an excuse, but to explain how this unfortunate mistake occurred.

"Our standard operating procedure is to use table and seat numbers on tickets to identify where each dish should be delivered. In this instance, the word "wheelchair" was used as a reference to identify where a birthday dessert with a candle should be delivered. Unfortunately, that notation was misunderstood and was written on the plate itself. There was absolutely no malicious or disrespectful intent behind the notation. However, we fully understand how seeing that word written on a plate could be deeply hurtful and upsetting.

"Since the incident, we have reinforced with our team the importance of following proper ticketing and communication procedures and have taken steps to ensure that something like this does not happen again. We have also made an attempt to reach the guest directly to personally apologize, although we have not yet been able to connect with them.

"We understand that an apology cannot undo the hurt or frustration caused by this incident, but we sincerely hope it conveys how deeply sorry we are. Blu on the Hudson is proud to be a part of the Hudson County community, and we are committed to being a place where every guest feels welcomed, respected, and valued.

"We are deeply sorry for this occurrence, have learned from it, and are committed to doing better moving forward."

[–] Blooper@lemmy.world 7 points 23 hours ago

10/10 apology; would forgive.

[–] running_ragged@lemmy.world 7 points 1 day ago (1 children)

That's a well crafted PR response that does it's best to accept responsibility and give a plausible explanation, which is what's expected. Doesn't mean its true.

It doesn't really fit well with what's in the image to my eyes though.

Maybe a second person saw the ticket, thought someone missed a word and added it, but that doesn't make sense at a high end place to have just anybody doing lettering.

Looking at that 'Happy Birthday' on a plate and thinking something needed to be added, I would not want to touch that perfect cursive even if I had similarly impressive flow, I can't imagine the different shape wouldn't be acceptable at a place like that.

[–] glimse@lemmy.world 1 points 16 hours ago

Well the other explanation is that someone did it maliciously knowing it would cost them their job

[–] moobythegoldensock@infosec.pub 4 points 1 day ago (1 children)

That begs a larger conversation about what is and isn’t ok to say informally at work.

Certainly “wheelchair” is not itself malicious and is less likely to be mistake prone than Seat 34a, especially if there’s only one patron in the room seated in a wheelchair. At the same time, the affected person might not enjoy being referred to by their disability.

I’m honestly not sure what the best solution is. Certainly, “red sweater” is less likely to cause offense than “black dude,” and 99% of the time these won’t be customer facing. I’m torn on whether the mistake was purely in writing it in the wrong location vs. whether the company as a whole should do better.

I know in the corporate world you typically don’t write down anything you don’t want read back to you later, and the fact that they realize the patron could be offended suggests that maybe they should adopt a similar policy of “never write down anything you wouldn’t want a customer to see.” At the same time, I’m aware most restaurants are not corporate culture and aren’t trying to be.

[–] Catoblepas@lemmy.blahaj.zone 12 points 1 day ago* (last edited 1 day ago) (1 children)

The seat itself is probably being identified as ‘wheelchair’, not who’s using it. Wheelchair seating has different dimensions and no seat, so if a restaurant is small enough to only need 1 wheelchair accessible seat to be in compliance with accessibility laws they might just call it the wheelchair seat instead of seat 8.

[–] towerful@programming.dev 7 points 1 day ago

Or someone in the party mentioned it to a server when they went to the bathroom as a surprise "can you do a special dessert for the person in the wheelchair, it's their birthday".
So the server just added it to the order without knowing where the person was actually seated at the table.