These are chat archives for pavelk2/social-feed
Once upon a time we had one guy helping out with Social-feed and he was looking for issues to contribute. I would like to share with you guys here things to consider next to implement:
Currently we have bower_components in the repository itself - i believe it is a bad practice. We can clean them up, make a new release, update https://github.com/pavelk2/social-feed/blob/gh-pages/bower.json file (so it cites the latest release). In this case the code will work, but it will not be possible to use it as an example via github pages. We can create another repository (social-feed-example), where we define the logic of downloading all the dependencies and we deploy it on Heroku (for free). So social-feed is only for the plugin itself, social-feed-example uses social-feed via bower to make example. Social-feed-server is an optional tool which can also be easily deployed on Heroku.
I have created a simple server-side app (you can deploy it easily on Heroku via a deploy button).
here is an example how you use it:
So what we can do: for each social network in social-feed we can add an option "server-proxy-url", which is false by default, which means that all the requests go as they go now - directly to the social networks. Otherwise - we can define a url of the app to send request, like "https://social-feed-server.herokuapp.com/" and inside to define the appropriate logic. If you use the social-feed-server app - there is no need to specify access_tokens as, they are added later in the app itself. Also omit adding callback? in the end of your urls for social-feed-server.
You can use https://codeclimate.com/ to validate the code on social-feed and fix issues if any.