• 0 Posts
  • 24 Comments
Joined 14 days ago
cake
Cake day: October 3rd, 2026

help-circle
  • For home Wi-Fi I use a strong password, but that’s because it’s something I input once in a blue moon. For guests I have a guest Wi-Fi with a simpler* (still reasonably secure and random, but shorter and without special characters) password and a QR code for simple use, though they are rate limited and have no access to any other network clients.


  • If we take the EFF wordlist commonly used to generate passphrases, we have 7776 words. If we take ASCII alphanumerics and special characters we have about 92. Assuming we generate a NIST compliant password of 15 characters in length we get 92^15=2.8*10^29 of combinations. To get the same level of security (same number of combinations) using the EFF wordlist we need (log(2.8)+29)/log(7776)=29.45/3.9=7.6 around 8 words. If we assume the words are 7 characters long on average, plus the separators, we get 7*8+6=62 characters long. If we start to also include Unicode characters like other scripts or emojis (something I’ve recommended to others) the required number of words grows even more. I don’t know about you, but I can’t be bothered to type that all out every time, a password manager works for me.











  • Yes, though slight caveats: Mint has 2 branches, 1 based on Ubuntu, as you said, but the other one based on Debian skipping Ubuntu actually, since there are a lot of things they are dissatisfied with Ubuntu, and one among them are snaps, so if you see anything regarding snaps when searching Ubuntu threads, disregard them completely.







  • From what I’ve seen, there are 4 core issues people complain with snaps:

    1. For full functionality, snap requires Ubuntu specific kernel patches, and has a hard dependence on Systemd, whereas Flatpaks work everywhere.
    2. Most Flatpak users default to the flarhub repo, however, just like you can have other apt sources, Flatpak supports other repos. Snaps on the other hand are exclusively tied to and controlled by Canonical, which seems very unlike Unix and rubs many wrong.
    3. You can install packages as a non-root user into your home with Flatpaks, but snaps can only be managed by root, since they are system packages. This means that they are very unsuitable for atomic distros like Fedora Silverblue.
    4. Technically not the fault of snaps but the decision by Canonical, when you try to install something with apt on Ubuntu (and derived) it may instead install it through snap, which, because of sandboxing and other security measures, may result in very unexpected and hard to diagnose issues. I personally wasted a day trying to fix a broken Docker daemon, which turned out to be due to snap, when I explicitly wanted an apt! I personally have no major issues with snaps in general, but ffs let me decide whether it’s a snap or not >_<

    Bonus: Some also complain about security, that snaps have had many vulnerabilities, and that malware was distributed as snaps, but the same has been true for Flatpaks too, so I don’t think it’s fair to point that out.



  • The laptop BIOS did see updates and now works fine running Cachy, but for over a year it was terible. A whole list of cryptic kerner boot arguments would make it boot, but then touchpad and keyboard issues would remain, and if it ever went to sleep it would hard lock again, not ideal on a laptop. I personally didn’t contact support, but on the official forum there was a thread with a tonne of comments about how support would say Linux is not officially supported on this model and people giving up and returning it. I couldn’t because I ordered from overseas, specifically because I heard Thinkpads worked great with Linux. Needless to say I was royally disappointed. At least it works now, and works better than with Windows.