I wonder if the next obvious attack - 2 pushes in rapid succession, one to show and one to hide - has been handled. The browser should debounce and replace the notification with a notice instead of hiding if it’s removed too quickly. Human time scales.
Given that Windows 11 isn't that different from Windows 10, I assume the app compatibility toolkit can be coaxed to work.
Or, more excitingly, probably more versatile in the longer term, and a pile of hacks upon hacks, it might be possible to run in the browser with the likes of jslinux + wine.
Please, stop pluralizing "BSD's", every BSD it's different and OpenBSD only reuses Linux drivers for KMS/DRM; FreeBSD has special layers and tons of drivers ported and NetBSD it's closer to philosophy in design.
So GNU/Linux now it's in the same group as FreeBSD as it has ZFS? Because neither NetBSD nor OpenBSD have it.
OpenBSD doesn't 'rely' on Linux drivers, thanks. Just a shim against KMS/DRM, everything else it's either homegroup or sometimes adapted (back and forth) from NetBSD but OFC patched for correctness and security. There's no ALSA. Pulse it's totally optional. There's no wpa_supplicant except for Eduroam or simlar niche crap under OpenBSD.
OpenBSD has OSS and sndiod. There's Xenocara, an X11 fork.
Again, not Linux, X11, MESA and Gallium are damn generic. Show me the rest of ported Linux drivers into OpenBSD, please.
Nope. The best we could do was to create a separate service that creates Docker tokens (using "docker login") and exposes a secure API.
Obviously, GitHub needs to just fix this nonsense. But I interviewed a couple of "senior" engineers from GitHub, and I have zero hope of that happening soon.
Bandwidth is problematic for mesh. A remote assistance situation would involve at least 4 high definition camera streams, and ideally with minimal latency. It's challenging to put that much data onto public spectrum even if you wanted to make a custom radio.
I was thinking more for communicating the “mass disruption in progress” message - or even just distributing the manually verified “traffic lights down” data between vehicles.
> When you run Get-Mailbox -Identity <MailboxIdentity> | Format-List AuditEnabled, the AuditEnabled property always displays as True. This hardcoded display value doesn't reflect the actual mailbox-level audit configuration.
> To verify the actual mailbox audit status, use the Filter parameter in the following command:
PowerShell
> If the command returns the mailbox object, mailbox-level auditing is enabled. If the command returns an error stating the object couldn't be found, mailbox-level auditing is disabled.
Traditionally they have a bias towards "working"/delivering traffic. It's easier to issue a refund than answer a urgent support request.
I can also imagine the biggest customers have all sorts of multi-vendor failover plans that may be affected.