Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)K
Posts
9
Comments
221
Joined
2 mo. ago

  • I think Mora is on the ball but we'd need their questions answered to know.

    One possibility is that you have SELinux enabled. Check by sudo getenforce. The podman manpage explains a bit about labels and shares for mounts. Read up on :z and :Z and see if appending either to the volumes in your compose file unlocks it.

    If running rootless, your host user also obviously needs be able to access it.

  • You don't interact much with lawyers and government in your work, I take it?

  • Auhorities in other European countries are known to MitM SSL certs at VPS providers for years already. Switzerland is moving their legislation towards the EU direction. Proton themselves have been vocal about their concerns about this.

    How long until someone realizes they can demand Proton to inject some extra JS into the webmail for desired targets? Folks in a sensitive situation should follow the established best-practice of not relying on remotely served JS for client-side encryption. To be safe against this vecor, handle your encryption and signing outside of the webmail; either in your own client or copy/pasting.

  • What would your father say? Real fathers use real startx.

  • slock

  • Revolut's deposit instructions say to transfer USDC to it, you have to use a network called Polygon. In his first, successful, deposit Tzoni selected one called "Polygon PoS".

    In the second deposit, when he tried to transfer 1,500 USDC, he selected a different network - "Polygon (bridged)".

    He thought it would work just as well but says instead it caused the coins to be converted into USDC.e - a different cryptocurrency.

    This is what Revolut received. The company does not handle USDC.e coins.

    The article does not mention which wallet app or service Raykov transferred from. This is the more important factor I think. Whatever those USDC.e coins are, it sounds like the wallet "helpfully" traded the original tokens for different ones on another chain on his behalf and then sent those. While Revolut's crypto offering is garbage and Revolut is a shady black company in general, it sounds like if anything the blame might be on the UX of his sending wallet being misleading and confusing.

  • I really hope the X11 session stays maintained.

    Otherwise, KDE will finally have a reason to get get its MATE/Cinnamon equivalent

    What should the fork be called? Surely someone can do better than "Plaxma DE".

  • Amazon has their own Linux dist that is relatively popular among their customers

    https://aws.amazon.com/amazon-linux-2/

    As for your question, consider thus: I think many users here have the resources to make their own personal Linux distributions without drawing from an existing base distro. Yet very few do. Why do you think that is? There's a lot of overlap in the answers.

  • In one way I think so, yes.

    Many people obviously offload trust to the community to some extent, (probably much more than we should, reflected in popularity of helpers like the one you asked for), which involves the AUR discussions and votes, and the Arch wiki.

    Sometimes a flatpak or container image, or straight up compiling from instructions, is the easier answer.

    Have fun and be careful but curious out there! How obscure AUR packages you will be able deal with safely depends on your level of ambition.

  • Supposedly both the display manager and greeters have system-wide configuration for this purpose, however. And the issue with notifications and DE overlays are present post login, too.

  • Read https://wiki.archlinux.org/title/Arch_User_Repository

    "Installing from the AUR" usually means:

    • Cloning the AUR repo
    • Installing build dependencies
      • If any of those are AUR packages, recursively repeat

    • Download source files from arbitrary online location
    • Run arbitrary commands to build
    • Pack it all into a tarball
    • pacman -U the tarball

    Anyone can easily register and upload AUR packages in seconds or minutes.

    This makes it a high-risk vector for malware and there is indeed malware uploaded to the AUR all the time. Looking at the NPM malware development, the increased popularity of Linux, and the already ongoing cyberattacks on AUR itself, this will only get worse.

    The idea is that you are expected to manually inspect and vet the PKGBUILD yourself by doing these steps before you run makepkg itself. With great power comes great responsibility. Developers realize that it is not responsible to make a tool specifically designed to make dangerous behavior and explicitly bypassing safeguards, stopgaps and best-practice protocols more convenient than the alternative, when it will be targeted to uneducated users.

    As wltr mentioned, there are helpers, but you really should pick one that involves that manual inspection (like aurutils), and after becoming comfortable enough with git+makepkg+pacman to make it routine.

    TLDR: If you can't or won't vet PKGBUILDs of AUR packages you shouldn't be blindly installing them.

  • Did you look this up?

    What do you think is more likely - that KDE Neon does not have a testing version of Plasma Login Manager or that a sensationalistic news headline is not giving you a 100% accurate and complete understanding?

  • Things I've run into:

    1. Out of the box, the lock screen comes on after screen unblanking - late enough that when things aren't snappy you can briefly catch the desktop without reauthing.

    2. Sometimes randomly after wake, keyboard input is not recognized in the password field at all. Except for Esc, which in this state appears to crash-restart it and makes it work again

    3. With a multi-monitor setup, I have still not been able to properly force the primary monitor. Is an issue because things like notifications and the login input will only show up on a usually turned off projector. This one might be PEBCAK.

    I have issues 1 and 3 with XFCE on lightdm, too, though.

  • Are you able to try it with other SATA drive models?

    Are there any relevant BIOS Settings like "legacy USB" that could make a difference? Do you have the latest firmware for the motherboard?