We're going to devote some effort to Bitcollider fixes and enhancements soon, so we'd like to hear ideas for what would be most interesting or useful.

Some ideas that have come up in discussion here or elsewhere:

• big files >4GB support
• Mac installer, 'shell' integration, uninstaller
• BitTorrent hash-segments calculation
• pretty-up HTML submit page
• p2p link (magnet, etc.) building feature completely in client (on submit HTML page, perhaps?)
• Linux GUIs in KDE or GNOME
• pure-java Bitcollider
• better browser handoff on all platforms (it's fragile everywhere)
• export/submit tigertree interim values
• support for extracting intrinsic metadata from more audio formats, such as FLAC/SHN/RealAudio
• support for extracting intrinsic metadata from more video formats, such as RealVideo and ogg-media OGM
• support for extracting intrinsic metadata from other document formats, such as PDF/DOC/XML
• support for unrolling composite file formats, bitprinting/submitting both the container and all included files (for ZIP, TAR, etc.)
• enable Bitcollider to watch a specific directory, and auto-submit new files (w/ user permission)
• additional options, command-line or otherwise, to control what is calculated, do a lookup without submit, suppress plug-in loading, etc.

Other ideas?

What's most important?

Can anyone volunteer to tackle specific items?

Thanks,

- Gordon @ Bitzi

I may have different interest that some people, as I'm planning to bitzi to extract metadata for use in my p2p app's catalog of files.

• Guess the mime-type and use that rather than "tag.image.format", or "tag.video.format"
• AVI tags (see this list of possible tags. Looks like I need to write a command line util like id3v2 to get more people using this. I would be nice if my opensource set top box could organize stuff as well as the iTunes clones).
• Output RDF triples on the client side. The catalog schema in Mnet is based on RDF. My python wrapper does this already, but not as well as it could
• Adding a BitSociety tag from the command line

For the website itself:

• RSS list of BitSociety files (this was suggested by someone else). Hopefully you could employ a) staticly writing the RSS feed once per update, b) some restriction that would disallow clients that didn't use ETags or Last-Modified-Date.

mpeg-4 file format support.

And the ability to hash many files at once! This is incredibly annoying! NO ONE LEAVES COMMENTS AND RATINGS FOR EVERY FILE THEY SUBMIT.

Also the ability to open the file in a user-defined browser. firefox is my default browser, but I would rather use opera to make submitting quicker.

For argument parsing use getopt_long.

I know this is a very late reply but I'm wondering if anyone is still listening.