

Fixed, thanks
Fixed, thanks
Their statement is that Alpine is designed such that it is friendlier to corporations who want to lock down their devices and prevent you from modifying them.
You cannot use coreutils and have a DRM locked down device.
You can use Alpine w/ musl + busybox and make a DRM locked down device
Alpine’s licensing favors large corporation’s rights in preventing the user from modifying their device
Operating systems using coreutils favor the end user’s rights
If they can take my unlocked device by force, they can probably also break my fingers to coerce me to unlock it See also: https://xkcd.com/538/
Randall is right in pointing out you need to consider your attack vectors, but this doesn’t mean you shouldn’t take reasonable precautions
Most people are more likely to run into the type of attack OP references than someone who can break LUKS encryption stealing their device
My naive reading is the difference here is HP slapped a discount sticker on it without changing the price.
Where Kohls, et. al. set the price extremely high and then always have it “on sale.”
Now, how companies get away with doing the same thing for Black Friday, no idea
I wasn’t confident which requirement you were missing, but I love that error
The default in systemd, unless your distribution has modified it either globally, or for a specific service, is 90 seconds
Wasn’t France the one that started switching to Matrix and funded a bunch of improvements?
It’s great that Germany is doing the same, I just remember Matrix talking about money from France and helping the French government deploy Matrix for government use back in the day. A lot of the E2E encryption improvements were attributed to their collaboration with France at the time
That one’s especially egregious because the Direct Rendering Manager handles displaying things to the screen, where you might have Digital Rights Management involvement in the form of HDCP support, etc.
deleted by creator
That’s already how it functionally worked for each major release
Here’s their previous strategy: https://web.archive.org/web/20220917195332/source.android.com/docs/setup/about/codelines
Google works internally on the next version of the Android platform and framework according to the product’s needs and goals
When the n+1th version is ready, it’s published to the public source tree
The source management strategy above includes a codeline that Google keeps private to focus attention on the current public version of Android.
We recognize that many contributors disagree with this approach and we respect their points of view. However, this is the approach we feel is best and the one we’ve chosen to implement for Android.
As far as I can tell, this would really only affect QPRs, since the public experimental branches that get made after they throw the next release over the wall is going away
There’s no chance in hell Vance knows what that phrase means
Oracle happened to it
All the devs went to LibreOffice after that
I wasn’t trying to give a positive side, I was just explaining why Microsoft wants the feature
If the executable binary has to be signed with a key, similar to the module signing key, Microsoft could sign their binaries
This, along with secureboot, would prevent the owner of the machine from running eBPF programs Microsoft doesn’t want you to run, even with root
I agree, but the wording of that is imprecise…
Google reimplemented the same API (which should be legal) but “use” sounds like they called Oracle’s implementation of the function
Oracle tried to argue that writing your own virtual machine with the exact same same interface as theirs (even a clean room reimplementatio, or an improved version) was copyright infringement
If Oracle had won, it would likely have killed things like OpenJDK, WINE, Proton, Rosetta, etc. and would have made licensing around OpenGL/Vulkan very confusing (for a few examples)
Kind of seems like they simply installed this dude’s tarpit from a few months ago
Where did Microsoft put an official announcement saying the statement from an official Microsoft employee, Jerry Nixon, speaking at an official Microsoft conference, Ignite, was incorrect?
Edit:
When reached for comment, [Microsoft] didn’t dismiss them at all
Recent comments at Ignite about Windows 10 are reflective of the way Windows will be delivered
https://www.theverge.com/2015/5/7/8568473/windows-10-last-version-of-windows
Yes, in the sense that every device you own has these same commands
The alarmist of the original was that this was somehow unique to the esp32
If your device has Bluetooth, it has these commands
They already have one: https://en.m.wikipedia.org/wiki/Budapest_Memorandum
Offering another empty promise is unlikely to cause them to make concessions again