Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by johnseq (1046) on 2003.10.06 12:40 (#24685) Journal
    http://www.venge.net/monotone/ is a distributed version control system that includes trust metrics and some PKI that got me thinking. My idea is that you can think of collaborating on a blacklist as a project under version control, one in which you don't necessarily trust everyone else's patches.

    It's different from the blacklist-as-single-document-from-a-single-server design -- instead consider a blacklist as instead comprising of a baseline and a set of patches from multiple sources, some of whom you trust, and some of whom you don't. I think you might end up with something like what Cloudmark does for client-side spam filtering, but with more power over who's spam-reporting votes matter to you.

    I know there are bootstrap issues regarding the baseline, the document format, etc ... but suspect they are resolvable.

    I haven't used monotone, but it just sounds like a cool hack and a neat overlap between several technology domains which do not normally overlap.