Changeset 427 in code for trunk/downstream.go


Ignore:
Timestamp:
Nov 20, 2020, 10:37:43 AM (5 years ago)
Author:
hubert
Message:

Don't send TAGMSG to upstreams that don't support it

TAGMSG are (in current specs and drafts from IRCv3) only used for
client tags. These are optional information by design (since they are
not distributed to all users), therefore it is preferable to discard
them accordingly to upstream, instead of waiting for all upstreams to
support the capability to advertise it.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/downstream.go

    r423 r427  
    15541554                                return err
    15551555                        }
     1556                        if _, ok := uc.caps["message-tags"]; !ok {
     1557                                continue
     1558                        }
    15561559
    15571560                        uc.SendMessageLabeled(dc.id, &irc.Message{
Note: See TracChangeset for help on using the changeset viewer.