matterbridge_wz.toml

###################################################################
#IRC section
###################################################################
#REQUIRED to start IRC section
[irc]

#You can configure multiple servers "[irc.name]" or "[irc.name2]"
#REQUIRED
[irc.freenode]
#irc server to connect to. 
#REQUIRED
Server="irc.freenode.net:6697"

#Password for irc server (if necessary)
#OPTIONAL (default "")
#Password=""

#Enable to use TLS connection to your irc server. 
#OPTIONAL (default false)
UseTLS=true

#Enable SASL (PLAIN) authentication. (freenode requires this from eg AWS hosts)
#It uses NickServNick and NickServPassword as login and password
#OPTIONAL (default false)
UseSASL=false

#Enable to not verify the certificate on your irc server. 
#e.g. when using selfsigned certificates
#OPTIONAL (default false)
SkipTLSVerify=true

#Your nick on irc. 
#REQUIRED
Nick="WZ_Bot"

#If you registered your bot with a service like Nickserv on freenode. 
#Also being used when UseSASL=true
#OPTIONAL
NickServNick="NickServ"
NickServPassword="{{ irc_pass_wz }}"

#Flood control
#Delay in milliseconds between each message send to the IRC server
#OPTIONAL (default 1300)
MessageDelay=1300

#Maximum amount of messages to hold in queue. If queue is full 
#messages will be dropped. 
#<clipped> will be add to the message that fills the queue.
#OPTIONAL (default 30)
MessageQueue=30

#Nicks you want to ignore. 
#Messages from those users will not be sent to other bridges.

#OPTIONAL
#IgnoreNicks="someuser"

#Enable to show users joins/parts from other bridges (only from irc-bridge at the moment)
#OPTIONAL (default false)
ShowJoinPart=false




###################################################################
#telegram section
###################################################################
[telegram]

#You can configure multiple servers "[telegram.name]" or "[telegram.name2]"

## In Telegram muss ein Bot erstellt werden, was über den Kontakt @BotFather in Telegram geht.
## Bot erstellen (Funktion /newbot), das API Token wird unten verwendet.
## Die Privacy Funktion des Bots auss auf "DISAABLED" gettellt werden (Funktion: /setprivacy) 
## Anschließend muss der Bot in die entsprechende Gruppe eingefügt und dort als Admin eingerichtet werden. 

#REQUIRED
[telegram.bot]
#Token to connect with telegram API
#Bot @warpzonebot
#See https://core.telegram.org/bots#6-botfather and https://www.linkedin.com/pulse/telegram-bots-beginners-marco-frau
#REQUIRED
Token="{{ telegram_token_wz }}"

#Nicks you want to ignore. 
#Messages from those users will not be sent to other bridges.

#OPTIONAL
#IgnoreNicks="Someuser"

#Enable to show users joins/parts from other bridges (only from irc-bridge at the moment)
#OPTIONAL (default false)
ShowJoinPart=false

###################################################################
#matrix section
###################################################################
[matrix]
#You can configure multiple servers "[matrix.name]" or "[matrix.name2]"
#In this example we use [matrix.neo]
#REQUIRED

[matrix.warpzone]
#Server is your homeserver (eg https://matrix.org)
#REQUIRED
Server="{{ matrix.public_url }}"

#login/pass of your bot. 
#Use a dedicated user for this and not your own! 
#Messages sent from this user will not be relayed to avoid loops.
#REQUIRED 
Login="wzbot"
Password="{{ matrix_pass_wzbot }}"

#Whether to send the homeserver suffix. eg ":matrix.org" in @username:matrix.org
#to other bridges, or only send "username".(true only sends username)
#OPTIONAL (default false)
NoHomeServerSuffix=false

## RELOADABLE SETTINGS
## Settings below can be reloaded by editing the file

#Whether to prefix messages from other bridges to matrix with the sender's nick. 
#Useful if username overrides for incoming webhooks isn't enabled on the 
#matrix server. If you set PrefixMessagesWithNick to true, each message 
#from bridge to matrix will by default be prefixed by the RemoteNickFormat setting. i
#OPTIONAL (default false)
PrefixMessagesWithNick=true


#RemoteNickFormat defines how remote users appear on this bridge 
#See [general] config section for default options
RemoteNickFormat="[{PROTOCOL}] <{NICK}> "

#Enable to show users joins/parts from other bridges 
#Currently works for messages from the following bridges: irc, mattermost, slack, discord
#OPTIONAL (default false)
ShowJoinPart=false

#StripNick only allows alphanumerical nicks. See https://github.com/42wim/matterbridge/issues/285
#It will strip other characters from the nick
#OPTIONAL (default false)
StripNick=false


###################################################################
#General configuration
###################################################################
#Settings here override specific settings for each protocol
[general]
#RemoteNickFormat defines how remote users appear on this bridge 
#The string "{NICK}" (case sensitive) will be replaced by the actual nick / username.
#The string "{BRIDGE}" (case sensitive) will be replaced by the sending bridge
#The string "{PROTOCOL}" (case sensitive) will be replaced by the protocol used by the bridge
#OPTIONAL (default empty)
RemoteNickFormat="[{PROTOCOL}] <{NICK}> "

# Media Download, see https://github.com/42wim/matterbridge/wiki/Mediaserver-setup-[advanced]#use-local-download
MediaDownloadPath="/media/"
MediaServerDownload="https://www.warpzone.ms/matterbridge/"

###################################################################
#Gateway configuration
###################################################################

#You can specify multiple gateways using [[gateway]]
#Each gateway has a [[gateway.in]] and a [[gateway.out]]
#[[gateway.in]] specifies the account and channels we will receive messages from.
#[[gateway.out]] specifies the account and channels we will send the messages
#from [[gateway.in]] to.
#
#Most of the time [[gateway.in]] and [[gateway.out]] are the same if you 
#want bidirectional bridging. You can then use [[gateway.inout]]

[[gateway]]
#OPTIONAL (not used for now)
name="gateway1"
#Enable enables this gateway
##OPTIONAL (default false)
enable=true

    [[gateway.inout]]
    ## Der IRC Channel der Wapzone 
    account="irc.freenode"
    channel="#warpzone"

    [[gateway.inout]]
    ## Telegramm Gruppe @warpzone (Spamfreie Warpzone Gruppe)
    ## 8.8.2017 von void deaaktiviert das das Spammen im Telegram Leute genervt hat
    ## 24.4.2018 für die spamfreie warpzone Gruppe wieder aktiviert (Beschluss Plenum)
    ## Vorgehen um Guppen-ID zu bekommen:
    ## - Bot in Gruppe einfügen
    ## - Chatnachricht erstellen  
    ## - https://api.telegram.org/<API Token>/getUpdates ausrufen, die ID findet sich in der Eigenschaft "message.chat.id"
    account="telegram.bot"
    channel="-272574265" 

    [[gateway.inout]]
    ## Raum auf dem Warpzone Matrix Server 
    account="matrix.warpzone"
    channel="#warpzone-bridge:{{ matrix.domain }}"