I'm all in for new takes that start with a clean slate, if that's what happens in the near future (e.g. redox-os grows bigger than gnu/ linux *), yet it saddens me that there's personal health costs on these developers that just wanted to contribute.
* after all, the year of the gnu/ linux desktop has already been past :P
I wonder if I know any other expression than: oh lala.. something! Yet, you know so many expressions that you can easily recall your own "top 20". Perhaps you do speak French?... Or I'm just a blatant ignorant xD
I use anzo and as password an empty string. It's never been guessed :p
Oh, I have no intentions to join. That's what I meant to say. I find the instant messaging rooms a bit overwhelming. Unless is strictly necessary for moderation, and even then I'd be looking for long-term alternatives (as in, other mods here or whatever)
Perhaps you need to use -ctime parameter on find command.
You're probably over-complicating things. Have you heard about the find -print0 | xargs -0 idiom? all that variable interpolation (dir=${dir:2}) and quoting "'""${dir}""'" is better to be dealt by the built-in shell tools. Or you could write a script for the whole body of that while loop, and then call find . -exec ./action.sh {} \;. Same script could be used with the previously mentioned idiom too, you'd need to use bash -c ./action.sh though. One advantage of "find | xargs" is that you can run these concurrently, paralellizing the action to all your dirs, in groups, of say 4 of them... and so on... it's cool and simple.
Movary comes to mind, and it can pull/ push info to accounts on third parties like tmdb.org
Actually, only after posting it came to my mind that anyway all intel nukes are fangless. That's their appeal. So that their bytes leave no marks. Long live the vempire.
I'm unsure but maybe hetzner admin panel is usable without JS.
Check for any customizations in /etc/NetworkManager
Alternatively, reinstall surfshark, enable killswitch, connect and disable killswitch before disconnection... When you disconnect it should be fine..
The killswitch is most surely a combination of changes on networkmanager dispatcher script, iptables rules and dns setting (/etc/resolv.conf)