Twitter API 1.1...
- Started
- Last post
- 4 Responses
- ideaist
Hello boys (and girl).
I had some pretty solid RSS/Atom feeds kickin' around various sites until the past few days when Twitter's 1.0 API became deprecated...
: (
I've read through their updated API:
https://dev.twitter.com/docs/api…BUT, I've yet to be able to come up with a simple feed alternative; any of you cats made the transition smoothly?
I know this is an attempt to keep control of Twitter's usage on blogs, sites, etc. but I'm hoping their is a quick and/or simple solution to persist with my feeds...
Much love...
: )
- falcadia0
Yeah, I went through the same thing yesterday. Ended up using a php solution but it wasn't that easy. I used this page to get there: http://stackoverflow.com/questio…
- falcadia0
Actually, look for the answer from budidino like 5 or 6 down the page. That is what I ended up using. He made it into function so you can just call returnTweet();
- nocomply0
Yeah what a bitch, eh? I have about a dozen or so sites that were using http://tweet.seaofclouds.com/. Now I gotta go in and fix all of them. I'm nervous about any kind of php work-around because I'm guessing it's technically against Twitter's TOS. I think the unfortunate solution is going to be just stripping it out. Bummer.
- The php option is not a workaround. It's using server-side OAuth which is acceptable.falcadia
- That's correct. The PHP option above is the proper way to do it.hereswhatidid
- Cool thanks guys! I'll have to check it out. Just found out about this stuff yesterday.nocomply
- mikotondria30
Hurrah for this, successfully implemented - thanks for the time-saving you guys here :)