Sure, but you still can use your own hardware if you choose to. And that's all that the original comment you replied to was saying. If you choose to use your own hardware, then Comcast won't have control over it and cannot do this wifi motion detection.
Of course, most people won't do this, but that's besides the point.
…and most people don’t. it’s an additional expense, additional work, and frankly not worth the headache for like 80%+ of users.
I used to work in this space, and have first-hand knowledge about the prevalence of third party modems with a sample set of over 100k people. What’s your experience?
They're talking about MTP, which is supported by every modern (and old) Android device AFAIK. It's not exactly a USB Mass Storage device, but as long as you're not on a Mac, it behaves basically the same as one.
Ah, I was mistaken. I thought they were saying that the reason Apple supports MTP (as opposed to UMS) is not that they want to make iPhones look good, but for some other unspecified reason (which I assumed was patent licensing). But they were actually saying that Apple does not even support MTP.
And even if you are using a "regular" video format like mp4, browsers will still use range requests [1] to fetch chunks of the file in separate requests, assuming the server supports it (which most do).
I used winaero tweaker [1] to disable web search, the search is infinitely better now.
You can do the same tweak by editing the registry [2] if you don't want to download an app for it (though the app includes a lot of additional useful tweaks).
This is only true recently! Through most of history people lived and died with technology and culture nearly identical to that of their parents / grandparents. In terms of tech and cultural evolution, we are on the uptick of a hockey-stick growth.
It's absolutely accurate that `kids these days` have grown up in a different environment than `grownups these days` than the same demographics from 50, 100, 200, or 1000 years ago.
Error values should be of the form ErrFoo:
var ErrFormat = errors.New("image: unknown format")
But the page says:
// But if you want to give it a longer name, use "somethingError".
var specificError error
result, specificError = doSpecificThing()
And also says:
Don't do this:
[...]
var errSpecific error
result, errSpecific = doSpecificThing()
So should error variables written like `errSpecific` or `specificError`? The go wiki says they should be written starting with `err`: https://go.dev/wiki/Errors#naming
So a public variable error should follow different naming conventions then a local variable? That doesn't seem right, the go wiki says you should use the 'err' prefix for both (capitalized for public variables though, obviously)
And I'm only asking about when you are giving an error a distinct name, not just naming it 'err'.
It blows my mind that somebody would get an answer from ChatGPT and post it here as a fact without doing the bare minimum to verify that it is actually true. It's insane, thanks for correcting them.
Gaming history is already filled with half-truths and straight up misunderstood things turned into lies because no one cares to write about anything but the players' perspective. Of fucking course the useless LLMs are going to start hallucinating bullshit when they try to navigate that.
I think it would have been interesting to send two down, one oil-filled and one not and see at what depths they break (or don't). The watches are cheap enough that destroying one isn't much of a loss.
I use an esim.me card in my phone and once you program the card with the esim.me app, it shows up as a normal physical sim card on the phone with whatever plan the esim was for. I believe you can even move it to another device and it will still show up with the same plan, though I haven't tried that.
The only issue I've had with it is that some esim provider apps refuse to work on a phone that doesn't have esim capabilities, and since the phone sees the card as a normal sim card, the apps don't work. I assume that will be an issue for any of these cards. Not a huge issue though, most esim apps/websites will still let you get the QR code or download the profile even if your phone doesn't natively support esim, and you just enter that into the esim.me app to program the card.
Of course, most people won't do this, but that's besides the point.
reply