1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
|
== One Client for Everything
== Table of Contents
[arabic]
. link:#foreword[Foreword]
. link:#two-ways-of-solving-this[Two ways of solving this]
. link:#the-web-app-way[The web app way]
. link:#gui-or-terminal-client[gui or terminal client]
. link:#matrix-or-irc[Matrix or IRC]
=== Foreword
First let’s talk about the problem we’re trying to solve here. I want to
have a unified interface into all the communication forms that I use. I
can’t be bothered to have different clients open all the time. I want to
have one client that takes care of all things mostly well.
=== Two ways of solving this
There is generally two ways one can try to solve this. Number one is to
just use a browser. Almost all forms of comm nowadays have a web client
so basically one way of solving our problem is to a dedicated browser
that has all the clients open. Mind you, there are even specialized and
more lightweight browser offerings specifically geared towards this
use-case but still this option is not ideal in terms of resources and
the interface you’re getting is not really unified.
==== The web app way
An example that comes to mind for this sort of solution is `rambox`
though they are no longer offering a FOSS solution. I’m just mentioning
them as an example of what’s being offered out there as a ready-to-use
solution.
Although this way of doing things is very resource-intensive, this is
the *complete* way of doing things. What I mean by that is that by using
the official web apps, you will not be compromising on any features that
the clients offer since you will be using the official clients.
==== gui or terminal client
The second way of going about and solving this is to pick a very good
client that supports a protocol with a lot of bridges and then bridge
everything through to the app of that one protocol. Currently there are
only three protocols that have enough facilities for bridging to make
this feasible. IRC, Matrix and XMPP. I’m adding XMPP for the sake of
completion but in terms of practicality XMPP doesn’t have nearly as many
bridges as IRC and Matrix.
So this basically narrows down our choice to either IRC or Matrix. Now
lets look at the clients that are available for these two protocols.
==== Matrix or IRC
The last requirement on my side is that i would rather use a unified
terminal keyboard-based client than a web application client. That being
said, i definitely expect to use a web client since using a terminal
client on a smart phone is pretty much just pain. A lot of pain.
Unfortunately at the time of writing this post, Matrix has no terminal
client that comes close to either https://github.com/irssi/irssi[irssi]
or https://github.com/weechat/weechat[weechat], both terminal clients
originally only supporting IRC but later advertising themselves as
multi-chat clients. Also as an added bonus, starting from the next irssi
release which should be irssi v1.5 one can elect not to build the IRC
module at all while building irssi.
Matrix and IRC both have a rich ecosystem of bridges. Matrix has a
growing fan base which means more and more bridges or tools with similar
functionality will be releases for it. Contrast that with IRC where that
number seems to be smaller than Matrix but still is very much alive and
well.
=== https://github.com/bitlbee/bitlbee[bitlbee-libpurple]
....
it'll be bitlbee
....
bitlbee is a bridge software for IRC. The distinguishing feature for
bitlbee is that the way it bridges other protocols to IRC is by
masquerading as an ircd. You could also use libpurple as the backend for
bitlbee (https://wiki.bitlbee.org/HowtoPurple[link]). libpurple has an
origin story similar to libreadline. Basically it used to live inside
pidgin, but later on it was turned into a library so that other
applications could use it as well.
List of protocols supported by libpurple:
....
aim
bitlbee-discord
bitlbee-mastodon
bonjour
eionrobb-icyque
eionrobb-mattermost
eionrobb-rocketchat
facebook
gg
hangouts
hehoe-signald
hehoe-whatsmeow
icq
irc
jabber
matrix
meanwhile
novell
otr
simple
sipe
skypeweb
slack
steam
telegram-tdlib
zephyr
....
=== https://github.com/42wim/matterbridge[matterbridge]
matterbridge is an everything-to-everything bridge.
Please keep in mind that with matterbridge, you don’t get the full
functionality of a protocol as in you get no private messages and such.
You get the ability to join public chat rooms or whatever they call it
in that protocol.
=== bridge ircds
==== https://github.com/42wim/matterircd[matterircd]
a mattermost bridge that emulates an ircd as the name implies.
==== https://github.com/progval/matrix2051[matrix2051]
another bridge that emulates an ircd, but for matrix.
==== https://github.com/adsr/irslackd[irslackd]
a bridge to slack that emulates an ircd.
==== docker compose
https://github.com/ezkrg/docker-bitlbee-libpurple[Here]’s the original
Dockerfile. You can find mine
https://github.com/terminaldweller/docker-bitlbee-libpurple[here]. And
here’s the docker compose file I use that goes with that:
[source,yaml]
----
version: "3.8"
services:
bitlbee:
image: devi_bitlbee
deploy:
resources:
limits:
memory: 384M
logging:
driver: "json-file"
options:
max-size: "100m"
networks:
- bitlbeenet
ports:
- "127.0.0.1:8667:6667"
- "172.17.0.1:8667:6667"
restart: unless-stopped
user: "bitlbee:bitlbee"
command:
[
"/usr/sbin/bitlbee",
"-F",
"-n",
"-u",
"bitlbee",
"-c",
"/var/lib/bitlbee/bitlbee.conf",
"-d",
"/var/lib/bitlbee",
]
dns:
- 9.9.9.9
volumes:
- ./conf/bitlbee.conf:/var/lib/bitlbee/bitlbee.conf:ro
- userdata:/var/lib/bitlbee
- /home/devi/.cache/docker-bitlbee/signald/run:/var/run/signald
- /etc/ssl/certs:/etc/ssl/certs:ro
signald:
image: signald/signald:stable
deploy:
resources:
limits:
memory: 384M
logging:
driver: "json-file"
options:
max-size: "100m"
networks:
- signalnet
ports:
- "127.0.0.1:7775:7775"
- "172.17.0.1:7775:7775"
restart: unless-stopped
dns:
- 9.9.9.9
volumes:
- /home/devi/.cache/docker-bitlbee/signald/run:/signald
- /etc/ssl/certs:/etc/ssl/certs:ro
environment:
- SIGNALD_ENABLE_METRICS=false
- SIGNALD_HTTP_LOGGING=true
- SIGNALD_VERBOSE_LOGGING=true
- SIGNALD_METRICS_PORT=7775
- SIGNALD_LOG_DB_TRANSACTIONS=true
matterircd:
image: 42wim/matterircd:latest
deploy:
resources:
limits:
memory: 384M
logging:
driver: "json-file"
options:
max-size: "100m"
networks:
- matterircdnet
ports:
- "127.0.0.1:7667:7667"
- "172.17.0.1:7667:7667"
dns:
- 9.9.9.9
restart: unless-stopped
command: ["--conf", "/matterircd.toml"]
volumes:
- ./matterircd.toml:/matterircd.toml:ro
networks:
bitlbeenet:
signalnet:
matterircdnet:
volumes:
userdata:
matterircddb:
----
timestamp:1699398469
version:0.1.0
https://blog.terminaldweller.com/rss/feed
https://raw.githubusercontent.com/terminaldweller/blog/main/mds/oneclientforeverything.md
|
