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/)ME
Posts
10
Comments
586
Joined
11 mo. ago

  • It's too late for me now coz I didnt do my research and ive already migrated over, but good god ever loving fuck was the AIO container the hardest of all my services to set up.

    Firstly, it throws a fit if you don't set up the filesystem specifically for php and the postgres db as if it were bare metal. Idk how or why every other container I use can deal with UID 568 but Nextcloud demands www-data and netdata users.

    When that's done, you realise it won't run background tasks because it expects cron to be set up. You have to set a cronjob that enters the container to run the cron, all to avoid the "recommended" approach of using a second nextcloud instance just to run background tasks.

    And finally, and maybe this is just a fault of TrueNAS' setup wizard but, I still had to enter the container shell to set up a bunch of basic settings like phone region. come on.

    Straight up worse than installing it bare metal

  • It's because this feature was implemented as a pseudo-keylogger on X11. All X clients could listen to the compositor state at all times (including input), even if input was focussed on another (potentially sensitive) application.

    In Wayland, clients have almost zero knowledge of the compositor's state. This was an explicit design choice to enhance security and enable modular features via wayland protocols. Of course, this also killed every implementation of app-specific global shortcuts.

    Wayland protocols take a lot of time to get agreed on - They need multiple implementations across different compositors (usually means KDE and GNOME need to implement the protocol spec and agree to it) and the specs can take a long time to design and reach production.

    Obviously this does hurt uptake for Wayland since issues can take years to resolve, but the core team are very aware of the pitfalls of X11's development and have long preferred this slow and methodical approach in the hopes it's sustainable and maintainable into the future.

  • Pro tip is to install a virtual machine like virtualbox or something on your Windows system. They're super easy to set up with loads of tutorials on youtube.

    From there you can install any number of linux distros (I recommend Mint or Pop!) and try them out without having to commit to real hardware. I would put the VM in fullscreen and pretend it was a real system, and use it as my dedicated machine for as long as possible. You can even install steam to get a feel of the setup process (bear in mind you'll need to set up stuff for graphics acceleration to play most games but the basic setup should be fine!)

    As for setup. Most Linux distros are as easy to set up as Windows or MacOS: USB in, boot, select a few basic options and stick to defaults. Reboot. Install stuff. You don't even need to deal with drivers (even Nvidia is cared for by most installers) which was nicer than burrowing through NV/AMD's websites to get their driver installers set up.

    At that point you won't be wondering if youve made the right choice when it comes to your next build, and you can get right down to actually using your PC instead of googling things. Good luck!

  • Is it that new? For the most part, the only people getting targeted with more than stern letters from their ISPs nowadays are members of cracking/release groups, or hosts of trackers themselves.

    Im sorta worried if they do get punished for it, because if anything that'll make the precedent to punish torrenters over the current precedent of targeting original uploaders.

  • The best part about COSMIC is that they've designed it from the ground up to be distro agnostic. Tbf you could install the COSMIC packages and plugins on any GNOME desktop but they were community repackaged iirc

  • I've kept a raspberry pi 4b that's given a mild OC to 1900Mhz in my boiler cupboard for a year and all its needed to keep it below 50 is:

    1. a tiny metal heatsink
    2. a 5w usb fan blowing already-warm air sorta towards it
  • I don't have much issue with email as a technology. It does what it needs to do, and does it well. The client side software is what hasn't budged in years - Search barely works, files and attachments are cumbersome, and spam is still rampant.

    It would be much cheaper and easier if users weren't centralised under a few big providers that prefer to bar any and all access to said users if you're self hosting, making it almost mandatory to use a private service.

  • EMA-AI-L protocol that turns your prompt into AI slop during transit, but contains a header with the original prompt so the recipient gets your actual message without bullshit attached.