So yesterday, June 8th, Amazon quietly flipped a switch on basically every Echo and Ring device in the country, and unless you went digging through a settings menu sometime in the last few weeks, you're now part of it whether you like it or not. I'm talking about Sidewalk, the mesh network thing Amazon announced last year that borrows a slice of your home internet bandwidth to help other people's devices stay connected. It went live yesterday, opted in by default, and I've seen approximately zero mainstream coverage explaining what that actually means for the guy with two Echo Dots plugged into his kitchen and hallway outlets. That guy is me, by the way.
Here's the pitch, roughly: your Echo or Ring device shares a small chunk of your bandwidth (Amazon says up to 500MB a month, which they compare to about a minute of video streaming, thanks for the metaphor Amazon) to extend the range of a low-bandwidth network that other Sidewalk-enabled gadgets can hop onto. A neighbor's Tile tracker loses its phone connection, your Echo picks up the slack, everybody's stuff supposedly works better at the edges of Wi-Fi range. Ring's smart lights and some Level locks are the first non-Amazon devices actually using it. It's not a crazy idea on paper. Community mesh networks are neat! I like the theory!
What I don't like is that I had to find out about the opt-out through a tweet, not through Amazon actually asking me. You turn it off in the Alexa app, under Settings, then Account Settings, then Amazon Sidewalk, and if you didn't know to look there in the last month, it's just on now. I did the toggle last night, both devices, took maybe forty seconds once I found the screen, and I'm still annoyed it needed forty seconds at all. This is the same playbook every company runs now: ship the feature enabled, put the switch three menus deep, let the privacy blogs do the work of telling people it exists. Facebook's been doing this for a decade. Now it's on my kitchen counter.
I'll say the actual privacy exposure here is probably smaller than the Twitter panic made it sound. Amazon's published a decent amount about the encryption layers, and your neighbor sharing your bandwidth doesn't mean your neighbor sees your browsing history or whatever. But "probably fine, trust us" isn't really the standard I want from a company that also makes a doorbell camera product, and the complaint isn't really about the security architecture anyway. It's about the default. If the feature's genuinely good, sell it to me and let me say yes. Don't make saying no a scavenger hunt.
Small tangent, only sort of related: this was also the same week half the internet fell over because of one company. Fastly, the CDN a lot of huge sites route through, had a configuration issue Tuesday that took down Reddit, the New York Times, Amazon's own retail site for a bit, even the UK government's gov.uk pages, all at once, for about an hour. I happened to be trying to look something up on gov.uk of all places when it happened and just got a blank error page, then went to check Reddit out of habit like you do, and that was down too, and it took a solid five minutes before I connected the dots that this wasn't just my wifi being bad. Different company, different problem, but there's a theme this week if you squint: a small number of businesses quietly sitting underneath a huge amount of stuff we do online, making decisions (or having outages) that ripple out way past their own customer list. Sidewalk is Amazon volunteering your router as infrastructure for a network you didn't ask to join. Fastly is a config push somewhere in San Francisco taking out a UK government tax site. Neither of those things used to be possible at this scale, and now they're just Tuesday.
Anyway. Go check your Alexa app if you've got Echo hardware and you care. It's a genuinely quick fix once you know where it lives, which is sort of the whole problem in miniature.