A misconfigured world-open resource is a huge security risk, but world-open resources have valid use cases. The only signal Amazon has that somebody might have misconfigured a resource to be world-open is if somebody tries to access it with authentication credentials, so they decided to interpret that configuration as "hey user, did you really intend for this to be world-open?"
We can't correct those because backwards compatibility is necessary to creating a global network that lasts decades. It's the railway effect... One simply can't expect every player to update their architecture religiously because they can't afford to, therefore what is made public tends to stick around for ages, and anything that fails to recognize that stickiness (IPv6 is my go to example) does so at its own peril.
The number of services I use that I wish had a "warning" side-channel for letting me know something in my query was off, let me tell you...
In fact, it's the recommended way to do things like tell a client things it might need to know. Example: "The game servers will be shutting down in 15 minutes for maintenance."
Working code and rough consensus is how we progress.
What's wrong with that? The only issue I see is the _in their opinion_ bit. If there's confusion about the spec, then it should clarified and codified. But otherwise: yes, you should absolutely aggressively reject everything not in spec.
"Public-readable resources get requested a lot, with no predictability over who or how many independent agents could be requesting them at once; so, to decrease the likelihood of requests on such resources DDoSing our backend, we could at least limit there to being exactly one canonical way to acceptably request the URLs of such resources. That way, such resources will end up hot in any edge-cache after the first request, and any non-normalized requests will break [and so be removed from the logic] — rather us needing to serve the same resource multiple times to get it saved under under multiple cache keys."
(I'm guessing that S3 also errors out if you submit random unrecognized query-string parameters on such requests?)
Doesn't look like it. I checked out the recent bankruptcy filing that was posted to s3, and you get the doc just the same with or without random query params:
https://pacer-documents.s3.amazonaws.com/33/188448/042120640...
https://pacer-documents.s3.amazonaws.com/33/188448/042120640...
Have you even met Siri? Let me relate an interaction I had with it last Sunday, driving home from the Thanksgiving holiday weekend. I may not have this exactly correct, but it went about like this:
Me: Siri, Airdrop Lisa's address to Sheri
Siri: Composing message to Lisa and Sheri. What would you like to say?
Me: Cancel
Siri: Got it. Would you like me to send the message now?
Me: Don't send.
Siri: "Sent!"
Sheri and Lisa received an email titled "Address" with message body "Cancel."
> Siri: "Sent!"
This suggests that it didn't.
What I recommended is a known solution, and has worked very well for me:
https://www.pcmag.com/how-to/apple-siri-tips-and-tricks
https://www.youtube.com/watch?v=TyUz6t7W1vk
https://osxdaily.com/2016/05/03/improve-hey-siri-voice-train...
https://www.applemust.com/ios-how-to-make-hey-siri-more-accu...
I suppose the tribalism surrounding communication device logos makes these sorts of technical suggestions risky.
Even now I can’t get Siri to share an address using Airdrop. I don’t think it’s possible. It looks like it can text the address but even that is dicey.
Let’s hope Siri improves for everything else!
Siri understands my voice just fine. It just doesn’t know how to interpret the request.
Now to be fair I was in my car on the highway and not looking at my phone so I don’t know exactly what it heard in this specific example. I’d made several attempts to word my request to send an address from my contacts to my wife’s phone. I worded it several different ways, and each time Siri didn’t seem to know what to do. This was the final attempt and as I said, perhaps I don’t have the exact exchange correct here.
I attempt to use Siri frequently and even when it hears what I’m saying often doesn’t understand the request. Here’s another example:
Hey Siri text Jessica, <pause> “Candles question mark”
Siri: there’s no one named “Jessica Candles” in your contacts.
I’ve learned I have to do this instead:
“Hey Siri, send a text”. Then wait for Siri to prompt: “Who would you like to text?” Answer with “Jessica”. Then wait for Siri to prompt: “what would you like to say?” Then answer “candles question mark”. All to get it to text my daughter the message “candles?”
Another time I tried to get Siri to tell me when my daughter’s train was due in at the Amtrak station. This was not a request without context. The trip was both in my email and on my calendar, and my phone was already navigating me to the Amtrak station but I wanted an update on the train’s progress. Siri either attempted to give me directions to my daughter’s address 200 miles away or to give me directions to the Amtrak station, and not even the station nearest to me, which the phone was already navigating me to. Is it really so unusual that someone headed to a train station or airport might want an updated ETA for the flight or train they were headed to pickup someone from? Why can’t Siri understand that request?
I could go on with dozens of example of things it gets wrong. How about this: “Siri, close the garage door.” Siri replies: “which garage door?” Even though only one door is open. It also doesn’t know what to do with “close both garage doors.” Sometimes saying “close all garage doors” works, but sometimes not.
Or how about when I ask Siri on my AppleTV to search for a movie and it starts playing a song instead? I have to very carefully tell it “search for the movie named …” and even then it sometimes gets it wrong.
But hey, at least setting timers works. Really well!
I do appreciate your attempt to help. Siri hears me fine. It just sucks at understanding what I want, whether I speak to it like an adult or coddle it like the stupid voice assistant that it is.
(this will never happen, requires power down.)
I suspect resources have been pulled with the realization that there's no real way to monetize people asking it to set timers, tell them the weather, or tell them what time the Rams game is on, which is about the extent of what most people use these things for.
If Siri didn't suck big time I would use it all the time.
You might as well say “the camera does not bring revenue to Apple so they intentionally didn’t develop it any further”, which is nonsense.
Siri has ongoing costs to run the servers.
But even those are outliers. Most people like the built in convenience of Photos and automatic cloud sync to other devices and it "just works".
As an aside, Apple used to charge for OS updates. Then they decided supporting multiple versions of the OS was idiotic (maybe they had other reasons as well) and reduced the cost/then went free.
https://arstechnica.com/gadgets/2022/11/amazon-alexa-is-a-co...
> We have to wonder: Is time running out for Big Tech voice assistants? Everyone seems to be struggling with them. Google expressed basically identical problems with the Google Assistant business model last month. There's an inability to monetize the simple voice commands most consumers actually want to make, and all of Google's attempts to monetize assistants with display ads and company partnerships haven't worked. With the product sucking up server time and being a big money loser, Google responded just like Amazon by cutting resources to the division.
> While Google and Amazon hurt each other with an at-cost pricing war, Apple's smart speaker plans focused more on the bottom line. The original HomePod's $350 price was a lot more expensive than the competition, but that was probably a more sustainable business model. Apple's model didn't land with consumers, though, and the OG HomePod was killed in 2021. There's still a $99 "mini" version floating around, and Apple isn't giving up on the idea of a big speaker, with a comeback supposedly in the works. Siri can at least be a loss leader for iPhone sales, but Apple is also hunting around for more continual revenue from ads.
Apple’s strategy is different where Siri is a convenience feature for the devices that they sell for a premium. I doubt that Apple has invested anywhere close to $10B in Siri.
We haven’t heard of Google is bleeding to the degree that Amazon is on the Google assistant. I suspect not.
“Siri, put on my focus playlist”
“Okay, playing your focus playlist on Deezer”
“Siri, take me home”
“Getting directions to home”
“Siri, take me Cornish Pasty Co.”
“Okay, getting directions to Cornish Pasty Co.”
“Siri, play DefCon Radio on Soma FM”
“Okay, playing DefCon Radio on Soma FM”
It integrates with Apple Car play too. Nearly everything I’d interact with the center console for before, Siri does for me now.
DAMN YOU SCIENCE FICTION AUTHORS YOU'VE INDIRECTLY DOOMED US ALL
- "Do not open door A1" - "You are not authorized. Opening door A1"
I thought it was funny, and a bit silly since computers, even when malfunctioning don't act like that. But with current AI developments and people not explicitly programming stuff just trying to coax AI to behave correctly this scenario begins to seem perfectly plausible.