Open SoniEx2 opened 4 years ago
This looks to be KVIRC specific rather than a standard feature, so I'm reluctant to support it.
KVIrc doesn't even support this actually. it's for ops and hand-crafted CTCP messages and stuff instead.
Afaik KVIrc does support CTCP. I use it to transfer my Avatar to other KVIrc users on the channel.
But yes it is something KVIrc specific.
Edit: I have to correct myself. I think IRC Cloud integrated this as well. At least I read it somewhere. It shouldn't be too hard to implement this and would give some users a bit more avatar comfort ;-)
KVIrc uses hidden color codes tho. and it doesn't support per-channel/room avatar. I want something that's more useful for ops than KVIrc users. there would be no automatic CTCPs being sent anywhere with my proposal.
this is just a way to query additional metadata on matrix users. metadata which is already exposed on the matrix side. (ideally we'd have CTCPs for all the relevant metadata we can bridge over. and it'd be one-way only (bridge to IRC) so the bridge isn't constantly spamming IRC users with CTCPs.)
Edit: I have to correct myself. I think IRC Cloud integrated this as well. At least I read it somewhere. It shouldn't be too hard to implement this and would give some users a bit more avatar comfort ;-)
Irc Cloud use the IRCv3.2 METADATA command which is slightly more standardized but supporting v3 is a bit outside of scope atm, since most irc servers do not.
I could argue all day about ircv3 metadata being unsuitable for 99.9% of use-cases, but I think the most relevant point here is that it doesn't and cannot support per-room avatars. (I suggest taking a look at the issues in one of my repos for other real-life use-cases that are incompatible with it.)
I think this is unlikely to be something to be taken up by myself as a thing to work on as we don't have a lot of demand for this from users, and the avatar space is fragmented between CTCPs and IRCV3).
That being said, I'm open to reviewing PRs that will add support for this.
There should be a CTCP AVATAR that sends out the HTTPS link of the Matrix avatar.
And for room-specific avatars:
(
>>> CTCP
indicates an incoming CTCP request,<<< NCTCP
indicates an outgoing CTCP response.)This is particularly useful for moderating matrix-bridged rooms from the IRC side.