summaryrefslogtreecommitdiff
path: root/terminology.txt
diff options
context:
space:
mode:
authorrebecca <ubq323@ubq323.website>2026-09-20 12:52:21 +0100
committerrebecca <ubq323@ubq323.website>2026-09-20 12:52:21 +0100
commitfa7b29f0f13d167ef0da0cdc49ee3bc7d88ab667 (patch)
tree42421dcefbb449657ec605f7e7b83d3e02db5e40 /terminology.txt
parente640def8de6d4682ad9973ad818dfe2e11c33998 (diff)
update terminology and todo
Diffstat (limited to 'terminology.txt')
-rw-r--r--terminology.txt21
1 files changed, 15 insertions, 6 deletions
diff --git a/terminology.txt b/terminology.txt
index e4157b2..a0c7e16 100644
--- a/terminology.txt
+++ b/terminology.txt
@@ -3,15 +3,24 @@ so i'm kind of figuring this out for myself
anyway
-pylon: a chat server that wilson makes a connection to
+Pylon: an outgoing connection from wilson to some chat server/service
which could be "some irc server", "some xmpp server"
or "discord" (discord is centralized so there's only 1 discord to connect to)
+ (though you COULD have multiple Pylons for discord, if you were crazy)
note that discord's concept of "server" aka "guild" is unrelated to anything
-channel: a particular chatroom on a particular service
- eg "#a on apionet" or "#general in some discord guild"
- in the code, a channel is identified by a combination of a pylon,
- and a string 'channel descriptor', whose format depends on the pylon type
+Channel: a particular chatroom on a particular service
+ eg "#a on apionet irc" or "#general in some discord guild"
+ in the code, a Channel is identified by a combination of a Pylon
+ and a string 'channel descriptor', whose format depends on the Pylon type
for instance xmpp channel descriptors are jids, discord uses numeric ids
-bus: a family of connected channels that messages will be bridged between
+Bus: a family of connected channels that messages will be bridged between
+
+Message: you know what a message is. it has a bunch of fields, which are
+ source_channel: the Channel the message came from
+ maybe rename to source
+ body: the string contents of the message
+ sender: the username (on the source service) of the message's author
+ TODO we need more info than that surely
+