Those locks are kinda optional. And luggage is way less important than all of one's communication ; imho.

Abolish marriage, too? Sure. But let the silly joke bring some joy to our miserable lives, pls.

Edit: I upvotes all your posts, but I still think that saying the joke promotes sexual harassment is stretching the concept

A baby dragon!

Create a user, and then a systemd unit for it, under ~/.config/systemd/user/ with contents like these:

[Unit]
Description=Caddy web server
After=network.target

[Service]
ExecStart=/usr/local/bin/caddy run --config /path/to/Caddyfile --envfile /path/to/Envfile
ExecReload=/usr/local/bin/caddy reload --config /path/to/Caddyfile --envfile /path/to/Envfile
Restart=on-failure
User=caddy
Group=caddy

[Install]
WantedBy=default.target

Adjust the paths in the arguments. It will require systemctl daemon-reload for such unit to be available for enabling and starting it...

Indeed! Before I was relying on the listing's of linuxserver.io , yunohost , casa os , etc .

Oh! I should get back to it... Togrther with the winamp skins I had downloaded from internet archive.

Plus projectM from Steam, and Spotube... I could stop using the monthly subscription for (*1) an ugly UI that barely handles drag-and-drop and is a mess to make my playlists with.

(*1) tbh, the recommendation engine got me hooked at first, but my interest has been fading away.

Oh.. I just saw your point. I'm comparing to Android (LineageOS) when it should be to iOS... void

Well, then this news are just sad.

We can't really know if BSD "lost" a sell to Sony. Right? I ask sincerely, maybe there's more to the case you cited.

From my naïve view, this new project can win new associated companies and get some income to pay new devs when some maturity is achieved on this framework since it's quite innovative and those companies can really participate whereas with a GPL they would just be left out.

I only mean to say that we might be discussing if the glass is half empty or half full. That's why I'm trying to put into this new perspective (like considering GrapheneOS as an example. In the long run, the license might not be that much of a hurdle. At least let's hope that's the case since they probably won't change to GPL.

A cheap VPS with headscale. Or just ZeroTier.com free plan.

The week went by and this was left unanswered. Usually I research a bit to treat anything on these threads. This time, I'm on the phone, so I went lazy and directly to chatgpt. Hopefully this is not an AI hallucination and it sheds some light for you.

The performance difference you're observing between AES128-CTR and AES128-GCM in OpenSSH with X11 forwarding can be attributed to several factors, including the nature of the ciphers and hardware acceleration support.

AES128-CTR vs AES128-GCM

1. Cipher Characteristics:

   • AES128-CTR (Counter Mode): This mode turns a block cipher into a stream cipher. It is generally faster because it can be parallelized and does not require padding.
   • AES128-GCM (Galois/Counter Mode): This mode provides both encryption and authentication (integrity check). The additional authentication step can introduce overhead, making it slower compared to CTR mode.

2. Hardware Acceleration:

   • AES-NI Support: Modern CPUs support AES-NI (Advanced Encryption Standard New Instructions), which accelerates AES operations. Both CTR and GCM modes can benefit from AES-NI, but the extent of the acceleration can vary.
   • GCM Overhead: Even with hardware acceleration, GCM mode has additional computational overhead due to the authentication process. If the hardware acceleration is not fully utilized or if the implementation is suboptimal, this overhead can become more pronounced.

Checking Hardware Acceleration

To determine if your system is using hardware acceleration for AES operations, you can check the following:

1. CPU Support:

   • Verify if your CPU supports AES-NI by checking the CPU flags:

     grep aes /proc/cpuinfo
     

   • If you see aes in the output, your CPU supports AES-NI.

2. OpenSSL Benchmark:

   • Run an OpenSSL benchmark to see the performance difference between CTR and GCM modes:

     openssl speed -evp aes-128-ctr
     openssl speed -evp aes-128-gcm
     

   • Compare the results to see if there's a significant difference in performance.

3. SSH Configuration:

   • Ensure that your OpenSSH configuration is optimized for hardware acceleration. You can specify the ciphers in your SSH configuration file (/etc/ssh/sshd_config for the server and /etc/ssh/ssh_config or ~/.ssh/config for the client):

     Ciphers aes128-ctr,aes128-gcm@openssh.com
     

   • Restart the SSH service after making changes:

     sudo systemctl restart ssh
     

Conclusion

The performance difference between AES128-CTR and AES128-GCM is expected due to the additional authentication overhead in GCM mode. Ensuring that your system is utilizing hardware acceleration (AES-NI) can help mitigate some of this overhead, but GCM will generally still be slower than CTR. If performance is critical and you do not need the additional authentication provided by GCM, sticking with CTR mode might be the better option.

Check if airvpn client has a Killswitch option.

Are you using docker? If so, you may use gluetun or run the vpn client inside the qbittirent container

Also, some vpn provide adblocking. So, another way would be... skip pihole and just use raspAP to create a WLAN where all devices connect. You may even turn off your router wifi and rename the newly created WLAN so that your brother doesn't even know ;)

I haven't tried it really, but maybe there are tutorials.

I had the same personal experience (compared to spacevim, doomvim and lunarvim). I just want something feature rich working out of the box, like many other IDEs... With easy access to keyboard shortcut hints. And I want to be able to customize without breaking it. So far, I have been using doom emacs. The reason is that vim didn't have a curated set of plugins that I could tinker with without being frustrated. Again, this was my personal experience with it over the years. I just kept 'raw' vim, and used many other CLI tools around it (e.g. lazygit, a python REPL, etc.)

I never picked up any of these languages to be honest.. I mean, vimscript or Lua.

Maybe if I had, my experience would have been another. I know many people that know basic vimscript prefer to have 'vanilla' config, sometimes not even using vimplug or pkg managers. And they got along better than I did with my empty vimrc ;)