Need is a strong word lol. I definitely don’t need as much as I’ve got as I only use 20-50GB on services (Docker and TrueNAS) with the rest being used as ZFS cache. I would not have bought this much normally but I got it as a package in a PC with an RTX 3080, Xeon Gold 6150, and the RAM for $1000 CAD (750 USD ish?). No way was I passing that up.
This survey definitely looks vibe-coded as heck lol but I hope the results will be good.
My results :)
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.
Giving away? As in free? Luckyyy
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.
While suggestions like these are good, I don’t feel that we’ll ever have full account portability on ActivityPub. By nature of the applications, the only way to keep your data and your account under your own control is to run your own instance. This is something AT Proto got much better (on paper) with their separate identity servers. Being able to host your own data without the bloat of running an entire (for e.g) Lemmy instance is huge.
My dynamic IP rarely changes. When it does, it gets updated by a Docker favonia/cloudflare-ddns image. I have yet to notice downtime.
I would love to see alternatives/replacements to them that are less opinionated. If you aren’t ready to consign your entire library to destructive edits and file replacements then it really is hard to fit any arr program into your workflow. Because I have a few files I want to keep pristine and a few opinions on what gets downloaded, I’ve hit a snag every time I try to set up any arr program. Lidarr, for example, simply refuses to allow a root dir to be read only. I still have yet to get any up and running.
So no one else has to look it up, 120°F is 49°C
The quality has held despite a drop in users.
I feel like I’m going mental over here because this has not been my experience. The quality has always been spotty, but the last few months I’ve noticed more and more posts linking to awful “news” rags or no source at all. Worse, I rarely see people questioning the lack of quality information, simply gobbling it up because it aligns with their world view. Plus 70% of the comments on this platform could be generated by a classic r/subredditsimulator style bot and nothing would change; the same 5 points about AI, capitalism, and Linux are made in every thread in the exact same style every day.
And yes I’m mostly talking about news communities because Linux comms are usually fine but repetitive and while I’d love to interact with non-news content there just… isn’t much being made.
It doesn’t have to be, but by nature of anyone being able to spin one up, people will end up on hobby instances.
Traditional social media is run for-profit and thus has an incentive to keep their website online as much as possible to keep their company alive by gaining users and revenue. And I would bet they do have backups. Hobby websites like fediverse projects often are can be run by any flaky nobody that can have varying motives and varying data retention practices.
In this nazi analogy it would be less of buying chairs and more the nazis giving away chairs for free that come with blueprints so if the nazis started installing spikes in their chairs people can just build their own from the blueprints, they just choose not to because it’s a lot of work. Which is fine if you don’t want those chairs, but a lot of people are fine with those chairs as long as the nazis don’t start any camps.
Just skip to the point and make it 1 day
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.
that statement has been used so universally sarcastically that no one believes you’re being serious when you say it now.
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.
I tried it first and swapped away. I know I didn’t like how Radicale required editing text files to add accounts, that’s for sure, but the main reason I swapped was that the Docker environment kept freezing and using up 200% CPU until I manually restarted it. Rinse repeat every few hours. This was on a new install with 1 user. No issues since I moved to Baikal and the web UI is much nicer.