The rationale for disabling the feature is that only RAX is using it and they enforce quotas separately?
I don't like assuming RAX is the only one using it. We have enough users now that it's impossible to predict what people may be doing. If we publish this issue, recommend disabling the extension and there are people who are using it ... then we've nicely screwed them.
How about we cook up the quotas patch and see how invasive it is? It might be backportable with manageable regression risk
The rationale for disabling the feature is that only RAX is using it and they enforce quotas separately?
I don't like assuming RAX is the only one using it. We have enough users now that it's impossible to predict what people may be doing. If we publish this issue, recommend disabling the extension and there are people who are using it ... then we've nicely screwed them.
How about we cook up the quotas patch and see how invasive it is? It might be backportable with manageable regression risk