Sending Tweets gives a 401 (in some cases)

[Half-Shot]

I've had multiple users confirm to me that sending tweets (from a valid authorized client) will give a 401.

Given that others (including me) have got this to work fine, there is something going on with some peoples accounts and their permissions.

https://matrix.to/#/!NbTssxRUWRYtpBMWeF:half-shot.uk/$1479230591361667fXwZe:matrix.org

[ara4n]

the order i tried was to auth without write access, then unlink and auth again without write, then unlink and auth with dm. could be that the relinking breaks?

[Half-Shot]

the order i tried was to auth without write access, then unlink and auth again without write, then unlink and auth with dm. could be that the relinking breaks?

Officially, this should work fine. I've recently tested that scenario myself and it did work.

I really need more testing though on this one.

[Half-Shot]

I'm closing this one on the basis that I've since changed the way send tweets are handled with it's own handler and I've not been able to reproduce this. I'll open it if anyone else reports a similar problem or it comes up in testing.

[Half-Shot]

http://paste.alacon.org/43428 appears to be having the same issue, even with the fixes.

[Half-Shot]

Doesn't appear to be related to content, which was one speculation. The authorization thing is still odd, since we check authorization before sending.