861–870 of 902 posts
Earlier quoted context omitted.
I get something like that when I try to comment and then upvote too quickly.
There's a manual rate limit that can be assigned to your account if you post frequently on controversial topics. Afaik once it's there it stays until removed by a moderator.
Earlier quoted context omitted.
It makes me wonder how the world would be if monitor manufacturers did the same thing, it would be unacceptable. I view VR headsets and their peripherals as no different than a mouse, keyboard, and display. Companies requiring all this nonsense to use your device, put in that light, is ludacris.
> I view VR headsets and their peripherals as no different than a mouse, keyboard, and display That could be valid when VR headsets were tethered to a PC via a DisplayPort or HDMI connection and essentially mirrored the display. The Quest is closer to an iPhone or Android phone or an all-digital handheld gaming device. With integrated compute, display, battery, text input, pointing devices, mic, and speakers, it bear…
This makes it a device that's generally capable of using any supported source for its screens, and can pass its peripheral input to other devices, like a PC, not unlike a mouse and keyboard.
VR headsets could treat their "OS" as a minimal experience akin to an OSD on a monitor that lets you switch sources and use the peripherals more generally like a mouse/keyboard with the right drivers on the target machine.
I'm more interested in calling out that Meta missed an opportunity here, and that it's confusing that they offer some semblance of these features (wireless linking for SteamVR...) while coupling that so closely to their OS and online-only experience.
Earlier quoted context omitted.
> I view VR headsets and their peripherals as no different than a mouse, keyboard, and display That could be valid when VR headsets were tethered to a PC via a DisplayPort or HDMI connection and essentially mirrored the display. The Quest is closer to an iPhone or Android phone or an all-digital handheld gaming device. With integrated compute, display, battery, text input, pointing devices, mic, and speakers, it bear…
It sounds like a server-side bug that forced a log out somehow. Which does really suck, Meta deserves criticism for that, but acting like this means the headset "isn't standalone" is silly, since that's not what "standalone" means in the context of VR headsets.
Earlier quoted context omitted.
It makes me wonder how the world would be if monitor manufacturers did the same thing, it would be unacceptable. I view VR headsets and their peripherals as no different than a mouse, keyboard, and display. Companies requiring all this nonsense to use your device, put in that light, is ludacris.
comparing it with a monitor is rather unfair, you have to bundle the computing along with it, not to mention the applications to make it an actually fair comparison. At that point, is it still ludacris?
Earlier quoted context omitted.
> plenty of people writing auth code will take the stance all failures are presented the same as a bad password or non-existing username Those people would be wrong. You can take all unexpected errors and stick them behind a generic error message like "something went wrong" but you should not lie to your users with your error message.
It's about not leaking sensitive information. If you have different messages for invalid username vs invalid password, you can exploit that to determine if a user has an account at a particular service. "Invalid credentials" for either case solves this problem. But sure, let's report infra failures different as "unexpected error" Now, what happens if the unexpected error is only when checking passwords, but not usern…
In this case, Facebook does not treat hiding username usage as a requirement. Their password reset mechanism not only exposes username / phonenumber usage, but ties it to a name and picture. So yes, Facebook returning an error that says credentials are incorrect when it has infrastructure problems is absolutely a defect.
Earlier quoted context omitted.
> It's almost never actually an outage impacting all of FAANG at once. Exactly. If you click through down detector when things are _up_ you'll see people still complaining that $site is down. Could be a local power outage or even a flaky connection in their own home. Down Detector is one of many signal sources and should have a "credibly" score associated with it that's proportional to the number of people complainin…
[flagged]
Earlier quoted context omitted.
Pushing people to unnecessarily reset credentials increases risk. Not only does it increase acute risk, but it also decreases the value of the signal by crying wolf. The argument here is the kind of nonsense cargo cult security that pervades the industry.
I think this argument falls flat on two axes: - in general, if the system is broken enough to be giving false-negatives on valid credentials, it's broken enough that there isn't much planning to be done here because the system's not supposed to break. So if they give me "Sorry, backend offline" instead of "invalid credential," they've now turned their system into an oracle for scanning it for queries-of-death. That's…
This is security by obscurity of the worst kind, the kind that actively harms users and makes software worse.
Earlier quoted context omitted.
I can guarantee you with 100% confidence from experience that the call centers for AT&T, T-Mobile, Comcast, etc. are all blowing up right now because of users who assume that if the Instagram app isn’t loading it means the “wifi” is broken. Also keep in mind “wifi” doesn’t mean 802.11, it means “anything related to the internet” up to and including 4g/5g and Ethernet.
Ok great. How does that equate to having down detector filter reports?