Remove the EventId field from the few TableMessage variants that have them.
I believe I put them in so that NickMapper would be able to use those fields, but NickMapper can simply look up the EventId for the TableId that all TableMessages are bundled with. Other than a few extra bytes of traffic, those extra fields don't hurt us, but I'd rather NickMapper have a single way of finding the EventId rather than an official and a legacy way of doing it.
ctm
commented
4 months ago
Remove the
EventIdfield from the fewTableMessagevariants that have them.I believe I put them in so that
NickMapperwould be able to use those fields, butNickMappercan simply look up theEventIdfor theTableIdthat allTableMessagesare bundled with. Other than a few extra bytes of traffic, those extra fields don't hurt us, but I'd ratherNickMapperhave a single way of finding theEventIdrather than an official and a legacy way of doing it.