That is very very explicitly just the name of technical the specification. Its a documents for people who design usb devices. The tech media failed us by reporting on it like they did.
The spec also explicitly tells us that we should refer to the usb cables/ports/devices as e.g. “USB4 40Gib” or “USB 3 20GiB”. So in fact we have easy to understand names but only a few manufacturers actually print that on the boxes or cables.
How do you do inter-pod communication witg quadlet? I never figured that out with podman kube play and just moved back to staring conatiners and creating networks from a shell script
I think ecc isn’t more required for zfs then for any other file system. But the idea that many people have is that if somebody goes through the trouble of using raid and using zfs then the data must be important and so ecc makes sense.
I love the idea of distrobox/toolbx!
but ive never understood why they by default share the home directory. They still overwrite each others config filesand leave a huge mess in the home dir. And last time i tried it wasn’t possible to really isolate things. Has thisimprovesd?
I’ve been a paying bitwarden customer for years but i through they were moving more towards free software and not away from it… Makes me consider quitting my subscription. Why do they do this?
Ah i see kde has fixed the issue where dropdowns had broken behavior when scrolling https://invent.kde.org/frameworks/kirigami/-/commit/f6ca218607ff7e5d5066eb3224154c3256cb9516 this was my main blocker why i couldn’t use it when i tried it around 2020. Maybe i could give it another try?
Actually the naming scheme you propose e.g. USB4 80Gb is the real naming scheme! It’s officially what the specification demands manufacturers label their products. “USB4 version 2” and so on are explicitly only the names of the internal standards that only concern people writing drivers or designing chips.
I have no idea what tech journalist are smoking. This has been a problems for so many years but they keep using the internal names. I mean nobody is complaining about having to always say “IEEE 802.11bn” instead of WI-FI 8
Reimplements in C
Segmentation fault (core dumped)
change code so it no longer segfaults
still is UB, has arbitrary code execution vulnerability
everybody dies
What non standard thing are they doing with the power supply? The PSU looks like a regular usb c PD supply to me (even supports 12v, nice!)
Edit: wtf! 5v@5a yeah thats non standard. What were they thinking?
The system tray is the one thing i need to see that/if email/steam/chat is running and if there’s new messages. Otherwise gnome works great for me
There are portals: https://docs.flatpak.org/en/latest/desktop-integration.html#portals . they allow secure access to many features. Also any flatpak app still has access to a private app-specific filesystem, just not to the host.
Doesn’t work for all applications but for many sand boxing is possible without a loss of features.
Edit: the meme says “closed source” which is patently false for Mongo
No, MongoDB is closed source, proprietary software. You might be confusing open source with source available.
Edit: Actually I am wrong sorry. Closed source is not the opposite of open source. I didn’t read your comment exactly enough. MongoDB is not open source, it’s not free software, it is source available and thus not closed source. The things below are still true but don’t contradict what you said.
The SSPL is not a free software license and it is not an open source license. The OSI said so:
https://blog.opensource.org/the-sspl-is-not-an-open-source-license/
only option for messaging between Android and iOS.
Well aside from like all the messaging apps, right?
It might sound surprising but it makes a lot of sense to have different standards supported over USB-C. USB-C is just a form factor of the connector.
For USB 3 or USB4 speeds you physically need more wires in the cable, while for USB 2.0 you only need 5 wires. Also if you want really high data transfer rates of 40 or 80Gbit/s the cable can only be around 1 meter or 3 feet long.
So because USB-C supports different USB versions, a charging cable can simply be USB 2.0 and be cheaper and long and do it’s job just fine.
If USB-C was only USB4 it wouldn’t be all that useful. Devices like wireless mice or DACs or game controllers wouldn’t/ couldn’t use it and the cables would all be thick and expensive and short. And for charging regular things we’d still be stuck with micro USB.
The only downside is that, yes if you are doing a thing where you need high speeds such as connecting a screen or external disk to a PC you do need to check that you’re using a high speed cable, but pretty much all good quality fast cables have the speed printed onto the connector housing.
But yes the iPhone restricting speeds to 2.0 is strange and most definitely just a trick to sell more pro models. There are plenty of devices that simply have no need for anything besides 2.0, be it because they send no data or just very little. But phones really aren’t in that category.
I get screen tearing when gaming on x11 so i use wayland and I only switch to x11 if i need to screenshare on discord.
yes these are the terms that are not supposed to be used in product naming or by consumers and are just intended for use by people developing USB devices.
Well you have to differentiate somehow and USB 5, 10, 20, 40 or 80 gbps sound like reasonable terms for normal people.
Yes it was never intended that any consumer hears about something like “USB 3.2 Gen 2” that was strictly internal naming for people developing USB devices.
In fact the naming guidelines we’re simplified even further than in the older version you linked: https://cdn.arstechnica.net/wp-content/uploads/2022/09/USB-IF-language-usage-guideliens.pdf
But yea borderline fraudulent manufacturers and uninformed tech journalists are to blame for all this confusion
The v2 part here really just refers to the fact that it’s version 2 of the specification. Consumerrs only need to know the term USB4 and the speed that their device operates at. It’s sort of like complaining that the ietf has terrible naming schemes because HTTP is defined in half a dozen RFCs with 4 digit numbers. This versioning is just meant for people developing USB things.
Actually this article here is one of the few times where even mentioning the version 2 part is reasonable since the details of these specifications actually matter to kernel developerrs. For everybody else it’s just USB4 80 gbps.
That’s a really good idea! So good in fact that that is actually what they did call it! https://www.usb.org/document-library/usb4r-specification-v20