0zymandiass
Your comment seemed to imply that a source release would trigger a different timer than a binary release, which is explicitly covered as the same thing in the law - for both the 4 and 6 month timers.
> or, if the source code is not publicly released, after an update of the same operating system is released by the operating system provider
They have not released the source code, but they have released an update of their operating system on their reference Pixel hardware.
Therefore, all devices must update within 4 months of that Pixel release, regardless of source drops, per this law
```This definition excludes signatures and some metadata and focuses solely on the payload of packaged files in a given RPM:
A build is reproducible if given the same source code, build environment and build instructions, and metadata from the build artifacts, any party can recreate copies of the artifacts that are identical except for the signatures and parts of metadata.```There are various repositories with 500k+ commits
Cluster computing can be useful, but until you're talking about petabytes of data, it probably isn't helping you
> Software engineering does not put safety first
I'm 100% agreed.
If the conversation is
> The PinePhone has less quality control than Android/iOS
It's patently false
I would parse the article as the second, as it's referring to a specific phone throughout
(not to mention they're just plain wrong about the battery/thermal not having hardware-level limits)
The motherboard just loads BIOS/UEFI into a predefined memory address and then starts the CPU
This is a pretty good explanation https://manybutfinite.com/post/how-computers-boot-up/
> In a multi-processor or multi-core system one CPU is dynamically chosen to be the bootstrap processor (BSP) that runs all of the BIOS and kernel initialization code
These days, the "bootstrap processor" is a separate core that your OS can't see. On Intel it's the IME (running Minix) and on AMD it's the PSP (ARM TrustZone)
They've become a bigger concern with UEFI since it has a massive attack surface compared to legacy BIOS.
For a processor sitting in AWS / Azure, they want guarantees, and they're the ones EPYCs are designed for.
The responsibility has to rest with the processor, since it's the only thing executing code prior to UEFI. What it's doing is validating that UEFI was cryptographically signed with the correct key prior to running any UEFI code. When it's first used, it is saving the key for the vendors UEFI implementation and won't allow it to proceed if the root signature ever changes (think something similar to root certs for HTTPS).
It's only relevant to Secure Encrypted Virtualization insofar as they are both implemented inside the PSP which is a separate ARM core that runs at a higher privilege level than the x86 cores (and is the core that actually initializes the x86 cores).
This is how all phones have worked for many years, but apparently it's now becoming a thing in servers too.
It also won't necessarily work in other Dell motherboards, just ones using the same key as the first.
It's strange Dell would blow the fuses by default, though.
Businesses don't have enough need for summer workers to pay them
If you had ubi, then you could still take those jobs for additional income for hobbies, travel, etc.
As it is right now, you're losing money by taking these jobs.
When it read back super incorrectly from an alias, I said something to the effect of "could you pronounce that correctly?" and it asked me to say it
Since then, it's understood that person's name. ¯\_(ツ)_/¯
It really needs to expose the option to train those easily
> I spoke with Verizon about the usage. They said it's getting categorized as audio and video streaming, but only because it's using network ports normally associated with those types of services.
Do you actually need clipboard events, or just dom.event.contextmenu.enabled for that?
My work has switched to iPhones, and I really miss NoScript when using Safari
I've only ever seen that setting fix sites that try to prevent you from copying.
You can't do it through a user agent, though
Why else would they keep moving things out of AOSP and into their proprietary frameworks?
Same for Linux itself - however in that case, there isn't incentive to make it proprietary, because the companies are either making money from hardware sales or from support contracts.
e.g. the first paragraph doesn't lose any important information trimming it down to:
"After adding a test matching the contents of router_routes.conf, `bundle exec rake` fails with:
ArgumentError:
invalid byte sequence in US-ASCIIRealistically, it would have been a better commit message if they'd given the shortlog SHA where the test was added that exposed the bug rather than an explanation of what the test does.
"After adding test <testname> (08c3e17), `bundle exec rake` fails with:"