fowl2

Telco networks are sprawling and accurately defining the boundary might be harder than it sounds.

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.

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.

Also no mention of Firefox in the article ;(

It might be possible to create/use some app compatibility shims:

https://techcommunity.microsoft.com/t5/ask-the-performance-t...

https://learn.microsoft.com/en-us/previous-versions/windows/...

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.

eg. https://github.com/lrusso/WinAppRunner or https://github.com/DustinBrett/daedalOS

If you get that working, that'd be really exciting.

Windows already does, so you’re talking about the BSDs or Darwin?

So:

1. Apple froze the Safari user agent in iOS 26 to be the same as iOS 18.6, so stats websites are reporting under-reporting.

AND

2. Apple is for some reason rolling out/'recommending'/'pushing' automatic updates in iOS 26 than in previous releases.

Yeah wow! Even most "trusted" contributors shouldn't have this level of access. Is there really no way of scoping tokens with more granularity?

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.

I wonder if the cars also have some sort of mesh (LoRaWAN?) network to help each other out in temporary dead zones, emergencies, etc.

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

Get-Mailbox -Identity <MailboxIdentity> -Filter "AuditEnabled -eq 'True'"| Format-List

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.

https://learn.microsoft.com/en-us/purview/audit-mailboxes?so...

Would really benefit from some more technical details. I wonder if they rolled this out to client/Windows 11 first for some lower stakes testing.

Incredible that no one from Google noticed this as a regression from their side and either put a workaround in or contacted Wikimedia.

Interestingly the public of Azure’s etcd-compatible service was withdrawn before exiting preview.

[1] https://learn.microsoft.com/en-us/answers/questions/154061/a...

Seems like there’s a few places Postgres could benefit from some more consistency checks.

(kinda) suprised there isn't environment variable to do this all in one go.

Many of these can definitely be set/automated using policies.json[1]

[1] https://support.mozilla.org/en-US/kb/customizing-firefox-usi...

Suprised no one has mentioned RFC 8914 Extended DNS Errors, specifically section 4.17[1]:

4.17. Extended DNS Error Code 16 - Censored

The server is unable to respond to the request because the domain is on a blocklist due to an external requirement imposed by an entity other than the operator of the server resolving or forwarding the query. Note that how the imposed policy is applied is irrelevant (in-band DNS filtering, court order, etc.).

Which would be relevant for Google DNS's "Query refused" at least. Although I guess it's possible maybe they do support it but Windows/Chromium don't...

[1] https://www.rfc-editor.org/rfc/rfc8914.html#section-4.17

Binary compatibility is necessarily at odds with the “recompile the world” philosophy. This global view has some advantages, eg. performance can be improved system wide LTO, calling conventions changes, security with hardening options, etc.

The local view, where a program with no knowledge of its runtime environment could appear at any time to a runtime environment that similarly knows nothing about a program, loses all those advantages and costs added constraints but gains.. the ability to run those programs.

The article argues that the balance should be shifted, to their (eventual) benefit, sure. I wonder how long until that would take.

I wonder if there’s more “pay for play” path. I guess that’s containers. Or maybe what they argue for but bundled software could stay the way it is now. Further bifurcation seems bad, adding more code paths to test etc.

Presumably there's some reason Go can't just use an embedded manifest[1] like everyone else?

Ahh, I'm inferring (from [2]) even with the manifest entry, a system wide registry key is also required to get long paths working:

I'm working with the Windows security team to find a way to enable long path support without having to modify the registry, just by using the embedded manifest, but the chances of this happening soon are quite low.

[1] https://learn.microsoft.com/en-us/windows/win32/fileio/maxim... [2] https://github.com/golang/go/issues/69853

Oh wow didn't really expect anything other than whole device loss. Just returning garbage does sound bad.

Do you know if they tried to communicate with clients and were just ignored/not implemented or if the APIs just don't support it?

A quick search indicates that "residency"[1] exists, but no idea the extent it's useful/implemented.

[1] https://learn.microsoft.com/en-us/windows/win32/direct3d12/r...

I guess "hibernating" (writing VRAM to swap) works better than expecting userspace to gracefully handle device resets. One linear read vs. a thundering herd of processes re-initialising, decompressing, etc. should be more predictable/reliable at least.

I do wonder however how much VRAM is "volatile" - ie. framebuffers - and could just be thrown away. And web browsers seem to handle GPU resets just fine, so maybe they could opt-in?

A seemingly coordinated release with the nominally independent FerretDb? What’s the relationship here?

Huh. Apparently the “current plan without AI” is $20 more expensive than “current plan”. Guess I’m grandfathered or something.

Wonder how this compares with the Consumer Data Right in Australia. The standards and discussions around them are right there on GitHub [1] - pretty surreal seeing accounts for the big banks. Of course it's mostly completely useless for anything DIY as semi-understandably access to any real data is gated behind certification requirements.

[1] https://consumerdatastandardsaustralia.github.io/standards/#...

There is a distinction in the dotnet world too. The docs[1] seem to refer to ABI as "Binary compatibility" and API "Source compatibility".

Jon Skeet has some good examples [2]

[1] https://learn.microsoft.com/en-us/dotnet/core/compatibility/... [2] https://codeblog.jonskeet.uk/2018/04/13/backward-compatibili...

Anyone have a textual version?

Depends on your perspective :)

"Origin" is a term from web browsers, from their point of view it refers to where a web page came from.

see https://developer.mozilla.org/en-US/docs/Web/Security/Same-o...

"supporting Linux on laptops with Windows on Snapdragon"

blinks rapidly

edit: I guess if you squint really hard to read "Windows" as "PC-style operating systems" (or "general purpose computing") it makes sense?

yes the beautiful advantage of having some super-forked kernel.

the solution is to get everyone on the same kernel, which is then updatable - not hack together something that kinda works on top of a never updated snowflake

I mean there's tons of IDLs, so many no one can agree on which one!

oblig: https://xkcd.com/927/

I mean, good? Physical access to a device shouldn’t automatically mean all your data is with the wind.

Theoretically this was already on for “new” devices since sometime in the Windows 10 timeframe.

(this has not been merged yet, Linus has thoughts[1])

[1] https://lore.kernel.org/lkml/CAHk-=wj1vvUhNd_+s8Cuvh-wO2iT7b...