Twitter is half of the problem here. Once you request read access and a user approves it, there is no way under the same application then go back and get write

Twitter is half of the problem here. Once you request read access and a user approves it, there is no way under the same application then go back and get write access. Ideally every app would start with read and then only upgrade to write when needed but Twitter won't allow it. There are multiple bugs in their api issue tracker and they don't seem to care. The only way to get around it is to have two applications, a read and a read-write which actually is more difficult and why bother working around Twitters short comings when most users don't care? I know this wasn't only about Twitter, but this is an issue I've had myself and it's incredibly annoying.