How to manually setup WACUP to use your own Twitter App API keys

[dro]

How to manually setup WACUP to use your own Twitter App API keys

To setup WACUP to use your own Twitter App API keys for sending tweets instead of using the WACUP App API keys, please follow the steps below.

If you are uncertain of what you are doing or only occasionally send tweets then you should ask in the forum or prefer to keep using the WACUP handling (assuming recent changes to how Twitter & access to it's API are e.g. if it's gone to a paid model).

• Goto Preferences -> Advanced
• Change 'WACUP' to 'User App' from the drop down
• Goto Preferences -> Playback -> Play Tracking -> Select the 'Twitter' tab
• Click on the 'Twitter App' link or go to L"https://apps.twitter.com/ to create a Twitter App
  - Please follow the instructions that Twitter provides on how to create a valid Twitter App.
  - If you have created a Twitter App you want to use then please skip this step
• Once the Twitter App is created, goto the part of the Twitter App page which shows your keys
• Copy the 'Consumer Key (API Key)' and the 'Consumer Secret (API Secret)' values and paste them into the same field on the preference page from step 3
• Click 'Encrypt & Save' to store the keys
  - If you make a mistake and you want to change or re-enter the keys, on the Preferences -> Advanced page, changing the drop down from 'User App' to 'WACUP' and back to 'User App' will reset things so you can then go back to step 3
• The preferences page will have now been reloaded and changed to ask for the user credentials to tweet for
• Follow the instructions provided on the preference page to authorise tweeting for the required Twitter user
• You should now be able to tweet to the desired user using your Twitter App API keys

-dro


Note: This is re-posted from the beta sub-forum & has been done in response to reported pending changes to access to the Twitter API which will likely put it all behind a paywall. If that happens then it's going to prevent the WACUP feature from working like it has been since it was first implemented years back but thankfully I put in place a means to use your own Twitter App api details.

I'll be keeping an eye on how this plays out as at the time of this post there's no information on what the cost is going to be as I'd prefer not to pay Twitter considering this is a cash grab but I'm also aware that there are those making use of the feature who'd not be able to use it.

[dro]

Tentatively it seems like they're going to price things starting from $100/month & require some sort of ID verification to go through with it which if so I'm not going to be doing. however it's still not properly defined on what is or isn't going to happen with such short notice.

Either way that basically leaves me shipping a dead feature in WACUP & I now need to decide how I want to handle that w.r.t. to either completely removing it from the plug-in or leaving it as some form of optional it may work it may not approach for those that do still need it 🫤

-dro