I was looking at, working with and writing documentation for the Tweet and Direct Tweet components as they would have some great value for us in monitoring and for other workflow/ServiceDesk items (tweet users when classroom emergencies come in for example). The problem is that on setting up the components, access tokens and consumer tokens all work (as verified by a regular scipt external to Workflow) but when used in Workflow a (404) error is generated. The guess is that Twitter has changed the URL that needs to be used to make a tweet (SSL enforced, URL changed, etc.) and the component has the URL hardcoded inside of it.
If components can't be upgraded in a more timely manner, perhaps making items that can change by a third-party more often (URLs, SSL, etc) as editable fields inside of the components rather than have them hard-coded into the component.