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?
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?
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.
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.
Get a cross body sling, One of those travel digital nomad things. The brand ones aren’t cheap but it’s like somewhat fashionable. Maybe that could work?
Anytype looks interesting but it looks like most of it is non-free non-opensource software:
While our core solutions, the infrastructure protocol any-sync, and the data protocol any-block, are released as open source under the permissive MIT license, we distribute the remaining layers, including the middleware library any-heart, and applications like anytype-js, anytype-swift, and anytype-kotlin, under the Any Source Available License. This license grants individuals the freedom to review, modify, and utilize the code for personal, academic, scientific, research, and development purposes. However, for commercial use, consent from the Any Association is required.
Sorry to ask but why is get/set facl not sufficient for acls on linux?
They had some serious cryptography issues (including no perfect forwards secrecy!!!) but they have promised to fix that. I’ve not yet seen any paper analyzing the new protocol. But maybe it could be good?
Edit: Here’s a paper with some of the issues: https://www.research-collection.ethz.ch/bitstream/handle/20.500.11850/623004/main.pdf
They conclude that:
The seven attacks we have presented highlight fundamental weaknesses in the design of Threema. Indeed, the Threema protocols lack basic properties that are nowadays considered de rigueur for a messenger app to be regarded as secure: forward secrecy with respect to a malicious server, and protection against replay, reflection, and reordering attacks. We believe that the cryptography in Threema has design flaws that need to be addressed in order to meet the security expectations of its users
They have redesigned their protocol since then but again i have yet to see a third party look at it but TBH i haven’t looked into it.
Well if they are in the repos i assume it be less likely to have incompatibilites when updates happen?
It’s just sorta strange to be because everything from fedora, ubuntu to arch and even windows just works in virt-manager without any special settings and openSUSE just doesn’t even get to the installer.
The problem with openSUSE Tumbleweed I have is that so far I’ve never been able to install it. For all other Linux distros I can just get the ISO and use virt-manager to create a VM. But openSUSE never manages to boot. Any ideas why? I’d love to try it.
Edit: I’m trying it again now and i made it into the installer now
Edit2: installed it and am trying it out. Looks good on first glance but some packages that i’d really need to use it as a daily driver appear not to be present, like gnome-shell-extension-appindicator or gnome-shell-extension-caffeine
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