lakerz16
Joined 14 years ago
Joined 14 years ago
If the seller re-opens the TM app and it generates a new token and invalidates the old one, then that's not the case.
You're also walking into a stadium/concert in plain view of security cameras, so the stakes and deniability are different as well.
There's a section named "Pirating Tickets", that just explains how to re-create a barcode that you already paid for. You're not using this to rob anyone of anything.
And at the end, "Have fun refactoring your ticket verification system". Why? There are no vulnerabilities here. A rotating barcode (even if following a known pattern) is still more secure than a static barcode on a piece of paper.
Instead, they are paying for ad space to siphon the traffic of already hungry customers looking to order from a restaurant.
GH then shows the numbers to the restaurant and says "Look how much business GH brings you. You need to pay us for this"
In many cases they are extorting restaurants over what would be organic web traffic. In these cases they are not adding new revenue to the industry, and are instead choking the restaurants that already operate on thin margins.
And now every customer after me won't be exposed to me, either.
Given all that Google knows about you, i'd say they're actually quite polite in how invasive they are. I'd much rather them have this data than 99% of the other companies out there.
It sounds like you basically just hate businesses that collect data. I'm sorry to break it to you, but there are a ton of them.
Or is the entire idea that each person is logging a unique POV or set of information about someone, rather than the system gravitating towards there being a single, cultivated profile about each person that is shared around?
(right now it's kind of the anti social media -- which seems like a refreshing take. Just curious if that's on purpose)
I hope 8.1 addresses the Desktop users in more ways than just the Start Button.
"this suggest a fundamental lack of security practices at the company" – that's a stretch of a conclusion to make. You're being as hyperbolic as the original post.
What didn't I understand about the article? This still offers a slight increase in security over static barcodes, without introducing any new vulnerabilities.