Steve Purcell

Hi Stan, that's neat! I'll have a think about how/whether to merge some of that back into this main repo. (Since you didn't start by forking this repo it's not...

Hi @Mandooox, please file related issues on tweet.js-mod rather than here.

@Mandooox As discussed earlier in this issue, it's not yet clear whether it will be possible to keep `tweet.js` working after the old API is disabled. For now, it's still...

@petenorris To be clear, `tweet.js` _will not_ work with the Twitter 1.1 API, because that API requires the use of authentication, and nobody with any sense will put his API...

I am also considering building a kind of "proxy" site, which would allow you to enter your Twitter auth details, and then it would sit between `tweet.js` and the Twitter...

Thanks guys. There's already been some discussion about options. If we put in work to provide a middleman service, we're in danger of being shut off by Twitter for bypassing...

Is this still happening? Can you please either provide a link to the site where the widget is misbehaving, or the code you are using to execute the widget? (Note,...

Correct, yes, you now need a server-side component, into which you must insert your API key. See #264 for more info.

There are no plans, but I'm open to it. The tests are just unittest.py tests anyway (which framework I originally wrote 20+ years ago!).

Also worth noting that `nose` is only included in `tests_require`, not `install_requires`. I'm surprised if the dev dependencies get included in the Debian package.