Problem with direct message - watch followers
- martin@rootjazz
- Site Admin
- Posts: 34803
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Problem with direct message - watch followers
Ok please send in the new update, will wait for an hour.
Else will submit the logs as directed.
Else will submit the logs as directed.
Re: Problem with direct message - watch followers
Is it fixed then finally ?
- martin@rootjazz
- Site Admin
- Posts: 34803
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Problem with direct message - watch followers
am not sure if your issue, but the running a single account test DM issue I found is fixed
Re: Problem with direct message - watch followers
Starting stream: https://userstream.twitter.com/1.1/user ... followings with:
Running stream connection: https://userstream.twitter.com/1.1/user ... followings with:
* WEB ERROR: The remote server returned an error: (401) Unauthorized.
Same issue again, what now ?
Running stream connection: https://userstream.twitter.com/1.1/user ... followings with:
* WEB ERROR: The remote server returned an error: (401) Unauthorized.
Same issue again, what now ?
Re: Problem with direct message - watch followers
Do you think it is because of some port being blocked ? Because following works perfectly.
- martin@rootjazz
- Site Admin
- Posts: 34803
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Problem with direct message - watch followers
ok so we are back to square one, the issue with watching.
Are you trying to connect to multiple streams from the same IP / account? That can cause a fail (although from memory you are not doing this - but please confirm)
failing that. If you stop all existing actions on your machine / instance, then try and run a single watch - is it same issue?
Could you export me an account for testing here - this will show if your machine is blocking something / somehow
(if you need my IP to auth for proxy use, let me know -
Are you trying to connect to multiple streams from the same IP / account? That can cause a fail (although from memory you are not doing this - but please confirm)
failing that. If you stop all existing actions on your machine / instance, then try and run a single watch - is it same issue?
Could you export me an account for testing here - this will show if your machine is blocking something / somehow
(if you need my IP to auth for proxy use, let me know -
Code: Select all
support[at]rootjazz[dot]com
Re: Problem with direct message - watch followers
Get TwitterUser: technology using:
* ERROR: Unauthorized - Authentication credentials were missing or incorrect.
401
Okay so when I delete everything do a watch followers for that account first, it works fine.
But problem is when I do a follow process in parallel, the follow process shows the error as indicated above.
Is there some issue with parallel processes not being allowed to run?
* ERROR: Unauthorized - Authentication credentials were missing or incorrect.
401
Okay so when I delete everything do a watch followers for that account first, it works fine.
But problem is when I do a follow process in parallel, the follow process shows the error as indicated above.
Is there some issue with parallel processes not being allowed to run?
- martin@rootjazz
- Site Admin
- Posts: 34803
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Problem with direct message - watch followers
so you have accA.
you create a watch action for accA,
* works fine
you create a search and follow action for accA
then the watch action fails.
From what I know of hte API that *should* be fine. Let me test here
you create a watch action for accA,
* works fine
you create a search and follow action for accA
then the watch action fails.
From what I know of hte API that *should* be fine. Let me test here
- martin@rootjazz
- Site Admin
- Posts: 34803
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Problem with direct message - watch followers
fixed a bug, when you follow someone, twitter sends it down the wire, the program was treating that as a new follower to you, thus trying to follow yourself and failing.
The next update will fix this. I shall let you know when it is ready.
Regards,
Martin
The next update will fix this. I shall let you know when it is ready.
Regards,
Martin