Mikaela/mikaela.github.io
1
0
Fork 0
mirror of https://github.com/mikaela/mikaela.github.io/ synced 2025-01-11 13:32:36 +01:00
Code Issues Projects Releases Wiki Activity

Quickly point freenode -> LiberaChat where applicable

Browse Source 
* ZNC had to have network name removed to avoid rewriting history.
* Keeping the ops opped is linked too widely and I just added a note
  that it also applies to LiberaChat directly
* umode+g I don't feel good about so I just removed it directly, I am
  not who I was in 2015.
  * references to it had to go away too
* LiberaChat runs Charybdis fork which removes the weird cmode +p
  behaviour to my knowledge
* Stagefright also couldn't have history changed so I just removed
  broken link and said it's now at LiberaChat
* ...
* TeleIRC instead of TeleMatrix had to go away, neither project is alive
  and due to freenode/LiberaChat situation living, I will hopefully
  update it to Matterbridge and more recent solutions in the future.
  TODO! Also RELAYMSG exists.
* links2: mostly dead links, but change network name
* r/chanserv: the link was dead
* r/mer-meeting: I don't think anyone uses that link and I have no idea
  if they are staying on freenode
* r/telefreenode.md: I imagine everyone has took anything useful from
  there a long time ago
This commit is contained in:
Aminda Suomalainen 2021-05-23 14:10:38 +03:00
parent 1617253442
commit 9351e09a4a
Signed by: Mikaela
GPG Key ID: 99392F62BAE30723
14 changed files with 24 additions and 107 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
blog/_posts/2015-02-24-znc160-ssl.md
View File

@ -22,7 +22,7 @@ ZNC 1.6.0 also doesn't have option to blindly accept certificates, which
would be stupid, but sadly
[Quakenet is right about most of people just accepting certificates blindly](https://www.quakenet.org/articles/99-trust-is-not-transitive-or-why-irc-over-ssl-is-pointless)
as people are asking how to disable the SSL certificate verification on
\#znc at freenode a lot.
\#znc a lot.
Some people even wrote [a patch and scripts to disable the verification.](https://gist.github.com/KindOne-/52cfade7b937ee8b4c37)
This isn't a good idea as patching ZNC can cause all kinds of issues as
@ -94,18 +94,17 @@ function like suggested by @DarthGandalf on \#znc.*
*Added on 2015-09-03. 4. added on 2016-01-26.*
There are usually four causes for this. Lets use freenode as example
There are usually four causes for this. Lets use liberachat as example
network.
1. You don't have the `ca-certificates` package installed (`ca_root_nss`
on FreeBSD), so your system trusts no certificate authority. Install it
and try again.
2. You are connecting to wrong address. freenode's certificate is valid for
\*.freenode.net, but there are CNAMEs pointing there. If you connect to
2. You are connecting to wrong address. liberachat's certificate is valid for
\*.libera.chat, but there are CNAMEs pointing there. If you connect to
CNAME and the certificate isn't valid for that CNAME, the certificate
is invalid.
* You should always connect to either `irc.freenode.net` or
`chat.freenode.net` where it points to.
* You should always connect to `irc.libera.chat`.
3. There is MITM which is unlikely, but unlikely is not impossible.
Validating the certificates either by trusted certificates or verifying
the fingerprints securely manually protect you from this. If MITM is the

8
blog/_posts/2015-03-26-weechat-sasl-simply.md
View File

@ -43,7 +43,7 @@ Then simply set your username and password
```
*Replace NETWORK with the name of network that you have in WeeChat, for
example `freenode`.*
example `liberachat`.*
And now after `/reconnect` you should be identified automatically using
SASL, but you might also ensure that you use SSL.
@ -53,8 +53,8 @@ SASL, but you might also ensure that you use SSL.
Change your address to use SSL port and enable SSL for the network:
```
/set irc.server.freenode.addresses chat.freenode.net/6697
/set irc.server.freenode.ssl on
/set irc.server.liberachat.addresses irc.libera.chat/6697
/set irc.server.liberachat.ssl on
/save
```
@ -62,7 +62,7 @@ Change your address to use SSL port and enable SSL for the network:
*6697 is the [standard SSL port](https://tools.ietf.org/html/rfc7194).*
Freenode has valid SSL certificate, but if it didn't, you would have two
liberachat has valid SSL certificate, but if it didn't, you would have two
choises:
1. Trust the fingerprints manually using

4
blog/_posts/2015-04-01-keep-the-ops-opped.md
View File

@ -12,6 +12,10 @@ redirect_from:
*Why I think that you should keep the ops opped instead of following
freenode's recommendations.*
***2021-05-23: this all also applies to LiberaChat and as this is possibly
one of the posts where I refer people to the most with anchor links, I am
not swapping the name like I am doing with everything else.***
Is there an issue with your IRC channel needing op attention? Without
having ops visible, your users will very likely go to the network support
channel instead of informing you or your ops.

67
blog/_posts/2015-04-02-umodeg.md
View File

@ -1,67 +0,0 @@
---
layout: post
comments: true
title: "Using umode +g / blocking unauthorized PMs"
category: [english]
tags: [english, irc]
redirect_from: /english/2015/04/02/umodeg.html
---
Since the [Limnoria episode]({% post_url blog/2015-03-25-leaving-bots-life %})
I have been blocking PMs from everyone, because multiple people thought
that as I am not part of any those communities anymore, the best way to get
support is PMing me which is wrong.
I get tired with telling people to go to proper channels, so I told my
ZNC to set umode +g automatically at freenode which accidentally went
to all networks (as I didn't have network level \*perform loaded), but I
am happy this way.
* I don't receive any unwanted PMs, so PM [harassment] has dropped.
* People learn basic politeness by having to ask before PMing.
[harassment]:https://github.com/Mikaela/freenode-harassment
So what if someone wants to PM me and does that without asking?
The sender sees the following:
```
Mikaela :is in +g mode (server-side ignore.)
Mikaela :has been informed that you messaged them.
```
And I see the following:
```
Michaela ~Mikaela@PirateParty/FI/Member :is messaging you, and you have umode +g.
```
All messages appear in server buffer and then I have some options:
* If I know Michaela and I trust that she has some good reason to PM me,
I can `/accept Michaela` and ask her to send the message again.
* I know Michaela, because Michaela is my altnick on many networks and
and this example comes from [PirateIRC] which is first network that
was open and that doesn't freeze [HexChat] when attaching to ZNC.
* If I have no idea who is Michaela, I can whois her to see if we share
any common channels and ask on those what she wanted to talk in PM
and if I see reason for it, I `/accept Michaela`.
* If I know that Michaela is some horrible person on channel, I can ignore
the notification on PM attempt as she is not going to say anything nice
or that is worth hearing, very likely harassment...
[PirateIRC]:https://pirateirc.net/
[HexChat]:https://hexchat.github.io/
If I had done `/accept Michaela`, she would be able to PM me until
* I removed the authorization using `/accept -Mikaela`
* I or Michaela disconnected
* Michaela changed her nick
I can also check which people are allowed to PM me using `/accept *`. PMing
someone automatically adds them to `/accept` on <s>modern</s> some IRCds if
you are on umode +g.
*[For (un)setting umodes, see this post.]({% post_url blog/2015-06-03-setting-umodes %})*

3
blog/_posts/2015-06-03-setting-umodes.md
View File

@ -31,7 +31,7 @@ way until you reconnect!**
* Modern way (1.7+): `/set irc.server_default.usermode -iI+wRQxg`
* *For setting umodes only for one network instead of them all
replace server_default with server.name, e.g.*
* `/set irc.server.freenode.usermode -iI+wRQxg`
* `/set irc.server.liberachat.usermode -iI+wRQxg`
* ZNC:
* Traditional way: `/msg *status loadmod perform` and
`/msg *perform add mode %nick% -iI+wRQxg`
@ -61,5 +61,4 @@ For what the actual umodes are on your network, try `/quote help umode` or
* Q — block channel redirects on Charybdis (mode +f or banforward).
* x — activates IRCd based uncloaking even if it's [not that reliable.](https://gist.github.com/maxteufel/1e2cf7ada079c271bd3c)
* g — caller-id, people must be `/accepted` or PMed before they can PM you.
More detailed post about that [here]({% post_url blog/2015-04-02-umodeg %}).
* t — only users using SSL can PM.

2
blog/_posts/2015-06-08-private_secret_channels.md
View File

@ -18,8 +18,6 @@ To make channel secret, there are two useful modes. You might also want to
mlock them with `/msg chanserv help set mlock`.
* +s — hides the channel from all channel lists (for non-opers)
* +p — depending on the network does the same, but on some networks such as
freenode hides the channel only from whois (of those people who are umode
-i). Keep in mind that you always see channels that you are on or share
with other people in whois. +p also prevents `/knock` (which is command
to request invite to the channel) on some IRCds.

6
blog/_posts/2015-07-28-stagefright.md
View File

@ -10,13 +10,11 @@ redirect_from: /finnish/2015/07/28/stagefright.html
*Stagefright on haavoittuvuus Androidissa, jolla haittakoodia voi ajaa
etänä. Lue lisää [Viestintävirasto Haavoittuvuus 067/2015](https://www.viestintavirasto.fi/kyberturvallisuus/haavoittuvuudet/2015/haavoittuvuus-2015-067.html)*
Valitin aluksi [Facebook-seinälläni] Viestintäviraston unohtaneen kertoa,
Valitin aluksi Facebook-seinälläni Viestintäviraston unohtaneen kertoa,
kuinka rajoittaminen tapahtuu käytännössä ja myöhemmin minulle selvisi
asia tarkemmin ja se olisi mahdollisesti ollut järkevämpää kirjoittaa
tänne suoraan.
[Facebook-seinälläni]:https://www.facebook.com/mikaelahmsuomalainen/posts/864710153623799
Tähän on kaksi minun tuntemaani tapaa
## Automaattinoudon poistaminen käytöstä
@ -28,7 +26,7 @@ Tähän on kaksi minun tuntemaani tapaa
## MMS APN-osoitteen poistaminen
Freenodessa kanavalla [#vapaakoodi](/r/irc-vapaakoodi.html) mentiin
Freenodessa (nykyisin Libera.Chat:issa) kanavalla `#vapaakoodi` mentiin
pidemmälle ja poistettiin koko multimediaviestien APN-osoite.
**VAROITUS: Et tämän jälkeen voi vastaanottaa multimediaviestejä ellet

6
blog/_posts/2015-09-19-atheme-quickstart.md
View File

@ -37,7 +37,7 @@ Now you should be successfully identified and should configure automatic
identification, I cannot help with it so much, but I can point you to
beginning:
* [freenode's SASL instructions](https://freenode.net/kb/answer/sasl)
* [liberachat's SASL instructions](https://libera.chat/guides/sasl)
* [My instructions for SASL with WeeChat]({% post_url blog/2015-03-26-weechat-sasl-simply %})
* [Searx YOURCLIENTHERE SASL](https://search.disroot.org/?q=YOURCLIENTHERE+SASL)
* IRCCloud: edit network and go to advanced settings and you will see box
@ -46,7 +46,7 @@ beginning:
that you specified a nick that is grouped to your account.
* Matrix: in the admin room (direct chat with the appservice-irc), say
`!storepass password` to have the password send with PASS on connect.
In case of freenode use `!storepass nick:password` and/or see more
In case of liberachat use `!storepass nick:password` and/or see more
information at [matrix-appservice-irc wiki].
* [IRC networks with Matrix bridge]
* [Matrix bridge end-user FAQ register/identify section]
@ -129,7 +129,7 @@ there:
* [Always add opers to access list (this is the $oper in my templates)]({% post_url blog/2015-01-10-channels-hostmask-groups-a-basic-howto %})
* oops, did I just repeat previous post
* [Keep the ops opped]({% post_url blog/2015-04-01-keep-the-ops-opped %})
* especially read this if you are at freenode or wondering why you
* especially read this if you are at liberachat or wondering why you
don't get automatically opped after registering the channel and
cycling while being identified!
* `/msg NickServ help`

6
blog/_posts/2016-03-09-weechat-tmux-quickstart.md
View File

@ -61,9 +61,9 @@ First we must connect to the network where the support channel of our
distribution is.
1. Add the network to WeeChat.
* freenode: `/server add freenode chat.freenode.net/6697 -ssl -autoconnect`
* liberachat: `/server add liberachat irc.libera.chat/6697 -ssl -autoconnect`
2. Connect there.
* `/connect freenode`
* `/connect liberachat`
3. Join the channel of your distribution.
* `/join #distribution`
* you can also join multiple channels at once by separating them by
@ -77,7 +77,7 @@ need to `sudo systemctl start gpm` or whatever init system you use).
2. `/mouse enable`
Now you should see bar with the core buffer (`weechat`), server buffers
merged to it (`freenode`) and `#distribution`. If mouse doesn't work, you
merged to it (`liberachat`) and `#distribution`. If mouse doesn't work, you
can `/buffer X` where X is the number to move. For moving between merged
buffers move to the buffer and press Ctrl + x.

1
blog/_posts/2017-09-19-teleirc-instead-of-telematrix.md
View File

@ -8,6 +8,7 @@ redirect_from:
- /teleirc.html
- /telematrix.html
- /english/2017/09/19/teleirc-instead-of-telematrix.html
published: false
---
*FAQ at SailfishOS Fan Club: why everything was made worse for Matrix users?*

2
pages/links2.markdown
View File

@ -25,7 +25,7 @@ random and [improvements are welcome here.](https://github.com/Mikaela/mikaela.g
<!-- * Minority-specific -->
* All GRSM (Gender Romantic Sexual Minority) people
* [##abgilpqt+ at freenode](/r/irc-abgilpqt+.html)
* [##abgilpqt+ at LiberaChat](/r/irc-abgilpqt+.html)
* [rules](https://abgilpqt.github.io)
* [webchat](https://abgilpqt.github.io/webchat)
* [#GayCafe at sorcerynet](/r/irc-gaycafe.html)

5
r/chanserv.md
View File

@ -1,5 +0,0 @@
---
redirect_to: https://blog.freenode.net/2008/04/registering-a-channel-on-freenode/
permalink: /r/chanserv.html
sitemap: true
---

5
r/mer-meeting.md
View File

@ -1,5 +0,0 @@
---
redirect_to: https://kiwiirc.com/client/chat.freenode.net:+6697/#mer-meeting
permalink: /r/mer-meeting.html
sitemap: true
---

5
r/telefreenode.md
View File

@ -1,5 +0,0 @@
---
redirect_to: https://gitea.blesmrt.net/mikaela/gist/src/branch/master/irc/telefreenode
permalink: /r/telefreenode.html
sitemap: true
---