Differences

This shows you the differences between two versions of the page.

--- chat [2022/07/22 11:28] – irc renamed to chat andi
+++ chat [2026/04/19 17:05] (current) – [VOC Chat] adjust last paragraph to new chat policy niklasnet
@@ Line 1: / Line 1: @@
-= VOC IRC
+= VOC Chat
+Neben den (monatlichen) Mumble-Treffen ist Matrix/IRC unser Haupt-Kommunikationsmedium, allerdings benutzen wir das teilweise stark asynchron: Das heißt, die meisten von uns nutzen einen [[https://matrix.org|Matrix-Client]] wie FluffyChat oder Element oder lassen den IRC Client auf ihrem Server laufen.
+Der Matrix-Raum [[https://matrix.to/#/#public:c3voc.de|#public:c3voc.de]] (identisch mit dem IRC-Channel `#voc-lounge` im Hackint) ist unser virtuelles Wohnzimmer. Wenn Du es betrittst, dann ist es nett, kurz ein "Hallo" in die Runde zu werfen.
+Wenn Du nach 5 Minuten wieder rausgehst, weil Du meinst, dass dort nicht los sei, dann warst Du zu ungeduldig. Wir sind zwar oft den ganzen Tag (und natürlich auch die Nacht) aktiv, aber beide Chatwege nehmen nicht 100% unserer Rechenleistung ein. Wir sind meist nur nebenbei in den Chats, hauptsächlich gehen wir irgendeiner mehr-oder-weniger sinnvollen Beschäftigung nach, Gerüchten zufolge sollen einige sogar versuchen, Geld zu verdienen.
+== Matrix
+We are currently using the federated Matrix Network in parallel to IRC communication, if you are "member" of our organisation ask the admins to invite you to the VOC Matrix Space.
+If you need to create a new account for the Matrix network, please use one of the many homeservers available, e.g. [[https://fairydust.space|fairydust.space]]. Account registration is integrated into the clients, e.g. [[https://fluffychat.im|FluffyChat]] or [[https://chat.fairydust.space|Element]]. We recommend to start with a native client on your mobile device, and then add a web/desktop client to your setup.
 == Channels
-There are several IRC-Channels that we're using during and between VOC-Events to organize ourself:
+There are several IRC/Matrix channels that we're using during and between events to organise ourselves:
-  * #voc @HackInt
+- [[https://matrix.to/#/#public:c3voc.de|#public:c3voc.de]] aka `#voc-lounge` aka !oQDxiYzvFgfYQvnTHS:hackint.org
-    * use case: VOC serious business. Invite yourself via /msg chanserv invite #voc or others using /invite nickname #voc
+  - use case: Winkekatzen Bar. Feel free to stay slightly on topic. Here we talk about video streaming, recording and publishing.
-    * access limitation: invite only, invite yourself if you are in the group !voc
+  - access limitation: none
-  * #voc-wok @HackInt
+- `#voc:matrix.org`
-    * use case:  SPAM SPAM SPAM, our twitterbot viri lives here, high traffic if event is 'in progress'
+  - use case: 2nd/3rd Level Support during events, on topic discussions
-    * access limitation: none
+  - access limitation: members of the VOC matrix space
-  * #voc-lounge
+- `#voc-<event>` @matrix
-    * use case:   Winkekatzen Bar. Feel free to stay slightly on topic. Here we talk about video streaming, recording and publishing.
+  - use case: 2nd Level Support during specific event
-    * access limitation: none
+  - access limitation: event organisers, event voc members, +members of the VOC matrix space
-  * #voc-mixer
+- `#voc-mixer`
-    * use case: mixer-channel during events
+  - use case: mixer-channel during events
-    * access limitation: none
+  - access limitation: none
+== IRC
 === Grant channel access
 New user has to register with nickserv https://hackint.org/services#NickServ
-    - ''/msg NickServ register <password> <email>''
-    - ''/msg NickServ identify <password>''
+ - `/msg NickServ register <password> <email>`
+ - `/msg NickServ identify <password>`
 Groupadmin has to invite the user to the group and give rights to invite https://hackint.org/services#GroupServ
-    - ''/msg GroupServ invite !voc <nickname>''
-    - ''/msg ChanServ flags #voc <nickname> +i''
+- `/msg GroupServ invite !voc <nickname>`
+- `/msg ChanServ flags #voc <nickname> +i`
 New user has to join the group
-    * ''/msg GroupServ join !voc''
+- `/msg GroupServ join !voc`
 New user has to tell ChanServ to be invited (add to autocmd)
-    * ''/msg ChanServ invite #voc''
+- `/msg ChanServ invite #voc`
@@ Line 38: / Line 58: @@
-== Usage of IRCBots
+== Usage of IRC bots
-* viri (mng)
+* viri (matrix)
-* mixerwatch (mng)
+* gitbot (forgejo)
-* gitbot (mng)
+* mqttwatchdog (mqtt)
-* twitterbot (mng)
-* mqttwatchdog (mng)
-* reminder (mng)
 * tracker-monitor (tracker)
 * fahrplan-monitor (tracker) started with autorun
@@ Line 52: / Line 69: @@
 === viri
-==== Reminder:
-  * [Eingabe von Alice] <code>viri: reminder, 23:42, Testnachricht hier eingeben</code>
-  * [Antwort des Bots] <code>13:37:23< viri> INFO reminder/{yournick}: Added reminder 'Testnachricht hier eingeben' around '30-12-2015 23:42'</code>
-  * [Reminder des Bots] <code>19:44:59< viri> WARN reminder/{yournick}: Testnachricht hier eingeben</code>
 ==== Silencing
@@ Line 76: / Line 88: @@
 < florolf> viri: unsilence system/disk/encoder-danimo
 < viri   > unsilenced 'system/disk/encoder-danimo'
-</code>
-or
-<code>
-< florolf> viri: unsilence all
-< viri   > removed all silencings
 </code>
@@ Line 104: / Line 109: @@
 <code>
-< meise> viri: watchdog, list
+< meise> viri: watchdog list
 < viri> INFO watchdog: currently watching hosts:
 </code>