carzian

Plasma 6 is built using QT 6, currently plasma 5 is using QT5. This is a huge effort to move the code to the new version of QT but it brings many improvements behind the scenes. Once this is done a lot of the code is going to be cleaner and more maintainable, which should translate to a smoother user experience.

Here's the plasma 6 wiki: https://community.kde.org/Plasma/Plasma_6#Work_that's_been_decided_on_but_not_implemented_yet

I've also used anonaddy for the last two or so years. It's been great, no complaints

I highly recommend using heat-press inserts. They allow you to put a threaded hole pretty much anywhere. It makes designing much easier and the end result will be stronger.

Loved the porko roso plane

Man this looks like a great release. Can't wait to play around with it

What no one else has touched on is the protocol used for network drives interferes with databases. Protocols like SMB lock files during read/write so other clients on the network can't corrupt the file by interacting with it at the same time.

It is bad practice to put the docker files on a NAS because it's slower, and the protocol used can and will lead to docker issues.

That's not to say that no files can be remote, jellyfin's media library obviously supports connecting to network drives, but the docker volume and other config files need to be on the local machine.

Data centers get around this by:

• running actual separate databases with load balancing
• using cluster storage like ceph and VMs that can be moved across hypervisors
• a lot more stuff that's very complicated

My advice is to buy a new SSD and clone the existing one over. They're dirt cheap and you're going to save yourself a lot of headache.

Using the HDMI out on the phone is the best option. If your phone doesn't support video out, this is the best way I found to do it.

I recently had to do this with my pixel when the screen died. I couldn't find this advice anywhere so I'm super proud of this work around. Unfortunately it's not easy. You'll need a OTG adapter, a wired keyboard, a Bluetooth keyboard, and a crap ton of patience.

Step one: enable android talk back/screen reader. This can be done using the volume keys or Google assistant. https://www.theverge.com/23184596/android-screen-reader-how-to-enable

Step two: connect the wired keyboard using the OTG adapter. Use the keyboard's keys to unlock the phone and use the arrow keys to navigate to the Bluetooth settings.

Step three: connect the Bluetooth keyboard to free up the USB port on the phone.

Step 4: use the Bluetooth keyboard to enable the backup method of your choice.

Bonus advice: Use Google play store on a computer to remote install a screen cast app https://www.howtogeek.com/690556/how-to-wirelessly-mirror-your-android-phone-to-your-tv/

Use the wired keyboard and screen reader to open the app and start the screen cast. That makes things much easier.

This was a few years back, maybe on 20.04 but could have been 18.04. The wifi card was a niche realtek that wasn't well supported.

The issue is more that neon and kubuntu both have trade-offs, using either means you will be using older software releases. Doesn't mean it will affect everyone, but for some people a rolling distro will be better.

Give it a shot! I did try running it on a live disk last week, the performance was really terrible (couldn't even move the mouse), don't give up on it immediately if that happens to you

I was using it on my older Asus and ran into wifi issues. I actually replaced the laptop before switching to tumbleweed. I'm running it on 3 computers so far, a Dell G15, custom built desktop, and a framework laptop.

I'm really liking it, it's a rolling release so it always has the news versions of everything, it's been really stable but also has a built in rollback feature in case there's a bad update

I've used kubuntu and neon in the past. The issue I ran into was kubuntu not having the latest KDE software, and it wasn't available in back ports. I tried switching to neon but it's based on the LTS version of Ubuntu so the kernel was pretty old, it didn't have great support for my hardware.

I switched to tumbleweed and have been loving it since.

I definitely recommend you do your own research into this. Brute forcing ssh keys should be practically impossible. Is it necessary to install fail2ban with password login disabled? Not sure, I'm of the opinion that it won't hurt, just one more line of defense. It's pretty easy to setup.