World News
A community for discussing events around the World
Rules:
-
Rule 1: posts have the following requirements:
- Post news articles only
- Video links are NOT articles and will be removed.
- Title must match the article headline
- Not United States Internal News
- Recent (Past 30 Days)
- Screenshots/links to other social media sites (Twitter/X/Facebook/Youtube/reddit, etc.) are explicitly forbidden, as are link shorteners.
-
Rule 2: Do not copy the entire article into your post. The key points in 1-2 paragraphs is allowed (even encouraged!), but large segments of articles posted in the body will result in the post being removed. If you have to stop and think "Is this fair use?", it probably isn't. Archive links, especially the ones created on link submission, are absolutely allowed but those that avoid paywalls are not.
-
Rule 3: Opinions articles, or Articles based on misinformation/propaganda may be removed. Sources that have a Low or Very Low factual reporting rating or MBFC Credibility Rating may be removed.
-
Rule 4: Posts or comments that are homophobic, transphobic, racist, sexist, anti-religious, or ableist will be removed. “Ironic” prejudice is just prejudiced.
-
Posts and comments must abide by the lemmy.world terms of service UPDATED AS OF 10/19
-
Rule 5: Keep it civil. It's OK to say the subject of an article is behaving like a (pejorative, pejorative). It's NOT OK to say another USER is (pejorative). Strong language is fine, just not directed at other members. Engage in good-faith and with respect! This includes accusing another user of being a bot or paid actor. Trolling is uncivil and is grounds for removal and/or a community ban.
Similarly, if you see posts along these lines, do not engage. Report them, block them, and live a happier life than they do. We see too many slapfights that boil down to "Mom! He's bugging me!" and "I'm not touching you!" Going forward, slapfights will result in removed comments and temp bans to cool off.
-
Rule 6: Memes, spam, other low effort posting, reposts, misinformation, advocating violence, off-topic, trolling, offensive, regarding the moderators or meta in content may be removed at any time.
-
Rule 7: We didn't USED to need a rule about how many posts one could make in a day, then someone posted NINETEEN articles in a single day. Not comments, FULL ARTICLES. If you're posting more than say, 10 or so, consider going outside and touching grass. We reserve the right to limit over-posting so a single user does not dominate the front page.
We ask that the users report any comment or post that violate the rules, to use critical thinking when reading, posting or commenting. Users that post off-topic spam, advocate violence, have multiple comments or posts removed, weaponize reports or violate the code of conduct will be banned.
All posts and comments will be reviewed on a case-by-case basis. This means that some content that violates the rules may be allowed, while other content that does not violate the rules may be removed. The moderators retain the right to remove any content and ban users.
Lemmy World Partners
News !news@lemmy.world
Politics !politics@lemmy.world
World Politics !globalpolitics@lemmy.world
Recommendations
For Firefox users, there is media bias / propaganda / fact check plugin.
https://addons.mozilla.org/en-US/firefox/addon/media-bias-fact-check/
- Consider including the article’s mediabiasfactcheck.com/ link
view the rest of the comments
Tbh this is an incredibly easy fix, either cap the number of waters someone can order in software or have an override where a human takes over if an order is suspicious, there's not an infinite number of ways to fuck with this.
Capping waters fixes that one specific issue but not the problem.
A suspicious order isn't easy to define and no person who has ever participated in software development would underestimate the infinite ways a User can break software.
There are machine learning algorithms for anomaly detection though. They actually work decently well because exploits like this do in fact differ significantly from regular orders. Because they assume all anomalies are attempted exploits, their false negative rate is rather low while their false positive rate can be a bit higher.
Taco Bell has the capability to create a decently large training set from all recorded orders (which must all be valid and non-malicious) so they shouldn't have too many issues developing this model.
If an anomaly is detected, make a human verify it is indeed an irregular order.
This is handwaving, which, to be fair, describes a lot of AI "solutions". An anomaly could be as basic as a customer not wanting onions on their burger because the vast majority don't make that modification.
Now what do you do in that situation? Force orders to never have modifications? That customization is such an important feature to the point that burger king adopted it as a slogan with "have it your way".
The idea of anomaly detection is to project some input onto a (high dimensional), numeric output. From the training data alone, you can then see where the projections are clustered and develop a high dimensional "boundary" where everything within is known and good and everything outside is unknown and possibly bad. Since orders come in relatively slow, a human would be able to check for false positives and overwrite the computer decision.
By the way, an ideal training set is preprocessed and has duplicates removed and new orders added by recombining parts of individual orders.
For example, if we have 3 orders:
We could then create the following set:
And so on, and so forth. A naive variant is just taking the power set of all valid orders.
This is more complicated than just having the available menu items, the available modifications, and the limits on quantities to compare against. This is already available through the app/online ordering.
That doesn't prevent someone ordering "everything" at max quantity, which is almost certainly a "malicious" order.
Surely if the person making the order sees 18,000 waters they would think, hold on this doesn’t seem right maybe I should ask the customer if they really want 18,000 waters?
The same applies for the ice cream with bacon on it which was mentioned in the article. I believe a lot of these could be resolved with a bit of common sense.
Sure, in the most extreme cases it would be obvious to the crew. But simply making mistakes at a higher rate than humans will result in a lot of unhappy customers.
Does it, though? Unlike the 18,000 waters, if I were working a drive through I wouldn't even blink at an order for bacon ice cream. Heck, I might make a little extra to try it for myself!
If you think bacon on ice cream is weird enough to cancel an order, I can only imagine you've never worked a customer service job.
Sure, but how do you distill this into a rule a computer can follow? "Suspicious" is not an objectively measurable thing that a program can just check against
Think the easiest way would be to collect order data for at least a good number of months if not a couple years and feed it in and use that as a baseline of what a typical human order looks like, anything that deviates too far from that baseline needs to be handled by a human until someone can validate it as a good order, though I imagine you could get false positives for new menu items unless you set a reasonable instruction for items that have never appeared in the dataset before.
Have you never seen what Americans eat? Bacon Creaminators are excellent.
there is an incredibly finite number of ways to mess with this, they just need a button to send a report to the engineers with how they got messed with and eventually they'll have a complete list. I really doubt it'd take long to iron out the vast majority of ways that can be thought of.
This isn't something you can input any text into, it's fixed, that joke doesn't apply, you can't do an sql injection here.
Close one, a joke was related to but not a perfect match for the present situation. Something terrible could have happened like... Uh...
Let me get back to you on that.
I don't know how you can think voice input is less versatile than text input, especially when a lot of voice input systems transform voice to text before processing. At least with text you get well-defined characters with a lot less variability.
No special characters, this is speech to text, inherently sanitized inputs.
Special characters is just one case to cover. If the user says they want "an elephant-sized drink" what does that mean to your system? At least that is relevant to size. Now imagine complete nonsense input like the joke you responded to ("-1 beers" or "a lizard"). SQL injection isn't the only risk with handling inputs. The person who ordered 18,000 waters didn't do a SQL injection attack.
none of those issues work because there is a whitelist of specific terms instead of a blacklist
-1 cannot be selected, a lizard isn't on the list of inputs, and my point with the sql is that this isn't a huge attack vector like an input field on a website, this is a dropdown list, essentially.
i challenge you to come up with one relevant attack that isn't order too much of a thing or order conflicting modifications (note of course the modifications are also essentially read from a dropdown list)
everyone here seems to believe that the input field paradigm is not solveable when the inputs are fixed, that isn't true.
Sounds like you've never programmed before.
stuck in a loop
stuck in a
stuck in
stuck
If what I was saying was false, there would be the same issues with the touchscreen ones.
Nothing you said there would at all be affected by the difference in input source.
The point is that loopholes in software will always exist that lead to unexpected outcomes.
In software in general? Sure, here? I really doubt it
that's what happens 99% of the time. It's kinda been a trend on the anti clanker side of TikTok, just order a large amount of stuff so a human takes over and actually helps you
Why can't a trillion dollar AI say "Sir, that's not reasonable"?
Because they train these to be your cheerleader, not some back talking reasonable person.
because they prioritize profit acquisition.
It actually crashed, per the article. Presumably because it failed a sanity check.