There is a need for cross populating of torrent data, verification capabilities using the torrent files, and some basic standards (even assinine xml) to facilitate further development.
Primarily, the checksum and file parser should be implemented in bitche to provide verification of data integrity across all sources especially to eradicate malevolent injections of bad data. Requires only fetch and parse of torrents from all sources, correlation of cert data, and option to verify files locally.
Also a script capability for cross populating data using a standard format (xml or enhanced torrent) would allow both for more specialized trackers to guarantee their clients maximal availability as well as facilitate data integrity to prevent rogue injections of malevolent sources.
This would provide additional opportunity for sourcing from unique originatorsof data as well as scripted capacity to add trackers to a new content availability across all services automatically.
Parsing or preparing a standard cgi post form (like add new) is simple and human confirmation of word-confirm and user would be minimized nothing more than the same scripting parser method of current.
1: verification of file data
2: verification of torrents across all systems
3: correlation of tracker availability and posting to server of complete availability
4: filtering ability on the client prior passing to bt to eliminate problematic or unverified tracker listings on the torrent.
All of this is scriptable and easily implemented, especially if the xml/rss/notify options are used in broadcast availability.
