kolorafa

Explain how can you use KeePass+Syncthing with 10-50 people (possibly different groups for different passwords) having different sets of access level while maintaining sane ease of use?

The passwords are encrypted in the first place so the security for them is only on the client side.

Because Nginx Proxy Manager exists.

And also because for me it started from web hosting where Apache and Nginx dominate and later because of many easy to understand example configs from the net including many "docker letsencrypt" examples.

You can go to /var/log/apt/ and read the history.log as it will contain every single package that you did install/remove.

Based on that you can just restore it to working state by manually undoing the changes (removing installed, installing removed)

I use to split personal and work stuff.

Mostly just change desktop wallpaper, have different pinned apps, and have some apps forced to start on specific activity using kwin rules.

And I sometimes also on top of that use workspaces, for additional split if different set of work/personal activities like switching between projects or leaving chat on one and IDE on another.

So it's almost like a simple 2x2 workspace grid but with additional window/taskbar rules.

...

Looks like the installer and grub is confused about the hard drive order different in instaler and different while booting, both those drives could also have the same partition/drive ID making it confused, that could happen if you cloned/copied the drive in the past

I would say as a easy and safe solution

1. unplug all other drives that you don't want install linux
2. Install Linux (best by formatting whole drive) - it should work just fine at this point
3. After confirming everything works - connect the other drives back
4. If Linux no longer boots after adding drives then tweak disk boot order in BIOS

First moved from 7 on home PC as a daily driver

And then later once I stopped distro hopping (stopping at Arch) and could do my work in full from home... ( by porting time tracking app to Linux )

Moved from 10 on work PC

I play BeatSaber and few more VR games using ALVR and it's working great. (But I know that not all VR games fully work on Linux)

But you just need to know that its for Quest headsets running mostly over Wi-Fi (but you can also run over USB) so your milage may vary depending on your WiFi setup.

I use Arch btw 😅

Whenever i get the Crash report window I fill it as much as possible and send, I stopped manually going into bugs.kde.org and manually create bug after the response I got was "it's probably nvidia issue", but for last months I'm on new AMD gpu and those issues still persist and I already learned to just periodically run kwin_x11 --replace& disown; exit to fix them and go with my life.

And yes, the issues is probably not easy to track, as it only happen after at least few days or running it.

Just recently the switch from plasma 5 to plasma 6 introduced another bug with the windows - every few hours/days i get a window that is visible but all mouse clicks go thru it and actually the window behind it receive those clicks, to fix it I (once again) do kwin replace.

And yes, I'm heavy user with 2 workspaces * 2 desktops * a lot of open apps/windows running 24h/day, to the point just few days ago I got and error in console "maximum number of clients reached" when on X11 when trying to open any new window... (And I didn't run out off RAM (48GB) or VRAM (16GB))

So as much as I'm full time on Linux desktop for 8 years, the experience did improve a lot, but the stability of long running KDE Plasma slowly degraded over last years, hence my response.

And I did have the same issues on my 8 year installation of Arch and on KDE Plasma.

I had only few crashes and only on plasma 6, yes I did switch to 6.0.1 which is very quite new, so few crashes could be expected, but I'm on 6.0.4 (will update to 6.0.5) and kwin is still buggy with window ordering, and compared to xorg, on wayland I can't do kwin_wayland --replace because it closes all my open windows/apps which is annoying. Heck, even killing/restarting plasmashell also shutdown all apps that was started from menu...

Why did I switch? Because of hoping that issues from 5.x was fixed in 6.x but that was not the case :(

Same that not many issues will crash whole kwin so they will never trigger "crash report". It would be nice to have some some way to easy "trigger" state dump and open issue. That I would like the 'stability' and those last 0.001% of stability polish to be the focus for KDE.

So as much as I love <3 KDE Plasma, and I yearly donate to KDE, I still can't with clear mind suggest anyone to switch from MS Win to Linux (KDE) especially now with Wayland that made me lose all my unsaved work 3 weeks ago due to kwin crash.

Make the plasmashell especially kwin stable, as its crashing a lot, and with wayland it's taking whole session down...

To the point I went back to Xorg

I would suggest to add those additional AP as soon as possible if going UniFi way, as adding more later might require to replace all units as we already saw multiple times with UniFi devices, as they are quick to deprecate old ones and make them not work with new ones.