But can we push it as a maintenance update for 11.3? That's what is really needed here. I'm a bit afraid that it's a new upstream version, from a different branch...
It adds new dependencies not in 11.3 so no, we can't.
The merge that upstream did has two issues:
a) The patch doesn't just apply to Twitter/OAuth, for some reason some other work was done on a branch that was meant to be solely for that work. b) It doesn't apply to the 11.3 package anyway, rendering the whole thing moot.
At the moment, work pressures mean I simply don't have the time to unpick a convoluted patch and manually beat it into shape for the 11.3 packages. If someone else will have a try, I can certainly offer advice and/or testing of packages before they're pushed.