

Yes, and that’s why I switched to Kagi
Yes, and that’s why I switched to Kagi
Cheese bread
Wait and see you distrohopping every month for years ending up in a boring stable distro.
What do you use as a Google Photos replacement?
To be honest, no. I run in a Truenas Jail, and its stable for me. Just a bit slow for big files sometimes.
I host it in a Truenas BSD Jail, and the process was as straightforward as compiling and running any other Rust / Postgres project. Which error did you get?
If you remove the app-platform role from Nextcloud by separately hosting the individual apps, what benefit do you get from having both Nextcloud and File Browser?
Nothing really. For almost any Nextcloud feature out there, you can find a server app that does the same.
But that’s the point in my opinion. I don’t want to waste time managing tons of apps if I can manage one Nextcloud instance. Nextcloud basically decides for me what’s the best way to get those features running, so I don’t need to figure out myself.
Now if you’re into self hosting one container for each feature, go for it, no reason to not do so.
An open source alternative is FRP
https://github.com/fatedier/frp
It’s a reverse proxy server that you install in both your server and a VM in the cloud, and it tunnels your server over the VM, like Cloudfare solution.
Why don’t you install flatpak on Ubuntu, make the packaging migration before doing the OS migration so you can evaluate your workflow with the new packaging system? Afer you’re used and confident with flatpak, backup and restore the flatpak folder into fedora and you transition should be smoother (don’t need to worry with 2 stuff at the same time)
As an addition to other responses, think that most apps (specially smaller ones) are developed using some framework or set of libraries that might or might not support those protocols.
So let’s pretend that I have an app buit using Electron and that framework does not support Wayland. There’s nothing I can do on the app side until Electron supports Wayland in this fake example.
So it actually takes time for the libraries to support the new protocol and then app developers to update their apps to support it aswell.
That’s why you see that the Wayland migration is incremental and not all at once.
Only if every btc node used this binary but because it’s decentralized theres multiple people compiling the source so the affected binary would not be affected.
In centralized software something like this is way easier. VSCode for example adds proprietary telemetry on top of their open source code and because most people downloads from the website instead of compiling, they ended up using a software that diverges the source code implementation. But even in this case you could use Codium that implements the source code version.
I started with a pi 4 and it worked really well!
I think the key here is to favor stability than latest features as you don’t want your server stopping due to bugs.
So the systems being recommended here, like Debian and Ubuntu LTS are good.
Nowadays I don’t even bother with upgrades anymore. Snaps and Flatpaks auto updates automatically, and for system updates Ubuntu notifies once a week.
For me the experience nowadays is better than before, where app updates are tied to system updates, meaning that older bases (like Ubuntu LTS) got behind on some softwares.
Snaps have a similar deduplication mechanism, and snaps allows calling apps from their names like you would do with regular packages.
I think the reason for the second one is that while snaps are also meant to be used in servers/cli flatpak is built only with desktop GUI apps in mind.
That would be the same of hating docker because it creates networks. It’s just how it’s sandbox works.
This seems like free hate as you can use certbot without snap without any problems. Imagine stopping using Firefox because of the same reason for example
In Brazil I pay 20 USD for 500mb. There are plans in my area that sells 1gb for 30 USD. Thay can’t put data caps due to legislation, only on mobile data (which I pay 6usd for 20gb cap, 5g)
I’m not defending canonical decisions, but definably when they started working on this there was no other alternative available for them to collaborate at the time
I like Thunder