Blame
Date:
Sun Jan 29 05:00:28 2023
UTC
Message:
Daily backup
02
2021-12-17
agent=Mozilla/5.0 (X11; OpenBSD amd64; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36
11
2021-12-17
text=[[https://www.bitlbee.org/|Bitlbee]] is a gateway from IRC clients to [[https://wiki.bitlbee.org/|a variety of other protocols]], by acting like a server for IRC clients and a client for those protocols. For example Telegram, Discord, or Slack.%0aThe core of bitlbee itself is written in C.%0a%0a!! Installation and configuration%0aFirst, let's install the package:%0a[@%0a$ doas pkg_add bitlbee-3.6p1-libpurple%0a@]%0a%0aNote : The developers suggest not installing OTR version of bitlbee if you plan to provide a public bitlbee instance. This is because the encryption provided by [[https://otr.cypherpunks.ca/|OTR]] (Off-the-Record) is undermined by the fact that the sysadmin can intercept the messages in plaintext. It gives a false sense of security. Moreover, OTR messaging is often broken when the same account is used with other XMPP clients besides bitlbee.%0a%0aAfter installation edit /etc/bitlbee/bitlbee.conf:%0a%0a[@%0aRunMode = ForkDaemon%0aUser = _bitlbee%0a# Bitlbee will only be bound to localhost on port 8171%0aDaemonInterface = 127.0.0.1%0aDaemonPort = 8171%0aOperPassword = password%0aAllowAccountAdd 1%0aHostName = example.com%0a@]%0a%0aReplace @@password@@ with your own password. We set bitlbee to be bound to localhost on port 8171, which users of [[openbsd/znc|our bouncer]] will be able to connect to, because remote connections of bitlbee server can't support SSL (unlike ZNC).%0a%0aTo start bitlbee:%0a%0a[@%0a$ doas rcctl enable bitlbee%0a$ doas rcctl start bitlbee%0a@]%0a%0a!! Discord Support%0a%0aUse [[https://github.com/sm00th/bitlbee-discord|sm00th's bitlbee-discord]] plugin. Here is a [[https://www.namtsui.com/cgi-bin/cvsweb/ports/net/bitlbee-discord/|convenient port]] provided by namtsui:%0a%0a[@%0a$ cvs -d anoncvs@namtsui.com:/cvs checkout -P ports/net/bitlbee-discord/%0a@]%0a%0a!! Telegram Support%0a%0a$ doas pkg_add telegram-purple%0a%0a!! Matrix Support%0a%0aFrom packages:%0a%0aNote: packaged version of purple-matrix is not working with bitlbee, so we have to install it from source instead.%0a%0a[@%0a$ doas pkg_add purple-matrix%0a@]%0a%0aFrom source:%0a%0a[@%0a$ doas pkg_add olm glib json-glib%0a$ cd ~/%0a$ git clone https://github.com/matrix-org/purple-matrix.git%0a$ cd purple-matrix%0a$ gmake MATRIX_NO_E2E=1%0a$ doas gmake install%0a@]%0a%0a!! RocketChat support%0a[@%0a$ doas pkg_add purple-rocketchat%0a@]%0a%0a!! Mastodon support%0a[@%0a$ doas pkg_add bitlbee-mastodon%0a@]%0a!! Adding accounts%0aconnect with your IRC client to your bitlbee server, this usually will be localhost, then join &bitlbee (not #bitlbee), you can see your buddy list or generally your chats with people in there. by default only 'root' user exist in there. root can used as a configuration panel to bitlbee.%0a%0afirst let's register your account, this will helps to store your settings.%0a[@%0aregister %3cpassword>%0a@]%0athen save it.%0a[@%0asave%0a@]%0a%0anext time you connected into bitlbee, you can login via NickServ or write directly in &bitlbee%0a[@%0aidentify %3cpassword>%0a@]%0a%0acreate your account using following command%0a[@%0aaccount add %3cprotocol> %3cusername> [password] [server]%0a@]%0apassword and server are optional and depends on the protocol, for example, telegram does not require them by default.%0afor protocol, there are two types of protocols, ones are supported by bitlbee and ones are supported by libpurple.%0afor checking bitlbee built-in protocols:%0a[@%0ahelp plugins%0a@]%0a%0aand for checking avaliable protocols supported by libpurple:%0a[@%0ahelp purple%0a@]%0a%0athe @@add@@ command by default gives a id to your account by the protocol name, for example if you add a matrix account it id will be 'matrix', if you had more than one matrix account, they will be named like matrix2, matrix3 and so on.%0a%0ayou can check your accounts using %0a[@%0aaccount list%0a@] %0a%0alet's add a jabber account:%0a[@%0aaccount add jabber myusername@ircnow.org MyVerySecurePassword%0a@]%0aof course, replace myusername@ircnow.org with your JID and @@MyVerySecurePassword@@ with your password (maybe YourVerySecurePassword? :] )%0a%0aanother example for telegram:%0a[@%0aaccount add telegram +11234567%0a@]%0ait will ask for login code later.%0a%0aNote: telegram-purple is known to be buggy and can't connect to telegram sometimes. try to disconnect using following command:%0a%0a[@%0aaccount %3cid> off%0aaccount %3cid> on%0a@]%0a!! chatting%0aafter adding your accounts, you can start chating using msg or query command, for example%0a[@%0a/query my_buddy%0a@]%0awill open a query with my_buddy user. if you want to message your buddy in jabber, do following%0a[@%0a/query JID%0a@]
15
2021-12-17
diff:1620811956:1620811630:minor=1c1%0a%3c [[https://www.bitlbee.org/|Bitlbee]] is a gateway from IRC clients to [[https://wiki.bitlbee.org/|a variety of other protocols]], by acting like a server for IRC clients and a client for those protocols. For example Telegram, Discord, or Slack.%0a---%0a> [[https://www.bitlbee.org/|Bitlbee]] is a gateway from IRC clients to[[https://wiki.bitlbee.org/|a variety of other protocols]], by acting like a server for IRC servers and a client for those protocols. For example, you can use Bitlbee to connect your perfered IRC client to many popular protocols, such as Telegram, Discord, or Slack.%0a91a92%0a> let's manage your account :)%0a
18
2021-12-17
diff:1620811630:1620811148:=1c1%0a%3c [[https://www.bitlbee.org/|Bitlbee]] is a gateway from IRC clients to[[https://wiki.bitlbee.org/|a variety of other protocols]], by acting like a server for IRC servers and a client for those protocols. For example, you can use Bitlbee to connect your perfered IRC client to many popular protocols, such as Telegram, Discord, or Slack.%0a---%0a> [[https://www.bitlbee.org/|Bitlbee]] helps act as an IRC server to connect IRC clients to [[https://wiki.bitlbee.org/|a variety of other protocols]]. For example, you can use Bitlbee to connect your perfered IRC client to many popular protocols, such as Telegram, Discord, or Slack.%0a4d3%0a%3c !! Installation and configuration%0a10,11c9,10%0a%3c Note : The developers suggest not installing OTR version of bitlbee if you plan to provide a public bitlbee instance. This is because the encryption provided by [[https://otr.cypherpunks.ca/|OTR]] (Off-the-Record) is undermined by the fact that the sysadmin can intercept the messages in plaintext. It gives a false sense of security. Moreover, OTR messaging is often broken when the same account is used with other XMPP clients besides bitlbee.%0a%3c %0a---%0a> Note : The developers suggest not installing otr version of bitlbee if you plan to provide a public bitlbee instance. This is because the encryption provided by [[https://otr.cypherpunks.ca/|OTR]] (Off-the-Record) is undermined by the fact that the sysadmin can intercept the messages in plaintext. It gives a false sense of security. Moreover, OTR messaging is often broken when the same account is used with other XMPP clients besides bitlbee.%0a> %0a50,51d48%0a%3c Note: packaged version of purple-matrix is not working with bitlbee, so we have to install it from source instead.%0a%3c %0a59c56,58%0a%3c $ doas pkg_add olm glib json-glib%0a---%0a> $ doas pkg_add olm%0a> $ doas pkg_add glib2%0a> $ doas pkg_add json-glib%0a91a91%0a> %0a110,111c110,112%0a%3c the @@add@@ command by default gives a id to your account by the protocol name, for example if you add a matrix account it id will be 'matrix', if you had more than one matrix account, they will be named like matrix2, matrix3 and so on.%0a%3c %0a---%0a> %0a> the add command by default gives a id to your account by the protocol name, for example if you add a matrix account it id will be 'matrix', if you had more than one matrix account, they will be named like matrix2, matrix3 and so on.%0a> %0a121,122c122,123%0a%3c of course, replace myusername@ircnow.org with your JID and @@MyVerySecurePassword@@ with your password (maybe YourVerySecurePassword? :] )%0a%3c %0a---%0a> of course, replace myusername@ircnow.org with your JID and MyVerySecurePassword with your password (maybe YourVerySecurePassword? :] )%0a> %0a135d135%0a%3c !! chatting%0a
22
2021-12-17
diff:1620811148:1620796477:minor=68c68%0a%3c $ doas pkg_add purple-rocketchat%0a---%0a> # pkg_add purple-rocketchat%0a73c73%0a%3c $ doas pkg_add bitlbee-mastodon%0a---%0a> # pkg_add bitlbee-mastodon%0a124c124%0a%3c another example for telegram:%0a---%0a> another example for telegram telegram:%0a130c130%0a%3c Note: telegram-purple is known to be buggy and can't connect to telegram sometimes. try to disconnect using following command:%0a---%0a> Note: telegram-purple plugin, is known to be buggy and can't connect to telegram sometimes. try to disconnect using following command:%0a
25
2021-12-17
diff:1620796477:1620796119:=40,43d39%0a%3c %0a%3c !! Telegram Support%0a%3c %0a%3c $ doas pkg_add telegram-purple%0a
28
2021-12-17
diff:1620796119:1620795745:=29,30c29,30%0a%3c $ doas rcctl enable bitlbee%0a%3c $ doas rcctl start bitlbee%0a---%0a> # rcctl enable bitlbee%0a> # rcctl start bitlbee%0a40a41%0a> %0a43,44d43%0a%3c From packages:%0a%3c %0a46,59c45%0a%3c $ doas pkg_add purple-matrix%0a%3c @]%0a%3c %0a%3c From source:%0a%3c %0a%3c [@%0a%3c $ doas pkg_add olm%0a%3c $ doas pkg_add glib2%0a%3c $ doas pkg_add json-glib%0a%3c $ cd ~/%0a%3c $ git clone https://github.com/matrix-org/purple-matrix.git%0a%3c $ cd purple-matrix%0a%3c $ gmake MATRIX_NO_E2E=1%0a%3c $ doas gmake install%0a---%0a> # pkg_add purple-matrix%0a
31
2021-12-17
diff:1620795745:1620795650:=24c24%0a%3c Replace @@password@@ with your own password. We set bitlbee to be bound to localhost on port 8171, which users of [[openbsd/znc|our bouncer]] will be able to connect to, because remote connections of bitlbee server can't support SSL (unlike ZNC).%0a---%0a> Replace pass123 with your own password. We set bitlbee to be bound to localhost on port 6668, which users of [[openbsd/znc|our bouncer]] will be able to connect to, because remote connections of bitlbee server can't support SSL (unlike ZNC).%0a
34
2021-12-17
diff:1620795650:1620793280:=1c1%0a%3c [[https://www.bitlbee.org/|Bitlbee]] helps act as an IRC server to connect IRC clients to [[https://wiki.bitlbee.org/|a variety of other protocols]]. For example, you can use Bitlbee to connect your perfered IRC client to many popular protocols, such as Telegram, Discord, or Slack.%0a---%0a> [[https://www.bitlbee.org/|Bitlbee]] helps act as a IRC server to connect IRC clients to [[https://wiki.bitlbee.org/|a variety of other protocols]]. For example, you can use Bitlbee to connect your perfered IRC client to many popular protocols, such as Telegram, Discord, or Slack.%0a6c6%0a%3c $ doas pkg_add bitlbee-3.6p1-libpurple%0a---%0a> # pkg_add bitlbee-3.6p1-libpurple%0a9,10c9,10%0a%3c Note : The developers suggest not installing otr version of bitlbee if you plan to provide a public bitlbee instance. This is because the encryption provided by [[https://otr.cypherpunks.ca/|OTR]] (Off-the-Record) is undermined by the fact that the sysadmin can intercept the messages in plaintext. It gives a false sense of security. Moreover, OTR messaging is often broken when the same account is used with other XMPP clients besides bitlbee.%0a%3c %0a---%0a> Note : The developers suggest not installing otr version of bitlbee, if you plan to provide a public bitlbee instance. This is because the encryption provided by [[https://otr.cypherpunks.ca/|OTR]] (Off-the-Record) is undermined by the fact that the sysadmin can intercept the messages in plaintext. It gives a false sense of security. Moreover, OTR messaging is often broken when the same account is used with other XMPP clients besides bitlbee.%0a> %0a16c16%0a%3c # Bitlbee will only be bound to localhost on port 8171%0a---%0a> # Bitlbee will only be bound to localhost on port 6668(7?)%0a
40
2021-12-17
diff:1620792459:1617938091:=1,3c1,2%0a%3c [[https://www.bitlbee.org/|Bitlbee]] helps act as a IRC server to connect IRC clients to [[https://wiki.bitlbee.org/|a variety of other protocols]]. For example, you can use Bitlbee to connect your perfered IRC client to many popular protocols, such as Telegram, Discord, or Slack.%0a%3c The core of bitlbee itself is written in C.%0a%3c %0a---%0a> [[https://www.bitlbee.org/|Bitlbee]] helps act as a bridge from IRC to [[https://wiki.bitlbee.org/|a variety of other protocols]]. For example, you can use Bitlbee to connect IRC to Telegram, Discord, or Slack. The core of bitlbee itself is written in C.%0a> %0a4a4%0a> %0a6c6%0a%3c # pkg_add bitlbee-3.6p1-libpurple%0a---%0a> $ doas pkg_add bitlbee-3.6p1-libpurple%0a9,12c9,12%0a%3c Note : The developers suggest not installing otr version of bitlbee, if you plan to provide a public bitlbee instance. This is because the encryption provided by [[https://otr.cypherpunks.ca/|OTR]] (Off-the-Record) is undermined by the fact that the sysadmin can intercept the messages in plaintext. It gives a false sense of security. Moreover, OTR messaging is often broken when the same account is used with other XMPP clients besides bitlbee.%0a%3c %0a%3c After installation edit /etc/bitlbee/bitlbee.conf:%0a%3c %0a---%0a> The developers suggest not installing bitlbee-3.6p0-libpurple-otr if you plan to provide a public bitlbee instance. This is because the encryption provided by [[https://otr.cypherpunks.ca/|OTR]] (Off-the-Record) is undermined by the fact that the sysadmin can intercept the messages in plaintext. It gives a false sense of security. Moreover, OTR messaging is often broken when the same account is used with other XMPP clients besides bitlbee.%0a> %0a> Edit /etc/bitlbee/bitlbee.conf:%0a> %0a16c16%0a%3c # Bitlbee will only be bound to localhost on port 6668(7?)%0a---%0a> # Bitlbee will only be bound to localhost on port 6668%0a19c19%0a%3c OperPassword = password%0a---%0a> OperPassword = pass123%0a24,25c24,25%0a%3c Replace pass123 with your own password. We set bitlbee to be bound to localhost on port 6668, which users of [[openbsd/znc|our bouncer]] will be able to connect to, because remote connections of bitlbee server can't support SSL (unlike ZNC).%0a%3c %0a---%0a> Replace pass123 with your own password. We set bitlbee to be bound to localhost on port 6668, which users of [[openbsd/znc|our bouncer]] will be able to connect to.%0a> %0a29,30c29,30%0a%3c # rcctl enable bitlbee%0a%3c # rcctl start bitlbee%0a---%0a> $ doas rcctl enable bitlbee%0a> $ doas rcctl start bitlbee%0a41,43c41,42%0a%3c %0a%3c !! Matrix Support%0a%3c %0a---%0a> !! Telegram Support%0a> %0a45c44%0a%3c # pkg_add purple-matrix%0a---%0a> $ doas pkg_add telegram-purple-1.3.1p2%0a48c47,48%0a%3c !! RocketChat support%0a---%0a> !! Matrix Support%0a> %0a50,124c50,57%0a%3c # pkg_add purple-rocketchat%0a%3c @]%0a%3c %0a%3c !! Mastodon support%0a%3c [@%0a%3c # pkg_add bitlbee-mastodon%0a%3c @]%0a%3c !! Adding accounts%0a%3c connect with your IRC client to your bitlbee server, this usually will be localhost, then join &bitlbee (not #bitlbee), you can see your buddy list or generally your chats with people in there. by default only 'root' user exist in there. root can used as a configuration panel to bitlbee.%0a%3c %0a%3c first let's register your account, this will helps to store your settings.%0a%3c [@%0a%3c register %3cpassword>%0a%3c @]%0a%3c then save it.%0a%3c [@%0a%3c save%0a%3c @]%0a%3c %0a%3c next time you connected into bitlbee, you can login via NickServ or write directly in &bitlbee%0a%3c [@%0a%3c identify %3cpassword>%0a%3c @]%0a%3c %0a%3c let's manage your account :)%0a%3c %0a%3c create your account using following command%0a%3c [@%0a%3c account add %3cprotocol> %3cusername> [password] [server]%0a%3c @]%0a%3c password and server are optional and depends on the protocol, for example, telegram does not require them by default.%0a%3c for protocol, there are two types of protocols, ones are supported by bitlbee and ones are supported by libpurple.%0a%3c for checking bitlbee built-in protocols:%0a%3c [@%0a%3c help plugins%0a%3c @]%0a%3c %0a%3c and for checking avaliable protocols supported by libpurple:%0a%3c [@%0a%3c help purple%0a%3c @]%0a%3c %0a%3c %0a%3c the add command by default gives a id to your account by the protocol name, for example if you add a matrix account it id will be 'matrix', if you had more than one matrix account, they will be named like matrix2, matrix3 and so on.%0a%3c %0a%3c you can check your accounts using %0a%3c [@%0a%3c account list%0a%3c @] %0a%3c %0a%3c let's add a jabber account:%0a%3c [@%0a%3c account add jabber myusername@ircnow.org MyVerySecurePassword%0a%3c @]%0a%3c of course, replace myusername@ircnow.org with your JID and MyVerySecurePassword with your password (maybe YourVerySecurePassword? :] )%0a%3c %0a%3c another example for telegram telegram:%0a%3c [@%0a%3c account add telegram +11234567%0a%3c @]%0a%3c it will ask for login code later.%0a%3c %0a%3c Note: telegram-purple plugin, is known to be buggy and can't connect to telegram sometimes. try to disconnect using following command:%0a%3c %0a%3c [@%0a%3c account %3cid> off%0a%3c account %3cid> on%0a%3c @]%0a%3c after adding your accounts, you can start chating using msg or query command, for example%0a%3c [@%0a%3c /query my_buddy%0a%3c @]%0a%3c will open a query with my_buddy user. if you want to message your buddy in jabber, do following%0a%3c [@%0a%3c /query JID%0a---%0a> $ doas pkg_add olm%0a> $ doas pkg_add glib2%0a> $ doas pkg_add json-glib%0a> $ cd ~/%0a> $ git clone https://github.com/matrix-org/purple-matrix.git%0a> $ cd purple-matrix%0a> $ gmake MATRIX_NO_E2E=1%0a> $ doas gmake install%0a
43
2021-12-17
diff:1617938091:1617937831:=56,57c56%0a%3c $ gmake MATRIX_NO_E2E=1%0a%3c $ doas gmake install%0a---%0a> $ gmake%0a
49
2021-12-17
diff:1617937816:1617937717:=51,56d50%0a%3c $ doas pkg_add glib2%0a%3c $ doas pkg_add json-glib%0a%3c $ cd ~/%0a%3c $ git clone https://github.com/matrix-org/purple-matrix.git%0a%3c $ cd purple-matrix%0a%3c $ make%0a
52
2021-12-17
diff:1617937717:1609857369:=45,50d44%0a%3c @]%0a%3c %0a%3c !! Matrix Support%0a%3c %0a%3c [@%0a%3c $ doas pkg_add olm%0a
55
2021-12-17
diff:1609857369:1603872636:=6c6%0a%3c $ doas pkg_add bitlbee-3.6p1-libpurple%0a---%0a> $ doas pkg_add bitlbee-3.6p0-libpurple%0a
58
2021-12-17
diff:1603872636:1597743447:=18c18%0a%3c DaemonPort = 8171%0a---%0a> DaemonPort = 6668%0a
61
2021-12-17
diff:1597743447:1597743406:=1c1%0a%3c [[https://www.bitlbee.org/|Bitlbee]] helps act as a bridge from IRC to [[https://wiki.bitlbee.org/|a variety of other protocols]]. For example, you can use Bitlbee to connect IRC to Telegram, Discord, or Slack. The core of bitlbee itself is written in C.%0a---%0a> [[https://www.bitlbee.org/|Bitlbee]] helps act as a bridge from IRC to [[a variety of other protocols|https://wiki.bitlbee.org/]]. For example, you can use Bitlbee to connect IRC to Telegram, Discord, or Slack. The core of bitlbee itself is written in C.%0a
64
2021-12-17
diff:1597743406:1597743406:=1,45d0%0a%3c [[https://www.bitlbee.org/|Bitlbee]] helps act as a bridge from IRC to [[a variety of other protocols|https://wiki.bitlbee.org/]]. For example, you can use Bitlbee to connect IRC to Telegram, Discord, or Slack. The core of bitlbee itself is written in C.%0a%3c %0a%3c First, let's install the package:%0a%3c %0a%3c [@%0a%3c $ doas pkg_add bitlbee-3.6p0-libpurple%0a%3c @]%0a%3c %0a%3c The developers suggest not installing bitlbee-3.6p0-libpurple-otr if you plan to provide a public bitlbee instance. This is because the encryption provided by [[https://otr.cypherpunks.ca/|OTR]] (Off-the-Record) is undermined by the fact that the sysadmin can intercept the messages in plaintext. It gives a false sense of security. Moreover, OTR messaging is often broken when the same account is used with other XMPP clients besides bitlbee.%0a%3c %0a%3c Edit /etc/bitlbee/bitlbee.conf:%0a%3c %0a%3c [@%0a%3c RunMode = ForkDaemon%0a%3c User = _bitlbee%0a%3c # Bitlbee will only be bound to localhost on port 6668%0a%3c DaemonInterface = 127.0.0.1%0a%3c DaemonPort = 6668%0a%3c OperPassword = pass123%0a%3c AllowAccountAdd 1%0a%3c HostName = example.com%0a%3c @]%0a%3c %0a%3c Replace pass123 with your own password. We set bitlbee to be bound to localhost on port 6668, which users of [[openbsd/znc|our bouncer]] will be able to connect to.%0a%3c %0a%3c To start bitlbee:%0a%3c %0a%3c [@%0a%3c $ doas rcctl enable bitlbee%0a%3c $ doas rcctl start bitlbee%0a%3c @]%0a%3c %0a%3c !! Discord Support%0a%3c %0a%3c Use [[https://github.com/sm00th/bitlbee-discord|sm00th's bitlbee-discord]] plugin. Here is a [[https://www.namtsui.com/cgi-bin/cvsweb/ports/net/bitlbee-discord/|convenient port]] provided by namtsui:%0a%3c %0a%3c [@%0a%3c $ cvs -d anoncvs@namtsui.com:/cvs checkout -P ports/net/bitlbee-discord/%0a%3c @]%0a%3c %0a%3c !! Telegram Support%0a%3c %0a%3c [@%0a%3c $ doas pkg_add telegram-purple-1.3.1p2%0a%3c @]%0a\ No newline at end of file%0a