Skip to content

skeleton enforcement for channels? #581

@slingamn

Description

@slingamn

We don't enforce the uniqueness of channel name skeletons, should we?

I haven't considered this as much of a priority because INVITE and LIST seem like the only contexts in which one might spoof a channel name (in contrast to which, nick spoofing is a potential issue whenever you're receiving a PRIVMSG).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions