Patrick

> Any idea why clicking "Open Data Folder" opens a web browser rather than a file browser application? HexChat opens a `file://` url with the default handler on the system...

If somebody can handle the theme name here and test that it works it would be appreciated: https://github.com/hexchat/hexchat/blob/90c91d6c9aa048eff8f8f8f888d37a21fd714522/src/fe-gtk/fe-gtk.c#L296-L301

Add `|| g_str_has_prefix (theme_name, "NAME_OF_XFCE_THEME")` to that line. Then build hexchat: https://hexchat.readthedocs.io/en/latest/building.html#unix And test.

For what its worth I made a test branch for hexchat supporting rfc3454 though no network implements it afaik to try it.

> How are we going to maintain the backward compatibility? It is a joke but it is a solution, convert it to punycode (or similiar) for non unicode clients. >...

I don't think there is really any way to sanely identify the network by the hostname. The server can't tell you every hostname as a malicious server could break other...

HexChat can't directly consume JSON as that requires a library. So that only leaves ini files which seems like what you had.

```ini [NetworkName] servers=foo.bar.net,baz.bar.net:+7000 port=6697 ; default if not specified ssl=true ; default if not specified encoding=utf-8 ``` Split servers by `,`. If a network has different encodings per server.. well...

The biggest problem with ini is honestly how inconsistent implementations are. Python's `configparser` is 'ini-like', GLib's `GKeyFile` is a freedesktop ini-like format, etc.

My example supports mixing ssl/ports/ips, but not encodings/descriptions which isn't valuable to me personally.