site/wiki/pages/irc.md

86 lines
2.9 KiB
Markdown
Raw Normal View History

2018-06-04 02:18:02 +00:00
---
author: ~ben
published: true
title: irc
2018-06-09 14:47:55 +00:00
description: irc information
2018-06-04 02:18:02 +00:00
category:
- main
---
# [tildeverse irc](https://tilde.chat)
2018-06-04 02:18:02 +00:00
2018-10-25 16:32:54 +00:00
hi teammates!
2018-06-04 02:18:02 +00:00
the tilde.chat irc network is available publicly at irc.tilde.chat:6697 (with ssl) as a round robin of
2019-02-26 17:45:06 +00:00
[available nodes](https://tilde.chat/wiki/?page=servers).
2018-06-19 13:47:50 +00:00
to connect directly to our node, you can use the following addresses:
- localhost port 6667 when at your shell or via ssh port-forwarding
- team.tilde.chat port 6697 with ssl
2018-06-19 13:47:50 +00:00
this is the beginning of the [tilde.chat](https://tilde.chat) irc federation! more info on that site.
2019-07-05 18:56:48 +00:00
## here are some options to connect:
2018-06-13 18:36:51 +00:00
2018-08-30 05:47:13 +00:00
* `weechat` when logged in with ssh
* `irssi`
* [`znc`](https://znc.tilde.team/) - contact ben (via irc or email) to request an account,
then log in with your shell password and configure as needed
2019-02-16 02:35:16 +00:00
* run `webirc` to register your thelounge account for [our webchat](https://irc.tilde.team)
2019-02-26 17:45:06 +00:00
note that thelounge does not authenticate with your shell password.
2018-06-04 02:18:02 +00:00
2019-06-27 13:37:15 +00:00
## weechat relays
weechat introduced [unix socket relays](
https://weechat.org/files/doc/stable/weechat_user.en.html#relay_unix_socket)
in version 2.5 which is a much easier way to offer per-user relay access.
username.ttm.sh/weechat is configured to proxy to the default unix relay socket
2019-06-27 13:37:15 +00:00
location (`~/.weechat/relay_socket`). to get started using it, follow these steps.
2019-06-27 13:39:45 +00:00
1. in weechat:
* `/relay add unix.weechat %h/relay_socket`
* `/set relay.network.password mysupersecretpassword` - don't use this password
of course. note that you might already have this set.
1. at your shell:
* `chmod o+rw ~/.weechat/relay_socket` - note that other members of the team group
are not included in the granted permissions. this allows nginx to connect
to your socket on your behalf
1. in your relay client:
* glowing-bear:
2019-06-27 13:41:13 +00:00
- $user.ttm.sh
2019-06-27 13:39:45 +00:00
- port 443
- your relay password
* weechat-android:
- connection type: websocket (ssl)
- websocket path: weechat
2019-06-27 13:41:13 +00:00
- relay host: $user.ttm.sh
2019-06-27 13:39:45 +00:00
- relay port: 443
- your relay password
- (if you get "Error: Could not connect using WebSocket", check to be sure
~/ and ~/.weechat have at least o+rx permissions so nginx can reach
~/.weechat/relay_socket)
2019-06-27 13:37:15 +00:00
2019-07-05 18:56:48 +00:00
## znc
the system znc authenticates using your shell password (same as with email and
[nextcloud](https://cloud.tilde.team). reach out to an admin on irc or send an
2020-08-29 10:19:21 +00:00
email to [sudoers@tilde.team](mailto:sudoers@tilde.team).
2019-07-05 18:56:48 +00:00
the webadmin interface is available at [znc.tilde.team](https://znc.tilde.team).
client connections are on port 6699 with ssl.
you can add network connections (up to 10) via webadmin or via a direct client
connection.
see the [znc wiki](https://wiki.znc.in/Connecting_to_ZNC) for more information.
2019-06-27 13:37:15 +00:00
---
2018-08-30 05:47:13 +00:00
for more info, see the [tilde.chat wiki](https://tilde.chat/wiki/) for info on bots and other specifics.
2019-06-27 13:37:15 +00:00