Ahh. Bone Apple Tea moment.

This reaks of chatgpt. All the way down to the milktoast ending.

It’s ok. I would go with “user hostile” in this case.

Fair. But in that case best use a more appropriate word.

I get not being a fan but no toggle switch. But in this case it literally isn’t “enshittification”. Is it anti choice? Yes. Is it enshittification? No. Enshittification does not just mean “thing I don’t like”.

Here is a quote that describes what enshittification is:

Here is how platforms die: first, they are good to their users; then they abuse their users to make things better for their business customers; finally, they abuse those business customers to claw back all the value for themselves. Then, they die. I call this enshittification, and it is a seemingly inevitable consequence arising from the combination of the ease of changing how a platform allocates value, combined with the nature of a “two sided market”, where a platform sits between buyers and sellers, hold each hostage to the other, raking off an ever-larger share of the value that passes between them.

More info can be found here. https://en.m.wikipedia.org/wiki/Enshittification

I know “Enshittification” is the Lemmy word of the year but you can’t just call everything you don’t like enshittification.

This clearly isn’t it.

I agree that’s why most of my systems run btrfs. (Maybe soon bcachefs).

But XFS is in the same tier of “datedness” as EXT4, just with more performance. Some apps like ScyllaDB actually require XFS performance crazily enough.

Btrfs or XFS.

No idea why people are into EXT4. XFS is more performant by far.

As a workaround yes. Just do your NFS exports over WireGuard. WireGuard acts as the authentication and encryption.

SSHFS will be incredibly slow. I would avoid it personally.

NFS will be performant and is easy to set up. This being said by default NFS is without any security.

The problem is that Kerberos is a huge pain to set up. I would avoid this unless you really need Kerberos.

If you want security NFS + WireGuard will serve you well.

Also I would consider Samba/CIFS if it is for local convenient fine access. It’s not super secure but for me it’s a good trade off.

You can fix this by manually placing the /boot partition outside of luks when you do your install. I did it and now my opensuse system boots in a reasonable time. Annoying to do but 100% worth it.

It because zypper is incredibly slow. They’ve been slowly working on the features needed to make it faster but they haven’t come together yet. I would guess early 2025.

Yes. The left side of the : in the volume is the file on the host. You can see this directory on the host. The right side of the : is where that directory is replicated into the docker container.

All you need to do is to interact with the directory on the host.

You should use volumes over bind. You just move your media into the volume location on the local host and try will show up in docker. You should never need to ssh or sftp into the container.

There is a lot here but I think the most important thing is that docker containers should always be disposable. Don’t put any data into the container ever.

All of your data and configuration should be done in volumes. Local disk to inside the container is all you really need.

By doing this you make updating any given docker container easy as just pulling the newest tagged version of the container. If you are using docker and not podman you can use tools like watchtower to do this automatically.

As for what distro, it depends on your goals. Do you want to learn and improve your skills? Stick with Fedora or Rocky or Debian or openSUSE. I recommend learning the command line as you go, but if you want a nice UI openSUSE has Yast which is a very robust tool.

If you want to just have a home NAS but don’t want to learn that’s a different question. In this case if you’re getting a proprietary NAS anyway you could just get one that supports docker (like synology) and kill 2 birds with 1 stone.

https://codeberg.org/forgejo/discussions/issues/67

The biggest issue is they require your to give them your rights as they pertain to copyrights.

That means even if you submit MIT or GPL licensed code they can just instantly say “we relicense this code as proprietary” and there is nothing anyone can do.

They rejected a bunch of valid PRs. Including the one linked here because the author refused to assigned their copyrights to the Gitea corporation.

Right now Forgejo is a drop in replacement. This article is them announcing that Forgejo will eventually not be one.

Because gitea is fully the victim of corporate capture. Any PRs that make gitea better in a way that would reduce the main corporate “sponsor” profit are rejected.

The company has a conflict of interest with the community and it shows. Forgejo is sponsored by a non profit open source cooperative.

+1 For Seafile. They put out a docker image that works well. It hasthe fastest sync I’ve ever seen and it has good clients.

Same thing happened to me. I ended up finishing up the upgrade in Sway. Not a great user experience, but it wasn’t a huge deal for me.