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)
brenno
joined 1 year ago
Imagine excluding almost all servers that don't have a gui and docker images from the Linux definition.
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.
What I do nowadays is to have Timeshift daily backups in case something breaks the system and the Ubuntu backup application doing daily backups of my home to my NAS. I don't have a separate home partition although this is often recommended.
This setup saved me once, but I haven't needed it for almost 2 years now.
Doesn't windows ship with a native email client? I don't use Windows but I remember an email app on it.
Of course you can use a reverse proxy to expose your apps to the internet.
Here's another similar solution that you can self host in a cheap cloud VM:
First of all you need that your ISP actually gives you an IP that points back to your home network. It's not uncommon that your IP points to some ISP NAT that routes the internet to many houses, making it impossible to expose some device in your network to the internet.
It was my case, then I needed to call them and ask to have an IP that goes directly to my gateway.
After that you can go to your gateway and do port forwarding from the internet to your server in your home. For example, you can forward port 80 from internet to your server private IP on port 80, so when someone browsers your IP it will get whatever page is hosted on your server.
About server tech specs, it depends on what you want to host. I used to host a personal Nextcloud server in a raspberry pi, which is really power efficient and cheap to maintain. Maybe you'll want a server with higher specs that might draw more power. It's really up to what you wanna do specifically.
To be honest after I switched to Bitwarden I could not find a reason to leave it even having access to Proton pass due to my plan with them.
It works and fills my privacy / licensing requirements.
I find myself spending less money on useless stuff by not seeing as many ads as before and getting more neutral search results.
Before I was finding myself wanting to buy certain stuff because they looked cool in ads. Now I think more on what I want to buy and start exposing myself to that product or service after the decision was made.
Canonical also tried this a few years ago with their Ubuntu Touch crowdfunding and failed. Even released some convergent devices but that didn't sell much. My impression is that although the concept is cool it is simply not appealing for the general audience
They sell a bunch of models with Ubuntu pre installed in Brazil also. Not every model / configurations, but even gaming laptops are available here.
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.