{"id":333,"date":"2011-05-27T20:28:16","date_gmt":"2011-05-28T01:28:16","guid":{"rendered":"http:\/\/www.mageuzi.com\/blog\/?p=333"},"modified":"2011-05-27T20:30:31","modified_gmt":"2011-05-28T01:30:31","slug":"trowl-re-authorize-for-dm-permissions","status":"publish","type":"post","link":"http:\/\/www.mageuzi.com\/blog\/2011\/05\/27\/trowl-re-authorize-for-dm-permissions\/","title":{"rendered":"Trowl: Re-Authorize for DM Permissions"},"content":{"rendered":"

\"settings_add_account\"<\/a>Twitter recently announced that they\u00e2\u20ac\u2122re adjusting application permissions such that DMs require a new level of access. To ensure that users know exactly what is being accessed by the programs they use, Twitter wants users to re-authorize applications that require DM access.<\/p>\n

If you use Trowl to view DMs, or you use the DM remote feature, you will need to re-authorize Trowl to access your DMs. otherwise you will start getting errors at the end of June<\/strong>.<\/p>\n

Luckily, it\u00e2\u20ac\u2122s pretty easy to do this. The first step is to go to the settings screen and click on \u00e2\u20ac\u02dcAdd Account\u00e2\u20ac\u2122, like the screenshot at the right shows. This will take you to the usual authorize screen, as if you were adding a brand new account. Click the link, and you will be taken to the Twitter website to authorize your account. The screenshot below shows the important part \u00e2\u20ac\u201c that you will be allowing Trowl to access your direct messages.<\/p>\n

After you enter your username and password, you will get the pin to enter back in Trowl. After you do this, Trowl will realize you authorized an account you already have set up, and will simply update your existing account with the new authorization. You will need to repeat this process for all accounts you use with Trowl. <\/strong>Click \u00e2\u20ac\u02dcSave\u00e2\u20ac\u2122 to confirm the new authorizations and you\u00e2\u20ac\u2122re done.<\/p>\n

(One other minor thing to note: I run Trowl on several computers, and each instance is authorized for the same Twitter accounts. One thing I noticed is that as soon as I re-authorized one instance of Trowl with the new access permissions, the access permissions used by the other instances of Trowl instantly became invalid. So, if you have a similar situation, you will need to update every instance of Trowl. I imagine this isn\u00e2\u20ac\u2122t a common situation, but wanted to mention it just in case.)\"twitter_authorize\"<\/a><\/p>\n

What if I don\u00e2\u20ac\u2122t want Trowl to access my DMs?<\/strong>
If you actually don\u00e2\u20ac\u2122t want Trowl touching your DMs for whatever reason, then you can either refuse to re-authorize Trowl \u00e2\u20ac\u201c in which case you will get errors whenever Trowl attempts to access them \u00e2\u20ac\u201c or you can change your settings to not Growl DMs or use remote DM commands.<\/p>\n

This is a bit of a nuisance, so thank you for taking a minute to do this. I understand Twitter\u00e2\u20ac\u2122s motivations, but I can\u00e2\u20ac\u2122t help but think there must have been a more streamlined way to implement this.<\/p>\n

Anyway, that\u00e2\u20ac\u2122s it. As always, if you have any problems, send me a tweet<\/a>!<\/p>\n","protected":false},"excerpt":{"rendered":"

Twitter recently announced that they\u00e2\u20ac\u2122re adjusting application permissions such that DMs require a new level of access. To ensure that users know exactly what is being accessed by the programs they use, Twitter wants users to re-authorize applications that require DM access. If you use Trowl to view DMs, or you use the DM remote […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[6,33],"tags":[7,12,34,61],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.mageuzi.com\/blog\/wp-json\/wp\/v2\/posts\/333"}],"collection":[{"href":"http:\/\/www.mageuzi.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.mageuzi.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.mageuzi.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.mageuzi.com\/blog\/wp-json\/wp\/v2\/comments?post=333"}],"version-history":[{"count":1,"href":"http:\/\/www.mageuzi.com\/blog\/wp-json\/wp\/v2\/posts\/333\/revisions"}],"predecessor-version":[{"id":334,"href":"http:\/\/www.mageuzi.com\/blog\/wp-json\/wp\/v2\/posts\/333\/revisions\/334"}],"wp:attachment":[{"href":"http:\/\/www.mageuzi.com\/blog\/wp-json\/wp\/v2\/media?parent=333"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.mageuzi.com\/blog\/wp-json\/wp\/v2\/categories?post=333"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.mageuzi.com\/blog\/wp-json\/wp\/v2\/tags?post=333"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}