Recent activity
Subscribe to this feed
mdy replied on September 26, 2008 09:24 to the idea "Add security to the API" in Twitter:
Hello. Just wanted to make sure that developers who use Twitter's API are aware of impending changes to the API's JSON responses, which may affect or break existing applications.
The change will take effect on October 25, 2008.
See this thread in the Twitter Development Google Group for details.
(And please pardon this posting if you already know this news.)
Edo replied on September 24, 2008 18:54 to the question "OpenMicroBlogging spec" in Twitter:
candrews replied on September 24, 2008 17:23 to the question "OpenMicroBlogging spec" in Twitter:
-
Todd Eddy started following the question "OpenMicroBlogging spec" in Twitter.
lantrix replied on August 22, 2008 14:16 to the question "Will we ever get IM service back?" in Twitter:
p858snake replied on August 20, 2008 08:35 to the question "Will we ever get IM service back?" in Twitter:
Todd Eddy replied on August 19, 2008 21:29 to the question "Will we ever get IM service back?" in Twitter:
I understand that capacity needs to be added and such but seriously I really don't think this is the "top priority" as they keep saying. If this is a top priority and taking 3 months, what about stuff that isn't top priority? There are plenty of xmpp sollutions out there. Some are quite scalable even if the configuration can be confusing (ejabberd I'm looking at you).-
Todd Eddy started following the question "Will we ever get IM service back?" in Twitter.
Todd Eddy replied on June 12, 2008 18:04 to the problem "Unable to upgrade twhirl" in Seesmic:
a whole lot of trial and error. Go through your running processes and tried stopping processes that don't look familiar. Just search on the process name in google and you'll usually find info to know if it's an important system file or from some other application. If you do stop a critical process, restarting the computer will fix it.
FWIW I don't get these errors anymore when upgrading, so it got fixed somewhere (either in a logitech update or air update)
t3mujin replied on June 12, 2008 13:51 to the problem "Unable to upgrade twhirl" in Seesmic:
-
t3mujin started following the problem "Unable to upgrade twhirl" in Seesmic.
-
Alex started following the idea "Add security to the API" in Twitter.
-
Damo started following the idea "Add security to the API" in Twitter.
-
duniyadnd started following the idea "Add security to the API" in Twitter.
Todd Eddy replied on March 05, 2008 01:31 to the problem "Unable to upgrade twhirl" in Seesmic:
Todd Eddy replied on March 05, 2008 00:47 to the problem "Unable to upgrade twhirl" in Seesmic:
An update on this... I tried uninstall and reinstall twhirl with no luck. Even removed it manually my deleting it in program files and any mention of twhirl in the registry and still no luck. Tried to uninstall adobe air to reinstall and it says to contact the administrator... when I am the administrator. so I guess it's not twhirl specific so trying to contact adobe now. I'll update this if I can get air working again.
Todd Eddy reported a problem in Seesmic on March 03, 2008 04:06:
Unable to upgrade twhirlWhen trying to upgrade from 0.6.3 to 0.7.1 I get the following error:
Sorry, an error has occurred
An error occurred while updating the application. Try updating it again. If the problem persists, contact the application author.
Error #0
I tried using the automated installer and manuall install. Also tried uninstalling the current version using both add or remove programs and the built in uninstall under advanced options in the installer. All give similar error and error #0
(edit)
This is on Windows XP Pro SP2. Air v1.0. Current version of twhirl is 0.6.3
mdy replied on December 27, 2007 04:49 to the idea "Add security to the API" in Twitter:
Todd -- It's possible you already know this, but just thought I'd mention:
I think you'll get a faster response to API related suggestions at the Twitter Development Google Group, which is devoted almost entirely to API related discussions.
See http://groups.google.com/group/twitte...-
mdy started following the idea "Add security to the API" in Twitter.
Todd Eddy shared an idea in Twitter on December 26, 2007 22:36:
Add security to the APII'd like to suggest a couple things to improve the security of the api and twitter in general. Use SSL for the API stuff and for logging in. Also instead of having to give all these sites my username and password and updating it everywhere, have an "api key" that I can use instead. Having to hand over my password, knowing it's going to be transfered "in the clear" worries me. The api key I can understand taking some time but SSL could be as simple as getting a certificate and force all conections to SSL (rewrite http:// to https://)
| next » « previous |
Loading Profile...





