WeeChat version 0.4.2 or higher is required, but WeeChat 2.9 or later is recommended for the best experience.

Use TLS encryption

To start using Glowing Bear, follow the instructions below to set up an encrypted relay. All communication goes directly between your browser and your WeeChat relay! This means that your server must be accessible. We never see any of your data or your password, and you don't need to trust a "cloud". All settings, including your password, are saved locally in your own browser between sessions.

When using encryption, all communication between your browser and WeeChat will be securely encrypted with TLS. This means that you have to set up a certificate. While it's possible to use a self-signed cert, we recommend against it, because it's handled poorly in browsers, and may not work at all on mobile devices. If you don't already have a certificate for your domain (or you don't have a domain), we strongly encourage you to get a certificate from Let's Encrypt—it's free and easy. We'll walk you through it.

If you don't have a domain you can get a free subdomain from providers such as afraid. You'll want to set up an 'A' record to your server's IP address, and quite possibly an AAAA record to its IPv6 address. These might take a few hours to propagate, if the steps below don't work right away, try again in a few hours.

Getting a certificate is easy. You'll need certbot—just follow the encryptions at https://certbot.eff.org. If you're not serving webpages on the same server or are unsure, select "none of the above" (if you are, you can probably use that webserver to proxy your relay, and skip this—check out the instructions in our Wiki). Next, get the certificate with certbot certonly --standalone -d {{ settings.host || your.domain.com }} and follow the instructions.

Nearly done! Now you just need to copy the files into place. To do that, use the following commands, replacing the username placeholder with your actual username:

mkdir -p ~username/.weechat/ssl
cat /etc/letsencrypt/live/{{ settings.host || your.domain.com }}/{fullchain,privkey}.pem > ~username/.weechat/ssl/relay.pem
chown -R username:username ~username/.weechat/ssl/

Once you've got the certificate and moved it in place, you can set up an encrypted relay on port {{ settings.port || 9001 }} with these WeeChat commands:

/set relay.network.password y0ur_StRonG-pa$sw0rd:of*choice
/relay sslcertkey
/relay add ssl.weechat {{ settings.port || 9001 }}

Your certificate needs to be renewed every couple of months. Either follow the instructions for automatic renewal at https://certbot.eff.org, or run certbot renew manually when renewal is due. Important: You'll need to follow the instructions for copying the certificate to the right place again, and re-run /relay sslcertkey in WeeChat.

Use TOTP (Time-based One-Time Password)

Configure WeeChat for TOTP. The secret key has to be a base 32 string.

/secure set relay_totp_secret xxxxx
/set relay.network.totp_secret "${sec.data.relay_totp_secret}"

Open an authenticator app and create an entry with the same secret. In Glowing Bear check the checkbox for "use Time-based One-Time Password" and fill in the one time password as you see it in the authenticator app.

Compatibility with WeeChat 2.8 and older

Required for WeeChat <= 2.8

With WeeChat 2.9—released in July 2020—relay client authentication was made more secure and resistant to brute forcing. Glowing Bear uses the most secure authentication method by default. However, to support older versions of WeeChat, this option allows Glowing Bear to still use the old authentication method, sending your password to WeeChat (in plain text if you are not using encryption!). Only enable this if you are using a WeeChat version before 2.9!

By default, WeeChat 2.9 support several authentication methods. Of these, Glowing Bear only uses the most secure one, pbkdf2+sha512. You can check the list of enabled methods to ensure it is in there: /set relay.network.password_hash_algo

Shortcuts

• ALT-n: Toggle nicklist
• ALT-l: Focus on input bar
• ALT-[0-9]: Switch to buffer number N
• ALT-j NN: Switch to buffer number NN
• ALT-↑/↓: Switch to buffer above/below
• ALT-a: Focus on next buffer with activity
• ALT-<: Switch to previous active buffer
• ALT-g: Focus on buffer list filter
• ALT-h: Clear unread counters in every buffer (locally)
• Esc-Esc: Disconnect (double-tap)
• Arrow keys: Navigate history, or navigate quick search buffer results. Pressing ↓ while writing a message pushes it onto the history for later re-use, without sending it.
• Tab: Complete nick
• The following readline/emacs style keybindings can be enabled with a setting: Ctrl-a, Ctrl-e, Ctrl-u, Ctrl-k, Ctrl-w

Pinning buffers

The option "Only show buffers with unread messages" is useful when you have a lot of buffers and can't meaningfully look at all of them at the same time. However, often you have a select few buffers that you use more frequently and would like to have displayed permanently.

To pin a buffer, type /buffer set localvar_set_pinned true. Note: Local variables on buffers are not persisted across WeeChat restarts, so either use script buffer_autoset.py to automatically apply that upon buffer creation or use a trigger if you want automatic repinning when buffers get recreated. To unpin, you can use the same command and set anything other than true.

Helpful trigger to automatically repin a buffer (in this instance, irc.libera.#weechat):

/trigger add autopin signal "buffer_opened" "${buffer[${tg_signal_data}].full_name} =~ irc.libera.#weechat" "" "/command -buffer ${buffer[${tg_signal_data}].full_name} * /buffer set localvar_set_pinned true"

Setting a custom path

The hostname field can be used to set a custom path. Or a URL parameter can be used see section 'URL Parameters'.

To connect to the weechat relay service we connect using a URL. A typical URL consists of 4 parts. {scheme}://{host}:{port}/{path}. The path can be changed by entering the relay's full URL (except the scheme).

• scheme: The scheme must never be input. The scheme is "ws" if TLS isn't used and it is "wss" if TLS is used.
• host: Can be an IPv4, IPv6 or a FQDN. IPv6 addresses must be wrapped in square brackets.
• port: can be specified in the host field or the seperate port field. However if the path is specified in the host field the port must also be specified.
• path: by defautl this is "weechat". In case a proxy is used the path can be changed by entering it in the host field.

Examples of correct input for the host field are:

• 192.168.0.1
• 192.168.0.1:8000
• 192.168.0.1:8000/weechat2
• [2001:db8:85a3::8a2e:370:7334]
• [2001:db8:85a3::8a2e:370:7334]:8000
• [2001:db8:85a3::8a2e:370:7334]:8000/weechat2
• yourhost.yourdomain.com
• yourhost.yourdomain.com:8000
• yourhost.yourdomain.com:8000/weechat2

Incorrect input for the host field:

• ws://192.168.0.1 (do not specify the scheme)
• 192.168.0.1/weechat2 (must specify port when specifying path)
• [2001:db8:85a3::8a2e:370:7334]/weechat2 (must specify port when specifying path)
• yourhost.yourdomain.com/weechat2 (must specify port when specifying path)
• 2001:db8:85a3::8a2e:370:7334 (must wrap IPv6 address in square brackets)
• 2001:db8:85a3::8a2e:370:7334:8000 (must wrap IPv6 address in square brackets)

URL Parameters

Parameters can be passed in the URL to prefill the fields. This can be useful when you have multiple relays and want to use bookmarks to manage them. We do not recommend passing the password in this way as it will be visible in plain text and stored in history/bookmarks but it is possible. Special characters should be URL encoded.

If we want just the path for example: https://glowing-bear.org/#path=weechat2

An example: https://glowing-bear.org/#host=my.domain.com&port=8000&password=hunter2&autoconnect=true

Available parameters:

• host
• port
• path
• password
• autoconnect

You don't need to install anything to use Glowing Bear, it works with any modern browser. Start using it right now at the top of the page! However, there are a few ways to improve integration with your operating system.

Chrome

To install Glowing Bear as an app in Chrome for Android, select Menu - Add to home screen. In the desktop version of Chrome, click Menu - More tools - Create application shortcuts.

Firefox Browser

Firefox used to support apps, but this was removed from Firefox. There's nothing we can do about it. Sorry!

Glowing bear is built by a small group of developers in their free time. As we're always trying to improve it, we would love getting your feedback and help. If that sounds like something you might enjoy, check out our project page on GitHub!

If you're interested in contributing or simply want to say hello, head over to #glowing-bear on libera.chat! We won't bite, promise :)