Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Meta outage

metastatus.com

Post reply on HN
Print view View original

771–780 of 902 posts

Re: Meta outage

#771

Post by xp84 »

TulliusCicero wrote: post #564
bloaf wrote: post #343

Earlier quoted context omitted.

I think the current buzz in the VR space is the "Bigscreen Beyond" which eschews all of the nice-to-haves in order to make the headset as light as possible, and the result is surprisingly compelling.

It looks compelling for high-end PC gaming VR enthusiasts, but if GP is more of a mainstream consumer it probably won't make sense for them. At least from what I've read, there's a bunch of downsides for regular consumers: very expensive ($1000) -- SUPER expensive if you bundle in controllers and tracking points (~$1600), needs external tracking, wired instead of wireless, no built-in audio, can effectively only be u…

Great news: Thanks to Apple, $1600 is now a budget super-economy VR headset!

Courage.

Re: Meta outage

#772

Post by marcosdumay »

callalex wrote: post #718
ndiddy wrote: post #535

Earlier quoted context omitted.

I see the "sorry, we are receiving too many requests, try again in a few minutes" error several times a day on here. I don't think that HN is reliably able to handle the amount of users it currently has.

That is a generic rate limiter that is independent of system load. As far as I can tell if you make more than one request per every 5 seconds, you will always be served the rate limit page.

The message for this is something like "we can't serve your requests that fast". The GP is quoting the site overloaded message.

Re: Meta outage

#774

Post by ben_w »

citrusybread wrote: post #644
TulliusCicero wrote: post #439

Earlier quoted context omitted.

The Quest 3 is kind of the obvious mainstream consumer choice for a VR headset. Standalone wireless headset, reasonably powerful chipset, can optionally stream from a PC either wired or wireless, good optics/resolution, decent controllers/tracking, large game library, large suite of features (including hand tracking and color passthrough), all for a reasonable price. Not sure any other headset really competes on all…

can we really call it standalone if you need it to phone home to Meta? and doesn't it require an account one of their services too? they did a fantastic job with hardware. I just wish they didn't couple the software so tightly.

> can we really call it standalone if you need it to phone home to Meta?

Yes, because etymologically it's "standalone" vs. "wired"; this is akin to how phones are "mobile" vs. (when I was a kid) "landline".

Re: Meta outage

#775

Post by TulliusCicero »

agar wrote: post #764
docmars wrote: post #700

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…

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.

Re: Meta outage

#776

Post by blastadon »

DeusExMachina wrote: post #281

Looking at the Downdetector home page [1], it looks like many more services are having outages, not just the ones owned by Meta, including: - Google - YouTube - Google Play - T-Mobile - X (Twitter) - Discord - TikTok - Pokemon Go - Snapchat It looks like they all have the same failure point. [1] https://downdetector.com

Yeah, I had issues accessing GCP's documentation site for AlloyDB around 8:00-9:00ish Eastern this morning. The page just said 'Service Unavailable'. Had to use Google Cache.

Re: Meta outage

#777

Post by TulliusCicero »

ben_w wrote: post #774
citrusybread wrote: post #644

Earlier quoted context omitted.

can we really call it standalone if you need it to phone home to Meta? and doesn't it require an account one of their services too? they did a fantastic job with hardware. I just wish they didn't couple the software so tightly.

> can we really call it standalone if you need it to phone home to Meta? Yes, because etymologically it's "standalone" vs. "wired"; this is akin to how phones are "mobile" vs. (when I was a kid) "landline".

Nitpick: strictly speaking it's standalone vs tethered (which is usually wired, but could be wireless).

Re: Meta outage

#778

Post by schrodinger »

Cheer2171 wrote: post #606
rimunroe wrote: post #551

Earlier quoted context omitted.

> I don't really trust Down Detector, which despite the claims is really People Winging on Twitter Detector. I'm confused. Isn't listening for spikes in complaints about outages a great way to detect them? I know for a fact some service companies monitor social media channels for this purpose (among others). I'd be surprised if that wasn't more or less standard practice. I've checked Down Detector for ISP outages in…

The problem is that people use FB login for other sites, and if FB login is down, many users report a problem with that other site, not with FB.

The point is that the “other site” _is_ down for those who use Facebook to login to it.

Maybe they should have a backup password (if they site allows it, f-ing Spotify doesn’t), but it’s still effectively down for them!

Re: Meta outage

#779

Post by agar »

TulliusCicero wrote: post #775
agar wrote: post #764

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.

Agree, many posts I read seem like classic "I don't like Meta/VR/big companies/social media so let me use this specific incident to confirm my biases."

As you say, there's valid criticism to be made but it's hard to find the signal through the noise.

Re: Meta outage

#780

Post by jessriedel »

Kalium wrote: post #728
jessriedel wrote: post #662

Earlier quoted context omitted.

Isn't this just the standard problem of reporting useful error messages? Like, yes, there are academic situations where you can't distinguish between two possible error sources, but the vast majority of insufficiently informative error messages in the real world arise because low effort was applied to doing so.

Yes and no. Yes, with the additions of sheer scale, a vast number of services, multiple layers, and the difficulty of defining "down" added in. I think the difficulty of reporting useful error messages is proportional to the number of places an error can reasonably happen and the number of connections it can happen over, and by any metric Meta's got a lot of those. No, in that detecting when you should be reporting a…

> If a service you call gives you a nonsense response, what do you surface to the user?

If this occurred during the authentication process, I think I would tell the user "Sorry, the authentication process isn't working. Try again later." rather than "Invalid credentials". And you could include a "[technical details]" button that the user could click if they were curious or were in the process of troubleshooting.

Post reply on HN