#30717 closed enhancement (wontfix)

Consider exempting Matrix.org users from OFTC registered nick requirement

Reported by: JeremyRand Owned by: alison
Priority: Medium Milestone:
Component: Internal Services Version:
Severity: Normal Keywords:
Cc: ggus Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


The Matrix.org relay is the most straightforward way to access OFTC over Tor. Users who are accessing OFTC via the Matrix.org relay are not considered by OFTC to be "registered" by default, since their registration is with Matrix.org infrastructure rather than OFTC infrastructure. This produces a problem because Tor's OFTC channels are configured to disallow any user from joining if they are not registered on OFTC infrastructure. (I tested #tor-dev; I assume the others are similar.)

Usually, this kind of policy is intended to mitigate spam attacks. However, historically none of the spam attacks against IRC networks have been routed via Matrix.org infrastructure. This may be because Matrix.org has its own rate-limiting mechanisms for account registration (e.g. a reCAPTCHA test for each new registration), and it may also be because Matrix.org is new enough that spammers haven't paid attention to it. In any event, I think it's highly unlikely that you'll see spam from Matrix.org infrastructure if you permit Matrix.org users to access your OFTC channels.

Documentation on exempting Matrix.org users from the registered nick requirement is at https://github.com/matrix-org/matrix-appservice-irc/wiki/End-user-FAQ#user-content-i-am-a-chanop-and-have-a-spam-problem-how-can-i-fix-it-without-affecting-matrix-users . Any chance you could do this?

PS: I'm not sure if Community is the right component for this ticket; feel free to reassign to another component if you like.

Child Tickets

Change History (4)

comment:1 Changed 12 months ago by teor

Component: Community- Select a component

We don't have a component for IRC changes.

I've asked about this ticket on the #tor-dev IRC channel and tor-dev@ mailing list.

comment:2 Changed 12 months ago by arma

One way to move this forward would be to figure out how to do this on oftc in particular.

(The docs you point to seem pretty generic, and not straightforward to apply to our channels on oftc.)

comment:3 Changed 11 months ago by teor

Component: - Select a componentInternal Services

I'm really not sure which component this belongs in.

comment:4 Changed 10 months ago by anarcat

Resolution: wontfix
Status: newclosed

I don't think it's technically feasible to accomplish this. The IRC channels are restricted to registered users using a CMODE (channel mode) like +R, which says:

R - client may join only when registered and identified to NickServ

There's no way to do exceptions to this based on host masks, which is how, I assume, we'd detect people coming from Matrix, but even that is unclear to me.

So while I understand where you're coming from, I don't think this is actually feasible.

One thing that *could* work slightly better is setting the channels +M (client may speak only when registered and identified to NickServ) and then maybe +v (voiced) would allow operators to apply exceptions for certain users.

But then we need operators to pay attention to joins, and that's unlikely to work...

Anyways, sorry about this, but I don't know how else to fix this. Note that it's possible for users to register with OFTC from Matrix. It's a little inconvenient, but it's possible, so that limitation can be worked around by users themselves.

Note: See TracTickets for help on using tickets.