There is no need for them to bring pain to me or anyone else. The bot
ones are also personal and won't say anything to anyone unlike the life
parts.
Removing them entirely doesn't feel right, so I begin just by hiding
them. One shows hint of hidden content in the blog page, but I don't
feel the need to change it.
It became horrible mess including four primary accounts plus two not so
important accounts + two Google accounts, so I am going to pretend XMPP
doesn't exist and manage keys with everyone invidually as needed as
currently I have only one actively XMPP using contact.
The rest moved to Matrix.
This time I didn't log out or anything, previous time I changed key I
hadn't noticed that the fingerprint included slash and continued for
longer than I had pasted.
Multiple redirects for different forms that could be used accidentally
or needed. It's link to Gogole Drive directory with different manuals
for different things at different locations.
I wished to fix disappearing notifications by using the F-Droid version,
but it worked even more badly disappearing when screen turned off
(possibly related to Greenify's aggressive doze even if it was
whitelisted) and then I returned to Play Store version and thought I
have to boot laptop for fixing this.
Backup plan: add Pushover email address to Riot.
The room #matrix:matrix.org is bridged to #matrix at freenode and
the room #irc:matrix.org is bridged to #matrix-irc at freenode.
Thanks Levans for noticing.
Phone#2 is having factory reset or more accurately many SailfishOS
updates since the recovery image which could be even older if it wasn't
in repair once.
I am at Kotka for Christmas and possibly new year while Terasar is at
home so I cannot check what it says thanks to Matrix only showing
fingerprint on that device.
* All downloads of Firefox Extended Support Release
* LastPass for Firefox (some redirects go to this file)
* All downloads of Firefox
* At time of committing this is very difficult to find and I found
here by editing URL of Firefox beta equivalent.
1. Note that settingumodes to be send to server on connect doesn't apply
until the next connect.
2. Future happened, so document two methods of setting umodes with
WeeChat, the old way (traditional would have messed lines) and new
modern way starting from 1.7+. I am not removing the old way as it
won't stop working and 1.7 is currently the git version. Also note
that the umodes can be set per-network.
3. Make ZNC also talk of traditional way (it fit without breaking lines)
and the modern way linking to issue about it and also clarify that
which networks the umodes affect depend on which levels you load
perform.
4. Add missing dot after umode +x which didn't have it even if the other
umode explanations had it.
Aminda Suomalainen