Just reading the new twitter changes.
There are some potential challenges here with these.
Firstly the requirement to authenticate the feed, the twitter badge plugin runs mostly on the client side so it’s the site reader who is connecting not you. To be able to authenticate the feed this would have to be turned completely on it’s head and the plugin will need to be server based and just render the results to all the users.
This makes it more complex to code and also for you to setup.
The second is the “display requirememts”, the idea is that you MUST have your tweets displayed EXACTLY as twitter wants them. The idea of this plugin was to have a shorter display so that the tweet does not take up all of the screen and the descriptive date format for me was one of the key features. But surely that’s what their own widgets do making third party plugins kind of redundant.
I fully understand why twitter wants to do this but it does not look promising for this future of this plugin.
Visioniz have offered to take over this plugin so hopefully they will be able to work around the API requirements.
As you might be aware, I’ve stopped supporting this plugin because of the iminent API changes that mean that client based solutions to displaying tweets are not going to work any more.
The Visioniz chaps don’t seem to be doing much with this plugin. I’m sure they will let us know if that’s not the case.
I’ve experimented with the widgets supplied by twitter and they do get something quite close to what I wanted so you might want to check that out for an easy option. The Jetpack plugin also provides a twitter feed, I’ve not actually looked at that but it’s been reported as being quite good.
For my site I’ve switched over to Really Simple Twitter Feed so that would be my current recommendation.
- The topic ‘[Plugin: Twitter Badge Widget] Twitter Breaking Changes’ is closed to new replies.