Help Resources/Community/Community Questions & Answers
Posts to Status.net Not Being Delivered
Stephen Judge
asked this on September 12, 2011 06:31
I have setup two Status.net destinations, all the settings look correct and no errors are being reported but my posts are not being delivered to either of them.
My Status.net accounts are:
Idenit.ca
Username: stephenjudge
Server URL: https://identi.ca
No other options set
Profile URL: http://identi.ca/stephenjudge
TWiT Army
Username: stephenjudge
Server URL: http://army.twit.tv
No other options set
Profile URL: http://army.twit.tv/stephenjudge
My posts to both my Status.net accounts should match my posts sent to my Twitter account http://twitter.com/StephenJudge except for my @replies or @mentions . If you compare my accounts you will see that none of my posts that are being delivered to my Twitter account are also being delivered to my Status.net accounts (most active feeds http://j.mp/MyDigg and http://j.mp/Stumbl). Both my Status.net accounts are active and in good order and I do post to them outside of dlvr.it
So if the settings above are correct, why are my posts not being delivered and why are there no errors being reported.
Also wouldn't it be better for dlvr.it to use the StatusNet API http://status.net/wiki/API along with OAuth which StatusNet supports to access and post to Status.net accounts rather than logging into these account with usernames and passwords, which can be problematic and is insecure for the user.
Comments
Status.net is not currently accepting posts from dlvr.it -- our attempts to post timeout. We've been in contact with them to resolve the issue, however, they have been slow to respond.
There may be a better way to handle / report the status.net timeouts in the dlvr.it UI.
Thanks for your patience.
We will post any changes in status here:
http://support.dlvr.it/entries/20472603-issues-posting-to-status-ne...
Thanks for letting my know this. Have you filled a bug report in the StatusNet issue tracker about this that I can subscribe and comment on. I believe you will get a better response on a bug tracker than by contacting them by email. Open source developers generally prefer to deal with problems on a bug tracker rather than email. http://status.net/open-source/issues
Could I suggest for the benefit of other users, that you place a note on users dashboards whenever they add a StatusNet destination to notify them of this issue. I didn't even realise for months after posting content everyday through dlvr.it that there was even a problem with StatusNet. Also as I said before "wouldn't it be better for dlvr.it to use the StatusNet API http://status.net/wiki/API along with OAuth which StatusNet supports to access and post to Status.net accounts rather than logging into these account with usernames and passwords, which can be problematic and is insecure for the user." using the official StatusNet API to communicate with there servers may solve this problem.