Mildly Infuriating
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.
view the rest of the comments
Tell me you know nothing about front or backend webdev...
Don't talk to our "FRONT END AND BACK END DEV" like that.
"Take what's coming out of your FRONT END and blow it out your BACK END!"
It's almost like buying and refunding are two completely different processes that are handled under entirely different protocols by credit processors, and one part working has no bearing on whether or not the other part works.
And I never claimed they don't have different prioritization. I'm just saying that one working doesn't mean the other will also work.
The page may have not loaded because of a failed API call to the credit processor when requesting a refund. Charges and refunds are different API usages, and it's wholly possible that an issue on the processor's side can break pages on a merchant's site. If for some reason Walmart's site can't communicate with Visa/MC/AmEx/whoever and their page isn't configured to handle a specific failure, it will likely go to a default error landing page as a failsafe.
I'm not defending Walmart or anything; just explaining some of the technical reasons a refund page can break. API failures happen even to non-scummy stores, as well.
It didn't even get that far.
This error quite literally came up when I click on the "request a refund" button within my order (where Walmart said I needed to. There should have been another page asking which item(s) I want to refund, and I would imagine ask me for a reason why. That's well before it needs to call an API for credit processing.
In any case, this was mildly infuriating, more for the wasted time on something that should have taken two seconds.
FWIW, I can only hope that Walmart gets notified whenever these end user issues pop up on the website... so they can fix the problem. It's been many hours already, and the page still errors out. Unless they've hired amateurs, this seems excessive. Would it take this long if their payment system was down?
Regardless of how these protocols may be handled, they advise customers to use the refund option within the order screen on the website, which is what I did.
If it's broken, why even direct people there? I wouldn't expect a half-working website from one of the largest retailers on the planet.
Links generally don't know if the service on the other end of the link is up or down at that time. I mean you could have it go out and prefetch the headers but that's a lot of overhead for every link.
"The service" in this context, would simply be another Walmart page. A page which also just happened to be one where I'd start the process of getting money back.
It was not a page to actually process any transactions, but to start the process of requesting a refund.
It's not the first company to "offer self serve" where the action involves taking away revenue and just so happens to never ever work, requiring a call to their support. It's almost as if they know some people will just give up and they can keep the profits.
Tell me you know nothing about anti-consumer business practices…
My friend, you're on !MildlyInfuriating
An annoyance is still an annoyance even if there's a reason for it
While this is technically accurate, if this is a long-term pattern you would hope that this would be fixed pretty easily, or have a comparable SLA to other services. If your refund tool is always down, that's a leadership decision.
This guy does it all! Front and back!
top and bottom, too.
In between is the best place to be!
Tell me you ever had a dream that you, um, you had, your, you- you could, you’ll do, you- you wants, you, you could do so, you- you’ll do, you could- you, you want, you want them to do you so much you could do anything?