I use Casa"OS". It’s fine, but nothing groundbreaking. Cockpit for example can do pretty much the same, and for Docker containers, I nowadays mostly use docker compose.

But hey, it helped me a quite a bit in the beginning, and it’s cool. Pretty basic, but enough for most people, mainly beginners.

Logseq and Obsidian are only similar on the first look, but very different usage wise. Both are very open with a plugin system, and you can modify them to turn them into one eachother.

So, if you want only FOSS, then Logseq is the only choices you have.

But Obsidian is, even though it’s proprietary, very sane. Open plug-in system, active community, great devs who don’t have much against FOSS, and more.

Obsidian

• More similar to a classic note taking app, like OneNote, but with a lot of features. Hierarchical structure, and more of an “essay” style, where you store a lot of text in one page.
• Page linking is only done when you think it makes sense
• Has been a bit longer around than Logseq, feels more polished
• Great sync and mobile app, which support plugins from what I’ve heard

Logseq

• Non-linear outliner. Every page is on the same level, but within a text passage, the indentation matters (parent-child-relationship)
• You create a LOT of more pages. Most of my pages are empty. They are mainly there for linking topics. I rarely create pages manually.
• The journal is where you write most stuff. You then link each block to a page.
• Logseq a bit “special”. May not be for everyone. I for example am a bit of a disorganised thinker, who mentally links a lot of knowledge and throws concepts around all the time. Logseq is my second nature, because it’s more flexible. My GF on the other hand is more structured, and prefers something like Apple Notes, or, if she would care about note taking, something like Obsidian.
• The mobile app isn’t great. It’s fine when I’m not at home, but the desktop version is the “proper” one, and mobile/ iPad a second class citizen.
• Sync is only experimental for now. It will soon be officially supported (hopefully) and self hostable, but it worked fine for me.

I don’t see any problems with that. Even I (and probably most others here), who are FOSS advocates, think Obsidian’s model is fine.

The devs surely get why FOSS is important, and try their best to match the pros of open source. They even stated that if the company goes bankrupt or they stop developing the app, they’ll open source it.

One major thing they do absolutely right is how the notes get stored. On other note taking apps, it’s a proprietary database, often “in the cloud”, where your notes get hold hostage. Here, they’re just Markdown files, and the whole thing is pretty open, encouraging a strong community.

It’s similar to Valve/ Steam. Proprietary, but liked by most Linux people.

That’s not what OP was asking for though.

Why not? In my comment I explained exactly what benefits it would have in this case with a Nvidia GPU. I think it makes sense to at least mention the option.

OP tried Bazzite and wasn’t the biggest fan of it, but not because it’s image based, no, just because it uses the same Nvidia driver as upstream Fedora.

They could also have said that they really liked it, who knows?

And I don’t understand why the Linux user community on Lemmy pushes immutable distros so hard.

Because they’re awesome? They’re extremely low maintenance, just work (for me), are very robust, offer a lot of choice, and much much more.

I think they’re very underrated and should be used much more. Sure, some people just don’t like them, but some people would, and those should know this option exists.

I personally think X11 shouldn’t be used anymore. Fedora dropped official support for it recently iirc and it will soon be deprecated, so it might be even worse in the future.

Wayland works perfectly fine under Gnome from what I’ve heard, and with Plasma, it should be working great too.

You could maybe try Bazzite or Aurora/Bluefin.

They are all Fedora Atomic, the “immutable” Fedora variant, and offer baked in Nvidia support.

The cool thing is:

1. If the driver/ Wayland breaks on your install, then it will break on thousands of others simultaneously, and the devs can fix it very very quickly, because every installation is identical.
2. If it breaks, you can roll back in seconds and keep using the image that still worked yesterday. And in the meantime, the developers are already working on a fix, which takes just hours or a day max.
3. You don’t have to install and update anything yourself. Just do your computer stuff and stop worrying.
4. There’s also a GTS (or whatever it’s called) variant around, which is the last major version of Fedora. You won’t get the newest stuff and will be half a year behind in terms of features, but then there won’t be any surprises. I believe the bluefin:gts isn’t around yet, but will come with the next major release.

Each to their own. Linux is, in my opinion, about choice. If one prefers everything to be ultra minimalist, native and lightweight, then that’s fine.

I personally just find to be Linux’ most overlooked strength is containerization. It’s one of the main reasons why most servers run Linux, because of things like Docker. On the desktop, containers are way underutilized, but that’s now slowly changing with things like Flatpak or Distrobox.

A distrobox container is technically more bloated than a native install, sure, that’s correct.

But, in my opinion, it’s like saying “Drawers and closets are bloat for my apartment. I throw everything on the floor.” Yeah, now you have less things in your room, but it looks like shit, you can’t find anything and you fall over your tubberware that’s mixed with your underwear and shampoo.

Having everything collected in a container only costs me a few hundred MBs and a small amount of RAM if needed. But, literally every PC has more than 50 GB hard drive space and 8 GB RAM. If your system slows down because of one container, then your PC is the problem, not distrobox.

That absolutely doesn’t mean we should stop optimizing software of efficiency. But it can help us to spend our time on more important stuff, like fixing bugs or adding new cool features.

I really love Flatpak because of that. Sure, it has some drawbacks, but as soon as more devs support Flatpak officially, and iron out some issues we currently have, like misconfigured permissions, they’re (imo) the best package format. Why should a distro maintainer have to apply every software change to their package format? That’s needlessly duplicated work.

Just a small (or maybe big?) tip for you 🙂

If it’s for Linux, there’s a 50% chance there are no releases and 2 lines of commands showing how to build it (which doesn’t work on your distro), but don’t worry because your distro has it prepackaged 1 version out of date

There’s a tool called Distrobox.
You can install it (via CLI I think?), and then manage it the easiest graphically way via BoxBuddy (available in your Software Center), or just the terminal if you prefer it.

With it, you can screw all those “Doesn’t work on my distro” moments.

You’re on Linux Mint? No problems, here’s the AUR for you!

✨✨✨ BONUS: Your OS won’t break anymore randomly due to some AUR incompatibility, because everything is containerized! ✨✨✨

Even if you run Arch, use it to install AUR stuff. Or Debian/ Ubuntu, add PPAs only via Distrobox.

It’s absolutely no virtual machine. It basically only creates a small, lightweight container with all dependencies, but it runs on your host. Similar to Flatpaks.

You can also export the software, and then it’s just like you would have installed it natively!
Your distro choice doesn’t matter anymore. You now can run any software written only for Suse, an abandoned Debian version 10 years ago, Arch, Fedora, Void, whatever. It’s all the same.

I hope that was helpful :)

If you want to use this laptop with Linux and not spend time fixing hardware compatibility issues, then I definitely would not recommend this laptop. Definitely get a Dell XPS for a Linux laptop that Just Works.

Have you tried the -framework images from uBlue?

Logseq! Right now, you can only self host the database and sync it with Syncthing for example, but the dedicated sync feature is currently in beta and will be self hostable afaik.

Grocy is exactly what you asked for.

That’s actually quite cool to know.
I’ve always wanted to make my own Cola, especially since I can’t tolerate even small amounts of caffeine. Thanks!

I never had any (major) problems with Nextcloud yet.

I just have following “conflicts” with it:

• It doesn’t follow the “Do one thing, and do it right”-philosophy. It tries to do everything at once. File upload/ sharing, media management (NC Photos), RSS, mail, calendar, contacts, and much, much more. I mean, it’s damn convenient and works pretty fine, but nothing is great. For example, Immich/ Photoprism is way better than NC for photo management.
• There’s a lot of abandonware, or buggy/ unmaintained apps. For example, my “News”-feed looks completely broken for months now.
• The performance isn’t good. I mean, the “server” (an old thin client) isn’t fast at all, but the loading times and responsiveness is just awful. The file upload also takes ages, even from the same network.
• It feels bloated. I think, if I would be more into selfhosting and had more time, I would search for alternatives and split all the NC features I use into their own services, e.g. one for file upload, one for document management, one for managing my photos, an own RSS client, and more.

But, as I said, the ease of use and amount of features is still great. I don’t want to spend three weekends just troubleshooting my server and searching for/ installing dozens of individial services. And for that, it’s good enough.

If you have a spare laptop/ PC, I insist you to try Nextcloud.

It’s super easy to install, you actually just download the Docker all-in-one container and it runs in less than 10 minutes. You don’t have much to loose.
I’m relatively happy with it.

I mean, to be fair, NC isn’t perfect. It sometimes feels a bit wonky and tries to do everything, while exceeding at nothing.
But it’s damn comfortable to set up and maintain.

It doesn’t perfectly cover your use case, but everything else (individual services, including web server, database, etc.) is less centralised and more complicated to set up.
Since NC AIO is inside a container, all data are too. It’s a relatively straightforward file system afaik.
Backup also is included, but you have to do it manually by default and it stops the services while doing it.

For offloading large files, you might look into 3rd party tools. NC is basically a remote drive you can connect to with most programs that support it.

I get the same messages, despite using uBlue.
It’s because of Flatpak.

I disabled the notifications and enabled daily/ weekly auto-updates of Flatpaks, otherwise I would get spammed to oblivion.