Twitter socket error?

Jonsey · Post by **Jonsey** » Fri 20 Aug 2010 8:23 pm

I donk know what it was but it has started working again.

lloydp · Post by **lloydp** » Wed 01 Sep 2010 3:05 pm

When I discovered the Twitter option (on v1.9.0 955) the other day I switched it on for my default twitter a/c and it was working fine. I then created a new twitter a/c just for the wx and it didn't work. (no info, just didn't update. I reverted back to my normal a/c and it now doesn't work either. I tried your twitter test prog, and this comes up with a popup box 'HTTP/1.1 401 Unauthorized' error for both a/cs. My twitter client is working fine. Any suggestions please?

Post by **steve** » Wed 01 Sep 2010 3:59 pm

lloydp wrote:When I discovered the Twitter option (on v1.9.0 955) the other day I switched it on for my default twitter a/c and it was working fine. I then created a new twitter a/c just for the wx and it didn't work. (no info, just didn't update. I reverted back to my normal a/c and it now doesn't work either.

There's an assumption that you will only use one Twitter account with Cumulus; it saves the authentication strings in cumulus.ini. To switch accounts, you have to delete the "OauthToken=" and "OauthTokenSecret=" lines before starting Cumulus, so it gets the new strings.

I don't know why it didn't work when you switched back, except I see that mine hasn't updated for the last 12 hours. I'll see if I can find out why that is; Twitter often seem to have problems.

The '401' problem while trying to authenticate has also been reported by someone else on the Twitter development forum.

Post by **steve** » Wed 01 Sep 2010 4:12 pm

I turned logging on for mine and it's also getting 401. I guess we'll have to wait till Twitter fix the problem, it's already been reported.

Post by **steve** » Wed 01 Sep 2010 5:50 pm

It appears that they fixed a bug in Twitter where they were accepting timestamps which were off by a long way (so now they don't). This exposed a bug in the library routine I use to calculate a Unix timestamp where it didn't take daylight savings into account. I've fixed this in build 956:

http://www.nybbles.co.uk/downloads/beta ... sSetup.exe

lloydp · Post by **lloydp** » Wed 01 Sep 2010 6:31 pm

[quote="steve"]It appears that they fixed a bug in Twitter where they were accepting timestamps which were off by a long way (so now they don't). This exposed a bug in the library routine I use to calculate a Unix timestamp where it didn't take daylight savings into account. I've fixed this in build 956:

Steve you're a star - works perfectly now, thanks!

Cumulus Support

Twitter socket error?

Re: Twitter socket error?

Re: Twitter socket error?

Re: Twitter socket error?

Re: Twitter socket error?

Re: Twitter socket error?

Re: Twitter socket error?