Avatar by eveoart. Artwork - Artist

  • 1 Post
  • 60 Comments
Joined 3 years ago
cake
Cake day: June 9th, 2023

help-circle
  • Darn. I had the same question as OP but have been working around it by combining everything into the same stack. It’s just a bit of a pain to edit the stack every time I want to test something or retire a service.

    Good work-arounds though! Maybe I should move to a script-based startup… Only trouble is all my containers are tagged with restart: unless-stopped so Docker restarts all of it at once on reboot which would mess up the order. Hmm.


  • My friend had bad luck with GoHardDrives. I bought 6 HGST 12TB drives from a different seller a couple of years ago and it’s been pretty decent. I had 1 fail within the year and got a refund with no effort. A second failed shortly after, outside of warranty. Accounting for the 1 I paid to replace I still came in below cost of new. Plus I now have a very healthy mix of power on hours and models with RAIDZ2 which I feel good about.






  • This survey definitely looks vibe-coded as heck lol but I hope the results will be good.

    My results :)

    Data Hoarder 💾

    • Fleet: 2–3 devices · More than 50 TB
    • Motivation: Privacy & data ownership, Independence from Big Tech & subscriptions, Customization & full control
    • My MVPs: Immich, Baikal, Forgejo, qBitTorrent, Home Assistant

    God knows I wasn’t going to put cost as a motivation… I am actively losing money running double the storage I am using and 100+ GB of RAM on a Xeon chip, but having the headroom is certainly nice and has allowed me to expand as much as I want. Getting a good deal a couple of years back before the price explosion was a huge stroke of luck. If this server ever failed I could figure out a smaller operation with more confidence.


  • A lot of it is doing what other people tell you to do. This may be encouraging or not, but I consider myself fairly versed in tech and there is still troubleshooting where it feels like trying things at random rather than any skilled insight to a solution. The take-away is it’s okay to skip an app that has terrible documentation and you can’t figure out. Start with something that has good tutorials and if that doesn’t work, try something else. If you can get that up and running those skills will carry over.




  • The first and most obvious is that (last I checked on Lemmy) per-user instance blocks only block posts, not comments. This means that for truly spammy instances (cough Hexbear cough) it requires an instance-wide block to achieve.

    Secondly, I would argue it is the same as any other reason to choose an instance. That being, I have to generally like the vibe and agree with the way it’s run. For example, I have to agree with the instance rules and trust the admins to moderate them. This is an extension of that.

    In the case of lemmy.ca specifically, I would say every major defederation I know of has been cast to a community vote and has had solid reasoning behind it. It comes back to trust and matching opinions: I (currently) trust the admin team to have reasonable defederations as they have matched or been similar to my opinions in the past.

    I enjoy not having to self-moderate my experience outside of individual users or rare cases. Choosing an instance that generally aligns with your views allows your admin team to do some moderation for you.



  • The best thing I did was probably set up Obsidian Live Sync after hearing about it in selfh.st weekly. Compared to the Syncthing setup I had before it is so much quicker, much easier to catch sync errors, and won’t drain my damn phone battery as much! The more things I can move away from Syncthing the better so I will probably be looking at Immich for my photos soon as well.

    On the management side, I’ve had my Docker stacks split across Dockhand and Komodo ever since a poorly executed move away from Dockge a few months ago. I finally thought about it and had the time to decide to give up on them both. I like some of the concepts of compose in a git repo and the fancier interfaces, but I just realised it was all over the top for what I need. I missed being able to simply SSH into a damn machine and docker compose up -d in an emergency. Compared to the constant deploy errors of Dockhand and the potential of scrounging application databases for in-DB compose data or attempting to deploy stacks from forgejo when forgejo itself is a stack deployed via git… going back to basic files is a blessing. Lesson learned!

    What that culminated in is all my stacks are now in Sencho (which clearly uses a lot of AI code sadly), but it was that or Dockge and I knew Dockge lacked a few things I wanted. The nice thing about Sencho (and Dockge) is that I don’t need either of them because they are based around file-on-disk simple operation. I can cut it out of my setup entirely at any moment and not shed a tear. So much peace of mind leaving Dockhand. Now I just need to find a builder image or write a script to replace Komodo’s build feature because I don’t want to keep using it.



  • Yeah there’s a fair bit outside of home people don’t mention. Basically any system-level stuff: fstab mounts, all your system packages, /opt installs, config tweaks you had to do. It tales some time to get set back up after a while on the same install.

    After having to reinstall a couple times myself I now don’t touch anything outside of /home by hand. It’s all scripted so that I can copy /home, run the script, and be back up and running. Well, theoretically, there’s usually a hiccup or two. But the peace of mind knowing it’s all (self) documenting is quite nice. Not for everybody of course.






  • Nah, having a useful tool built in is a good user experience, provided you can remove it. Windows fails on the second part. But I think OS’s should aim to have simple tasks covered by default apps such as Paint on Windows or Libre Office on most Linux distros, and an anti virus is probably a necessary install for many Windows users.