By encryption you mean disk encryption? I'm not using that so hopefully won't have to do anything
Also I looked up that ftpum stuttering issue and it doesn't match with what I'm seeing. It's not a stutter, just a complete freeze of the screen for a solid second, and then it returns to being completely normal.
During the minute that one of these freezes happened, this is the log output:
Mar 30 12:14:42 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:42 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:42 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:42 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:42 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:42 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:39 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:39 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:14:06 HAL systemd[1880]: Started VTE child process 5674 launched by gnome-terminal-server process 5653.
Mar 30 12:14:06 HAL systemd[1880]: Started GNOME Terminal Server.
Mar 30 12:14:06 HAL dbus-daemon[1892]: [session uid=1000 pid=1892] Successfully activated service 'org.gnome.Terminal'
Mar 30 12:14:06 HAL systemd[1880]: Starting GNOME Terminal Server...
Mar 30 12:14:06 HAL systemd[1880]: Created slice Slice /app/org.gnome.Terminal.
Mar 30 12:14:06 HAL dbus-daemon[1892]: [session uid=1000 pid=1892] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.108' (uid=1000 pid=5650 comm="/usr/bin/gnome-terminal>
Mar 30 12:13:53 HAL rtkit-daemon[1238]: Supervising 12 threads of 5 processes of 1 users.
Mar 30 12:13:53 HAL rtkit-daemon[1238]: Successfully made thread 5636 of process 1889 owned by '1000' RT at priority 5.
If they want to use it that's fine. I'm just cautioning against using a command line tool like that until they feel somewhat comfortable with the terminal.
Docker is a developer* tool, not really something you should be using without some technical knowledge, or at least some experience in the terminal. It's purely a terminal application, so you just type "docker" in the terminal to use it. You can also type "man docker" to view the manual (which shows arguments and command you can use) but again, that won't help much without some prior knowledge.
The things you're trying to use look like self-hosted web servers, which is a lot to set up for someone who's new to the terminal. I won't stop you if you want, but be warned. I'd recommend using something simpler like cozy, which you should be able to find and download in the software store.
*Edit: it's not only a developer tool, it's used for deployment as well. I lumped the two together. It's still a tool made for people with more familiarity using the terminal though.
Yeah it's fine right now, but these companies are prone to changing their minds. I think it's a good option but also wouldn't put it past discord to suddenly decide to crack down one day.
I would caution anyone using a client mod like that, since it is technically against Discord's terms of service. To be fair I've never heard of them banning anyone for that, but it's worth noting. Webcord is generally a much safer option.
/bin, since that will include any basic programs (bash, ls, cd, etc.).