I have no clue what’s meant by “without download”, but this app just uses web assembly to inspect the archive in the browser. The sandbox they talk about most likely refers to the browser sandboxing.
So it pretty much boils down to “risking running malicious code is fine, because this app as a whole is treated as malicious by the browser”.
Idk, ~five years doesn’t seem like a long time with regards to CPUs. I had my Ryzen 2200G from summer 2018 to this January, and I would consider my purchase of a cheap Ryzen 3600 to be a bit premature (and it was definitely an impulse purchase). And it also means that the CPU sticker became outdated pretty soon.
Yeah, it’s not uncommon to do that, it’s just that I’d expect better from a tech website.
It’s an AMD GPU, so how does it have anything to do with RTX, which is a marketing name for a bundle of Nvidia technologies including the CUDA compute framework, an AI framework, and of course a ray tracing API (which games generally don’t touch, because that would limit their ray tracing implementation only to Nvidia GPUs)?
It was removed in Android 12
The author acknowledges that, the blog post seems to be aimed at demystifying the concept of namespaces by showing that a “container runtime” that only does limited filesystem namespaces (using chroot) is enough to get some widely used containers running (of course without all the nice features and possibilities of the other types of namespaces)
saying that my legitimate copy of Windows 11 was at end of service
The screenshot says the version you use reached EoS and you need to update. There’s absolutely nothing about invalid licenses in the screenshot.
Good job for getting upvotes on a “haha winblows bad” troll post, I guess.
However, for most people, the 5-a-day limit might actually provide a better framework for taking high-quality images. This limit makes you think more about your shots, so it could be useful to improve. your composition, timing, and framing.
See, it’s pro-consumer. Lol
OK, so the current dev implementation seems to make accessing notifications one-handed nearly impossible? You need to reach somewhere to the left half of the upper edge to pull them down - the top right corner is already far enough from my thumb most of the time to be a bit inconvenient to pull down on.
And I hope they bring back some quick toggles to the notification screen, it would be awful to have to go to the full quick settings menu just to turn on the flashlight, lol.
If you keep your Pixel plugged in for a few days, it will give you an option to limit charging to 80% (or maybe just turns it on on its own, not sure about that). There’s no other way to activate it currently, but that should change soon (the Adaptive Charging option will have three options instead of just on/off).
deleted by creator
As far as I was aware AMDGPU is used by default on most if not all distros
I really don’t think that’s the case, assuming you’re talking about AMDVLK (amdgpu is the kernel module used by all three Vulkan drivers - RADV, AMDVLK and the Vulkan driver from AMDGPU-PRO). Ubuntu and Fedora definitely default to RADV, and Arch Wiki recommends RADV unless you need something from the other drivers.
I noticed a performance increase after forcing RADV on NixOS so not really sure.
NixOS seems to default to RADV according to their Wiki. If this was a few years ago then maybe you might be confusing it with the ACO shader compiler for RADV? That brought a significant performance increase and eventually became the default in RADV. I remember using custom Mesa (the project that develops open source graphics drivers, like RADV and radeonsi) builds to massively reduce stuttering in DirectX games.
I personally chose RADV after looking into this myself and the only drawback from my understanding is that they are proprietary drivers.
RADV is the open-source community developed Vulkan driver. It has the widest hardware support of the three Vulkan drivers and is generally the best for gaming.
AMD provides two more Vulkan drivers - AMDVLK is the open-source one available in AMDGPU, then there’s the unnamed proprietary Vulkan driver in AMDGPU-PRO. The biggest advantage of the proprietary one is that it is certified - doesn’t matter most of the time, but when it does, a missing certification is a deal breaker.
Pixels never had the SD card slot
Since the phones have water resistance, they are technically designed to work under water
Oh, so a device that offers no warranty in case of water damage (because you’re not supposed to expose it to water) can use an IP certification as a loophole to completely avoid this law? That’s not good
As @Treeniks@lemmy.ml pointed out, the author considers something as small as spawning a separate process for each window to mean a “non-native experience” (wait till they see how web browsers work)
It’s likely the same sensor that is included in
the rest ofthe Pixel 9 Pro Fold.
I see proofreading the first paragraph is too hard these days.
Don’t know about the rest, but…
Does reflashing a ROM fix it?
The phones appear to be simply dead with no response to anything. No way to connect ADB, no way to connect fastboot, nothing.
Also the bootloader allows flashing over the cable only when it’s unlocked (at least on Pixels; I couldn’t find anything relevant in the Android documentation). The vast majority of Pixels should have their bootloaders locked, and it is only possible to unlock it through the system settings, so it’s pretty safe to say that most Pixels cannot be recovered if Android fails to boot because you cannot unlock the bootloader if you can’t get into settings.
Licensing the source as GPL doesn’t really force the copyright holder (which is 100% BitWarden due to their Contributors Agreement^*, no matter who contributed the code) to do anything - they are absolutely free to release binaries built on the same codebase as proprietary software without any mention of the GPL.
For example if I write a hello world terminal program, release its source code under GPLv3 and then build it and give the built binary to you (and a permission to use it), you cannot force me to give you the source code for that build because I never gave you a GPL licensed binary.
If you were to take my GPLv3 source code and distribute a build of it however, you would have to license your binaries under GPLv3, because that’s the terms of the license I provided the source code to you under. Your users would then have the right to request the source code of those binaries from you. And if you released the build under an incompatible license, I (but not the users) could sue you for violating my license.
Their previous versions, still being under the GPL, would require them to release a change to make it usable on desktops.
License violations are usually not resolved by making the violator comply retroactively, just going forward. And it’s the copyright holder (so BitWarden themselves) who needs to force the violator to comply.
^* this is the relevant part of the CA:
By submitting a Contribution, you assign to Bitwarden all right, title, and interest in any copyright in the Contribution and you waive any rights, including any moral rights or database rights, that may affect our ownership of the copyright in the Contribution.
It is followed by a workaround license for parts of the world where copyright cannot be given up.
On the 8 series and up. Apparently the Tensor and Tensor G2 are too weak to handle this feature or something /s