Avatar by eveoart. Artwork - Artist

  • 5 Posts
  • 257 Comments
Joined 2 years ago
cake
Cake day: June 9th, 2023

help-circle

  • if I write a loophole in your employer’s code, like a patch, that keeps them from having to pay you, and they like not having to pay you, I haven’t done anything egregious or unethical?

    I don’t really care about the ethics in the Revanced situation nor the greater adblocking scene. That’s a moral question for individuals to answer. From a legal perspective, I don’t agree with the removal of original code. While I don’t know of a legal precedent for the digital age, the closest physical comparison I can make is to the distribution of a lock-pick or a gun. And we don’t prosecute lock-pick manufacturers for selling to a thief, we prosecute the thief for breaking into someone’s home with it. Exempting cases where the actual product is illegal, such as specific gun models, but as far as I am aware there is no such law against any software (yet). Even if there were, I doubt it would all under the perview of DMCA. Thus my reasoning for saying this is an abuse of DMCA and my reason for distaste towards the situation.

    Bringing this back to your original comment:

    I wouldn’t expect Spotify to just let people use premium services for free. Fuck Spotify, right there with y’all on that, but this isn’t egregious or unethical behavior for them.

    I wouldn’t expect them to either! But I also don’t expect them to try and take down material they have no right to take down and I would consider that to be a bit ‘egregious’.

    Edit: You know, I should have actually done the research before commenting. Anyway, I looked further into DMCA intent and it covers some circumvention tools which may(?) apply to adblockers, although I haven’t heard of that being tested in court before. Leaving my comment here since it’s already federated anyway.







  • I have two identical HDDs as a mirror, another one that has no failsafe (but it’s fine, because the data it contains is non-critical)

    On separate pools, I hope? My understanding of ZFS is that the loss of any vdev will mean the loss of the pool, so your striped vdev should be in its own pool that you don’t mind losing.



  • I have been using TrueNAS Scale for a while but have not used base Linux for my NAS. My opinion is if you’re looking for a quick initial setup or are like me and didn’t want to install ZFS yourself, TrueNAS is rather appealing, but otherwise it doesn’t offer much. It has ZFS pre-installed, gives you a webUI to monitor basic things about your machine, and has fairly easy ways to setup data protection with snapshots and backups with rsync or zfs replication. In the more recent versions it even has Docker apps built-in so you can host some basic things. The downside of TrueNAS is that despite being Linux under the hood, it’s a lot more locked down so doing advanced measures is more of a pain and much of their “simpler” UI-based stuff is exceedingly basic, half-featured, and lacks documentation.

    The way I use TrueNAS right now is to treat the main OS as mainly untouchable. I don’t try to break out of the limits placed upon it. I instead use a “Jailmaker” machine (defunct wrapper script for systemd-nspawn) for all my Docker needs. This way the main system remains more stable. If I have to re-install, then it’s a simple config import and my NAS is back to how it was.

    I would use the built-in VM tools or the built-in Docker tools for this, but A. they weren’t implemented or weren’t working when I set this up, and B. I found their setup rather… annoying. For instance, I tried to set up some apps with their previous app system and it required configuration before working and yet nowhere did anyone explain how to configure it so I was wokring blind. No one makes guides for setting up an app in the TrueNAS UI, so the extra layer of obfuscation was just a hinderance to me. Compare that to setting it up directly in Docker, there are a million guides and great documentation for everything I get stuck on. Thus, despite being the “harder” way to set it up, it was easier due to the existence of information about it.

    So, looking at it objectively, what parts of TrueNAS do I even use compared to base Linux? Not much. I use the WebUI to accomplish basic tasks such as creating or modifying datasets and permissions, snapshots, SMB shares, etcetera. All the basic things are there and I use the UI for them. But ever since that initial setup I spend most of my time in the CLI adjusting my scripts and Docker config files, creating directories inside the datasets, fine-tuning permissions… I could definitely have gone for a base Linux install as long as I knew what to install for ZFS support, some manner of WebUI, and so on. TrueNAS just did all that initial setup for me, and having a more locked-down OS forced me to use safer methods of installing programs via containers and keeping my install a lot more portable which I plan to continue no matter what OS I use.

    This was probably not helpful, but that’s been my experience of TrueNAS for what it’s worth. Whatever you do, just remember: RAID is not a backup. It is protection against drive faults, but an error in the RAID system itself or the RAID pool’s data requires a separate copy of the data stored elsewhere to restore.









  • on most of my systems I get tired of constantly lsing after a cd so I combine them:

    cd(){
        cd $1 && ls
    }
    

    (excuse if this doesn’t work, I am writing this from memory)

    I also wrote a function to access docker commands quicker on my Truenas system. If passed nothing, it enters the docker jailmaker system, else it passes the command to docker running inside the system.

    docker () {
            if [[ "$1" == "" ]]; then
                    jlmkr shell docker
                    return
            else
                    sudo systemd-run --pipe --machine docker docker "$@"
                    return
            fi
    }
    

    I have a few similar shortcuts for programs inside jailmaker and long directories that I got sick of typing out.



  • Media watch status no longer persists on media rename. When you move or rename your media files, previously Jellyfin remembered the watch status based on external IDs alone; now it uses an actual reference to the database entry. This is a transitional change and we are working on a better way to handle that in a future version.

    I hope they do figure out a solution for that soon… Until that’s fixed I’m going to stay on 10.10.7 for a while.