> ... may not actually know which permissions need to be changed. Sure, the first notice may have come from user flags, and the motivation for those flags is u

> ... may not actually know which permissions need to be changed. Sure, the first notice may have come from user flags, and the motivation for those flags is unknowable. But it's been rejected again, after substantial permissions pruning. Either they know why they rejected the update, in which case they should tell the developer; or they don't know why they rejected the update, in which case they're holding developers hostage to an inscrutable black box. Both scenarios are shitty.