> over the last years we had people getting confused over <suite>-updates
> (recommended updates) and <suite>/updates (security updates). Starting
> with Debian 11 "bullseye" we have therefore renamed the suite including
> the security updates to <suite>-security.
https://lists.debian.org/debian-devel-announce/2019/07/msg00004.html
I thested this earlier and am committing it in case I encounter Zaldaryn
sooner than anticipated and forget to copy the change and then start
doing conflicting changes there.
Is it going to be in tray kindly or will I distract myself by starting
to click and read on it? It's the only autostarting app that I cannot
configure to hide or be more unsuitable for bigger chats.
It turns out that having apps full of distractions starting
automatically is not good for focusing. This leaves three instant
messengers:
* Wire - family and other small groups
* Signal - some friends, unsuitable for large groups
* Gajim - polycule and small friend groups visibly autojoined,
everything else joined as minimized so it doesn't distract me unless
something notifies me
There are no actual license changes (or at least I tried to avoid them
by reading the `git diff`) and I added the lines missing from GitHub
selector, even if I have no idea where they originate from (the two last
ones).
Maybe three electrons not working with hibernate is another reason for
it to go out of fashion, I wonder if I should also add warning to myself
about quitting all electrons before either operation.
When I previously tried them, Snap worked better and Flatpak was
misbehaving, but now the situation seems to have turned around with Snap
unable to use some features such as tray icons (which is attributed to
an uptream issue with Electron builder).
* expected packages now also contains keybase
* Keybase's tray popup is now floating
* autostarting Flatpaks are separated from normal apps and below them
* Gajim has --quiet, even if it probably doesn't affect anything here
I need unisolated port for dnscrypt-proxy which I fear would otherwise
generate too many circuits which wouldn't even be used and I guess
there is no harm in sending Yggdrasil to a separate port that only has
access to onions which is a port I may sometimes wish I have otherwise
too.
OpenSSH is evil and gives you three not-optimal options to this:
A) trust DNSSEC and don't write known_hosts
B) ask whether to trust DNS, but don't bother telling me if it's signed
C) don't even check SSHFP
I see A) as the least evil, but I wish known_hosts was written.
Alternatively B) should tell me whether there is DNSSEC or not, not
only "matching keys found from DNS" or whatever it says always.
> The ClientPreferIPv6DirPort option is deprecated, and will most likely be removed in a future version of Tor. It has no effect on relays, and has had no effect on clients since 0.2.8. (If you think this is a mistake, please let us know!)
If the lowpower option uses values 40 and 20 which are a lot higher than
mine were and considered suitable for laptops and smartphones, I guess
they are the best for me to use and I find content faster.
