Eskating cyclist, gamer and enjoyer of anime. Probably an artist. Also I code sometimes, pretty much just to mod titanfall 2 tho.

Introverted, yet I enjoy discussion to a fault.

  • 0 Posts
  • 408 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle
  • But there are no hacks required to install it on old hardware.

    Yes there are.

    If you used rufus or ventoy, you’ve just applied them without knowing.

    Unmodified Windows 11 ISOs will refuse to install on any hardware with a CPU older than Ryzen 3000 or Intel 8000.

    In fact there are less hacks required to install / upgrade to windows 11 then there are to install any Linux distro.

    What?

    On the vast majority of systems, the vast majority of linux distros will install and run with zero “hacks” of any kind. Literally just boot the ISO as-is and have at it.

    genuine copy of windows will receive all and any updates

    No. On many machines, while windows will install just fine due to the modifications to the installer applied by rufus/ventoy, the yearly major version updates can fail catastrophically.

    A lot of hardware will update without issue, but there ABSOLUTELY is risk.

    Windows is just an os. As long as it is compiled for the correct CPU architecture, it is just as supported as any other hardware. The hardware is supported by individual drivers, normally provided by the hardware manufacturer, not Microsoft.

    You are confusing functional, and supported.

    Something can “technically still work” without being officially supported.

    Not being supported means Microsoft can make breaking changes in updates, because they made no promises your hardware would be accounted for in the future.

    Just because it works today, no longer means it will tomorrow.





  • Heck yeah!

    I’m gonna make a couple celebratory posts on [email protected].

    Also, a tip on quickly getting up to speed with federation, is to get your instance and communities set up on lemmy-federate.com.

    Since content only shows up for users on instances with subscribers, the idea is to use a bot account on each participating instance to have that one required subscriber, so that posts from new communities actually show up on other instances, rather than just the originating one.

    It basically allows you to kick-start federation, actually allowing users to organically discover your instance and communities.

    edit: There is an active Balatro community at [email protected].



  • Yes. But you don’t have to switch.

    People say “start” with simpler distros because if you go past just using it as-is, and grow to understand linux closer to the system level, you’ll likely eventually end up preferring something more complex.

    There’s little point to starting at the deep end, like arch, since you don’t know whether you’ll end up staying in the shallows yet. Either way, it’s the start. It can also be the end, but that is unknowable.


  • Sorry, I must’ve misremembered about systemd. It’s how my installs start up, and the unit file is not in the usual location for systemd units I’ve created myself, so my assumption was it came with Kopia. There is no systemd timer though, and one isn’t needed.

    Edit: Just confirmed no systemd file came with kopia on my system either, my mistake.

    in the past week, it did not backup anything. Hence, there is no scheduler built into kopia automagically as described/ hinted in the docs.

    Was Kopia running during that time?

    If you run a Kopia command, then it will perform the instructed task, and then exit. It will obviously not do anything after completing whatever command was given, as the process will have exited, leaving no kopia process running on the system. This is for when you use it in cron or your own scripts.

    The other way of doing things is to run it in server mode kopia server start, which will set it running as a background daemon. When running, it allows you to log into the web interface or configure it via cli to do whatever you like. And as long as the process starts along with the host system, that’s all there is to it.

    How the daemon is set up to start, doesn’t really matter.



  • My current setup, is as follows:

    Personally curated music I buy and organize using Picard into folder A.

    Lidarr is configured with folder C, which is a mergerfs volume consisting of folder A and B. Folder A is read-only, and any writes on C go into folder B. This way Lidarr can “see” all my existing music, while any automated downloads go into folder B, keeping them separate from my organized files.

    Lidarr actually works, because it is hooked up to Soulseek using Tubifarry with ytdl as a fallback. I also have an import list hooked up to my last.fm recommendations to automatically download new stuff I might like.

    When I feel like it, I go through folder B using Picard, moving things I want to keep into folder A.

    To access my music, I use Jellyfin, also through folder C. My clients are Feishin and Symfonium.

    In Symfonium, I use smart playlists for discovery. These playlists populate based on stuff like “unlistened tracks” or “multiple plays without being favorited” and “recently added from favorited artists”.

    My favorite feature however is the tag-based endless playback which allows me to pick a track to start with, and then swipe through music with at least some kind of logic to the progression. This is my main way to browse my library.

    It works extremely well, with the exception of files that don’t contain many tags. Hence my main pursuit has been to find a good way too add at least some genre tags to ALL my files. I haven’t found a final solution.

    For iOS support, look at Navidrome for the server and maybe SubStreamer for the client.








  • The main advantages of Kopia, are speed and destination flexibility.

    The off-site storage does not need to have Kopia installed. It can be a mounted network location, an FTP server. Whatever. A generic cloud storage bucket like Backblaze B2.

    That’s why just a router with and external drive hooked up is able to suffice.

    For all of these, you can connect multiple Kopia instances to that same destination, and each client can browse backups, restore from them, and backup their own files to the destination. It even performs file deduplication across different source device. All while that destination device or service, has no access to your encrypted files.

    With borg, you need something like a Pi that can have borg installed. (You can also do this with Kopia, in which case the Kopia instance on the destination device is also able to manage the backups).

    Kopia also beats borg and restic in speed. My daily backups typically complete within a minute or two. I used to use Duplicati, with which it was common for it to take up to an hour. When it started regularly taking more than an hour, I switched to Kopia.

    Kopia is not the fastest for initial backup. The speed of this varies depending on destination type. It does not compress by default, but you can enable almost any type of compression you want. No, what it is fastest at is updating backups. If there is nothing to update, it does not take forever for it to figure that out. Kopia does it in seconds.