I find it very useful when doing CAD (with intent to 3D print something). It lets me quickly sketch rough shapes and note measurements I've taken, visualize ideas to show them to colleagues, do geometry "math" with less chance of messing up. Paper would work just fine, I guess, but RM has editing and undo, so reworking large regions doesn't result in attempts of striking out with more ambiguous lines.

So, to generalize, I'd suggest it for people that do bespoke construction of some sort often.

Why is your life more worth than mine?

> API necessarily provides at least the data point of, "Did they select an option in the permission notification?"

If a bird app (or, heck, pancake recipe site) asked for WebRTC or GPU access I would be rightfully suspicious. It's a shame these things don't happen.

They do ask for location data, and it tends to mostly work - sites like openstreetmap will ask for it when you press the right button for example, which makes sense.

There is a risk that it ends up like cookie banners, and the adtech industry manages to brainwash the world into thinking that the government is the bad guy and they just want some harmless data to share with their 1,345 best friends and they are “forced” to show these. Despite there being no requirement at all to track data, and they break the law with it anyway so why bother.

This is a poorly explored avenue. I think a lot of these more advanced APIs ought to be permitted to "installed" PWAs. Maybe it could even look like permissions menu for apps in phone OSes.

I was a bit dismayed when mozillians in the bugtracker dismissed the idea of requiring consent to initialize WebRTC. F'k it, scan the local network.

Didn't work out for Organic Maps. Merely allowing to access map data makes you un-family-friendly. Or at least that's what we can assume, since Google won't indulge in specifics. https://news.ycombinator.com/item?id=41272925

Amazing. This is probably the correct way do make amp controls. I'd say the volume should be a multi turn trim potentiometer in the back of the device so you don't have to brief your guests on correct operation.

>Now that this Global Outage happened, it will change the landscape a bit.

I seriously doubt that. Questions like "why should we use CrowdStrike" will be met with "suppose they've learned their lesson".

I'm referring to the landscape how current Cybersecurity vendors deliver "detection definition" (for lack of better phrase) to their customers.

If you don't send them fast to your customer and your customer gets compromised, your reputation gets hit.

If you send them fast, this BSOD happened.

It's more like damn if you do, damn if you don't.

> If you don't send them fast to your customer and your customer gets compromised, your reputation gets hit.

> If you send them fast, this BSOD happened.

> It's more like damn if you do, damn if you don't.

What about notifications? If someone has an update policy that disable auto-updates to a critical piece of infrastructure, you can still let him know that there's a critical update is available. Now, he can do follow his own checklist in order to ensure everything goes well.

What if they're sleeping and won't read the notification until they wake up?

Wouldn't they get compromised?

most people will defer updates indefinitely if they are able to.

Okay, but who has more domain knowledge when to deploy? A "security expert" that created the "security product" that operates with root privileges and full telemetry, or IT staff member that looked at said "security expert" value proposition and didn't have issue with it.

Honestly, this reads as a suggestion that even more blame ought to be shifted to the customer.

The AV definition delivery is part of UX of the product.

That would be equivalent to asking "would you prefer your fleet to bluescreen now, or later" in this case.

Presumably you could roll out to 1% and report issues back to the vendor before the update was applied to the last 99%. So a headache but not "stop the world and reboot" levels of hassle.

With the slight difference that you can stop applying the update once you notice the bluescreens

Those eager would take it immediately, those conservative would wait (and be celebrated by C-suite later when SHTF). Still a much better scenario than what happened.

You don't have to do a full loop if you need an adjacent exit. Eases load on the rest of entrances.

Ah, that makes sense. Thank you!

How is that specific to React? And who would use webapp technology for a website?

According to cheema33 React is most "popular frontend stack", but I'm not allowed ask questions of why websites demand JS to display basic content... I suppose my reply could have been more _constructive_ as to ask "by whose count" or "how does popularity correspond to quality" but that's like playing chess by one step in front of you.

Look, I'm seeing an increase of blogs made with an implication that _infinity_ amount of visits requires less resources than one and I don't just find it true.

Yeah, feels more like another reason to hate them for contributing to the enshittification of the web.

This doesn't make Recall any better.