snowfalldreamland

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.

from https://blog.anytype.io/our-open-philosophy/

Well you don't get long COVID from the flu so it's not like the flu at all.

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.

But here it's deleting /* and not / so I think it won't prompt you for that flag, but I'm not about to try 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 S22 charges at a maximum of 45W. That's technically within the 60W limit that all USB-C cable can handle. I could not find how exactly how the charging works but it's possible that they are doing something like 9V @ 5A and thus are requiring a 240W or 100W cable. However it looks like in this particular case it might not matter.

https://arstechnica.com/gadgets/2022/02/the-galaxy-s22s-45-w-charging-doesnt-actually-improve-charge-times/

GSMArena says the Galaxy S22+ charged to full in 62 minutes on the 25 W charger and 61 minutes on the 45 W charger. The Ultra took 59 minutes on the 45 W charger and 64 minutes on the 25 W charger.

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