Reply to message

I think they've boxed themselves in code wise on this, or they'd of fixed it years ago. I'm sure at this point it's circulated around their dev teams and they all just kinda threw their hands up.