Val Lorentz
Val Lorentz
Depends on #1483 (yes I opened that issue just because of this, but it has been on my mind for a while) Relationale: This would mean trying INVITE and waiting...
You could use code from Owner (here: https://github.com/ProgVal/Limnoria/blob/master/plugins/Owner/plugin.py#L62 ) and add something similar in `src/conf.py`.
https://docs.python.org/3/library/tempfile.html#tempfile.TemporaryDirectory
Looks like GNOME broke these links. The "new" URLs: * https://developer-old.gnome.org/libpeas/stable/ * https://developer-old.gnome.org/gi/stable/
One of the purposes of `UTF8ONLY` is to prevent misconfigured clients from sending or decoding messages with the wrong charset, so I think it makes sense to override it in...
> this permanently denies the user the choice of using any other encoding. Yes, that's a feature. It means that, once enough clients support it, server operators can safely enable...
If I'm not mistaken, this PR only changes the encoding for the connection to servers that advertises UTF8ONLY, not for other connections. > What will happen when users find that...
I don't know how these scripts work, but if they send non-UTF8 data, then `UTF8ONLY` servers will reject them; with or without this patch.
Did you try on a `UTF8ONLY` network (eg. [ergo.chat](https://ergo.chat/))? They are likely to be rejected.
If it works, it means your script only sends UTF-8 data, so it won't be affected by this patch.