Back to the main page.

Bug 246 - svn server does not send the updates to twitter

Status CLOSED FIXED
Reported 2010-11-27 13:33:00 +0100
Modified 2011-01-26 15:38:31 +0100
Product: FieldTrip
Component: documentation
Version: unspecified
Hardware: PC
Operating System: Linux
Importance: P1 minor
Assigned to: Simon Oosthoek
URL:
Tags:
Depends on:
Blocks:
See also:

Robert Oostenveld - 2010-11-27 13:33:02 +0100

http://twitter.com/fieldtriptoolbx does not show any of the recent updates


Robert Oostenveld - 2010-12-01 16:22:02 +0100

there is a hook to the svn software that should do this. I guess that the twitter API has changed, which means that the hook has to be updated. It requires login on the svn server and sudo root to change stuff in /home/svn/fieldtrip or so.


Simon Oosthoek - 2010-12-02 15:18:55 +0100

The problem seems to be that twitter no longer supports basic http authentication on the page used to submit the commit messages. An alternative might be to use a commandline twitter tool, like "twidge", though that has a complication, in that it's written in Haskell (which isn't installed on the svn server and not easily available; it's redhat, not debian) I'll keep on looking...


Robert Oostenveld - 2010-12-22 23:29:42 +0100

using ttytter (cmmand line client with no difficult external dependencies) I got it to work again using OAuth. http://www.floodgap.com/software/ttytter/ ttytter is installed in the fieldtrip repos directory together with the key for http://twitter.com/#!/fieldtriptoolbx


Robert Oostenveld - 2011-01-26 15:37:11 +0100

I closed all bugs that were resolved prior and including 2011-01-25. All resolved bugs should have been discussed by now, therefore we don't want to see them again in the next meeting. Instead, in the next meeting we want to see the recent improvements and fixes.


Robert Oostenveld - 2011-01-26 15:38:31 +0100

I closed all bugs that were resolved prior and including 2011-01-25. All resolved bugs should have been discussed by now, therefore we don't want to see them again in the next meeting. Instead, in the next meeting we want to see the recent improvements and fixes.