Twitter pulled a fast one on us: they revoked Twidge’s API key for some fake security reason. See http://blog.nelhage.com/2010/09/dear-twitter/ for why this is wrong-headed.
You have three options:
In August and September, 2010, twitter made two changes: they dropped support for authentication that doesn’t use OAuth, and they also dropped support for some of the older-style API requests. Both of these could cause some trouble for you. If you are getting errors, here’s what you should do:
It has been observed that Twitter has disabled the old API on some servers and not on others. You may not see this problem immediately.
Set serverbase: https://identi.ca and urlbase: %(serverbase)s/api in [DEFAULT] in ~/.twidgerc
Also change all … %(serverbase)s/oauth/ … lines to … %(serverbase)s/api/oauth …
No. The Identica platform doesn’t implement all the features of Twitter. You can see the status of their API. Major things to note are that Identi.ca doesn’t support direct messages, nor will it support —unseen options to various commands. Some of these options may be silently ignored, and others will return mysterious errors.
Updating works fine.
Here’s how I installed ghc and twidge with MacPorts:
sudo port install ghc
sudo port install hs-cabal
cabal install twidge
Last edited by shortmanikos,