677
this post was submitted on 15 Apr 2024
677 points (98.6% liked)
Mildly Infuriating
35493 readers
367 users here now
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.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
How the hell would you double dip? They scan you in.
I built a ticketing app for folk festivals 2 decades ago and we had that problem beat even then.
Actually think this is more about protecting against unscrupulous scalpers selling tickets multiple times.
When you can just email a pdf or print it, nothing stops you from doing it multiple times.
At the end, it's ticketbastard that has to listen to the people that got scammed. This method forces authentication and secure the chain of custody.
Mfa does make sense here tbh. I'm more upset by their outrageous fees and monopoly.
Change a number. Then when they scan it you claim it's an error and then you are dealing with a "technology problem".
Sure, they can you on, but which patron is the real patron?
Suppose the ticket was supplied as a PDF. Then it is either in the users Downloads directory or in their email. If that PDF is obtained by a malicious actor, it could be resold countless times. You could have 100 "guests" arrive at a venue with a bogus ticket but only the first one gets in, because they were scanned. That first person may not be the legitimate ticket owner.
Now, if your using their app, they usually put an animation over the barcode, and the gate attendants know to look for that. If that animation isn't there, don't scan. Pretty simple instructions to give to anyone. And accessing the app likely requires logging in, probably with some form of MFA (though probably SMS), so it gets a lot more difficult to rip off both the legitimate users and Ticketmaster in this way.
I don't like having to use a specific app for things like this, but "I kinda get it".
Now, it'd be better if we had a universal standard format for putting secure, validated passes into the native phone app. Perhaps registering your device to your account via their website, then only allowing the ticket to be installed on one device. I'm sure there'd be more to it, im just spitballing.
PGP-encrypted email for everyone, problem solved.
Yah, yah, I know...
There you go, assuming the problem is worth the corporation's time and money to bother solving. The correct answer is to not bother hiring a customer support department and telling people that they're SOL when stuff goes wrong. The goal is to take in more money than you spend on customer support, so you spend none.
AXS does not integrate with google wallet. I put a note in each calendar event which app the tickets are in. At least the Pixel phones now let you put anything in your wallet that is a QR code. I wish it would let us put plain old images in the wallet.