Skip to content

Conversation

dwfreed
Copy link
Member

@dwfreed dwfreed commented Dec 20, 2020

I did look through most of these to make sure they were sane, but a second set of eyes would be good. I didn't touch most snotes for bans (K/D/X lines, RESVs) because I figured we could do those when we rework ban propagation and elimination of clusters and such.

@edk0
Copy link
Contributor

edk0 commented Dec 20, 2020

I'm not thrilled about making things netwide snotes that are propagated globally anyway.

@dwfreed
Copy link
Member Author

dwfreed commented Dec 20, 2020

Connect needs to be netwide, because only the local server knows the connection class; the others that are propagated that previously had a snote extension I'd be open to integrating into the appropriate place. But sno_globaloper was a hack (checks for umode +o), and sno_globalkline is the hackiest of hacks (checks for specific quit messages), so those definitely need to go.

@dwfreed
Copy link
Member Author

dwfreed commented Dec 20, 2020

(The sasl_abort1 test failures are because the connect snotes are now in the server sendq)

@dwfreed dwfreed added this to the OFTC Feature Parity milestone Feb 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants