Over the years, I've grown so accustomed to using Mac keyboards on Windows that I swap the positions of the left Alt and Windows keys when using PC keyboards.
Is there a reason they can't offer the previous theme as an installable theme for the new theming system?
This would be a lot more convenient than putting it behind an about:config-only preference that you need to jump through hoops to sync (and that's more likely to be removed sooner than the new theming system).
They don't use inline assembly. They hardcode the preassembled syscall function in a char array, mmap an anonymous write+execute memory page, copy the bytes from the array to the newly mapped page, store the address of the page in a char pointer type punned to a function pointer using union shenanigans to avoid compiler warnings, and call the function through the function pointer (which is obviously nonportable, but presumably valid implementation-defined behavior since it doesn't elicit a warning when compiled with -Wpedantic).
The school could presumably plug this particular hole by locking down mmap and mprotect at the syscall level with seccomp.
The full proof of concept code[1] is in the linked GitHub repo.
Specifically, either a registered name or a subdomain of a registered name reserved for this purpose, because the A records for the apex should or must — I don't remember which, but it's definitely the default configuration — point to the domain controllers, and you probably don't want to host your public web site on the same addresses as your DCs (or for that matter, your internal and public records necessarily hosted on the same server).
Historically (20+ years ago), some Microsoft documentation suggested .local as an example of an unregistered domain that could be used for this purpose, which was problematic when .local was subsequently reserved for multicast DNS.
Given that there don't appear to be any BGP announcements for 25.anything, is it possible that the MoD uses this address range internally, or not at all, and has agreed to continue to do so?
Looking at your links, subjective and legacy considerations aside, .alt per RFC 9476[1] seems as good a choice as .lan.
Personally, I just use a registered domain for this purpose, as they're cheap enough to not care (last I checked, I pay $10–20/domain/year for registrations, depending on registrar and TLD, and $0.21/zone/month for hosting public zones on Google Cloud).
A registered domain has the added benefit that you can use the same namespace for externally accessible services. I personally do this (using Cloudflare Tunnels, not open ports).
Probably more, but not necessarily functionality users requested or even know about.
Case in point: VSCode has a multistage "upgrade project to the latest .NET runtime with Copilot" process that takes several minutes of processing punctuated by frequent authorization prompts for even the most trivial project, resulting in the functional equivalent of
find . -iname '*.csproj' | xargs sed -E -i.bak 's/(net)8(\.0<\/TargetFramework>)/\110\2/'
along the happy path.
It has many more features than my shell command, of course, but none that I care about when migrating trivial projects from runtime version n-1 that are unlikely to hit breaking runtime or compiler changes that don't elicit warnings from the toolchain.
I’m starting to think the ones that “adapt” the most are the ones most likely to burn out, as their productivity collapses under the weight of code and related artifacts that neither they nor their “interns” are qualified to understand.
reply