Open tmaiaroto opened 10 years ago
Not sure about this... Using OAuth in this manner (for Twitter at least) doesn't allow users to post to their timelines, etc. So a lot of functionality that's going to be desired will not be available.
Part of why I wanted front-end OAuth for the APIs was to use Social Harvest public app ids and track usage. Also maybe to build more of a community for "social harvesting" - sharing data sets maybe, etc.
Look back into this later. It's still possible, but requires a central server to be hosted (cost).
Using: http://adodson.com/hello.js https://github.com/MrSwitch/hello.js
This will allow for additional API methods to be called which can enrich widgets (show profile pictures on demand for example).
It will also allow the dashboard to help with social media management. In other words, users could then post messages from the dashboard. If the harvester API allows various scheduling, then even scheduled messages could be possible using the dashboard. This expands Social Harvest and pushes it into a management platform as much as it will be an analytics platform.