matrix-appservice-irc
matrix-appservice-irc copied to clipboard
matrix-org
Bridge Matrix threads
This treats each thread reply as an old message reply, as in: always quotes the previous message from a thread, regardless of how long ago it happened – with the possibility of multiple threads going on concurrently, short replies just turn into a mess.
It is quite noisy, but I think it's the best we can do to preserve the context. Replies from IRC won't work, obviously :(
I suppose the jury is out on whether it's useful to have this
This is what it goes down to, yeah. If it'll end up the giving the false impression that we can transparently bridge threads, and yet we can't bridge replies from IRC to Matrix it'll just become a mess. Perhaps it'd make more sense to do channels-as-threads on the IRC side?
It is quite noisy, but I think it's the best we can do to preserve the context. Replies from IRC won't work, obviously :(
Wouldn't it be best to just support IRCv3 reply client tag as per https://github.com/matrix-org/matrix-appservice-irc/issues/1414?
It is quite noisy, but I think it's the best we can do to preserve the context. Replies from IRC won't work, obviously :(
Wouldn't it be best to just support IRCv3 reply client tag as per #1414?
I realise it's a bit chicken and egg, but atm only IRCCloud supports it...so we're unlikely to do the work to support it until Server/Client impls catch up.
It is quite noisy, but I think it's the best we can do to preserve the context. Replies from IRC won't work, obviously :(
Wouldn't it be best to just support IRCv3 reply client tag as per #1414?
I realise it's a bit chicken and egg, but atm only IRCCloud supports it...so we're unlikely to do the work to support it until Server/Client impls catch up.
It's also supported by Limnoria and Palaver has expressed interest towards implementing it. On servers at least Ergo has it and I would think InspIRCd to at least have it planned if not implemented already.
until Server/Client impls catch up.
Servers don't need to implement it. It's a client-tag, and servers just pass all client tags without explicitly implementing them. (Though UnrealIRCd has a whitelist, but it already has the tag on its whitelist.)
until Server/Client impls catch up.
Servers don't need to implement it. It's a client-tag, and servers just pass all client tags without explicitly implementing them. (Though UnrealIRCd has a whitelist, but it already has the tag on its whitelist.)
Mm, though client-tags is still lagging behind a bit as well (https://github.com/solanum-ircd/solanum/issues/167). Granted, we could probably implement given enough servers do support it.
I am under impresson that Solanum is going to get a rewrite at some point and is not going to implement a lot of IRCv3 features before it happens, so I wouldn't include them in considerations how widely supported something is.