My Linux machine is headless, so browsers except lynx are out of the question. Unfortunately, it looks like lynx doesn't save cookies across sessions, so when bitcollider sends in the bitprints, I'm not logged in and they get dropped. Why does bitcollider need a browser, anyway? Why not just let me put my user name and password in a .bitzirc and send the btiprints directly via HTTP?

Hmm; it should at least remember the submission through the login screen, so we'll try to fix this.

(Also, there is a compile-time option for Lynx to save cookies, "--enable-persistent-cookies", in case you want to take that approach.)

Passing off the submission to the browser provides us with a number of benefits, including, for most browsers, that the submission can be associated with a previous login, and automatic navigation of local firewalls/proxies.

Also, what needs to happen after a submission is highly dependent on what is submitted and what's already in the database: the user might need to confirm some fresh info, and will be presented with already-known info in a variety of still-evolving formats. Thus we like the flexibility of being able to display results, forms, etc. in a browser, rather than making it the Bitcollider's internal duty to submit/receive-results/parse-and-display.

That said, we are working on raw web-service APIs for submission tools and other applications to submit/lookup directly, ignoring the browser completely when appropriate.

Yeah, I played around a little and noticed that it seems to work as long as I log in immediately after submitting the data. Then I switch to my Mac and commit the tags from there.

I'm having the same problem and I'm curious if it'd be possible just to hand off a URL that I can post into my desktop browser (already logged in). So submit the data from bitcollider directly and get back a session ID or something. Then print a URL with the session ID in it which I can paste into my browser. (BTW, kudos on going with the ACS.)

It does work, Aaron, you just have to log in using lynx immediately after bitcollider spawns it.

A workaround you can use for now:

1. Use the bitcollider to generate a submission file, but add the -n flag so that the submission isn't automatically posted.
2. log into bitzi.
3. load /tmp/bitprint.html with the logged-into-bitzi browser, 'click' the submit 'button'.
4. your submission should go through without more problems.