Malicious developers
"Encumbrance pollution attack"
Our solution includes "everyone delete your database",
does this really count as being able to resist such
attackts? About the only problem you *won't* have is
independent revisions changing their names the way some
centralized systems could potentially change revision
numbers.
Is it really that bad? Can't people make a new database like the
article suggests?
mtn db kill_rev_locally <rev-id>
mtn db init --db=new_db.mtn
mtn serve --db=old_db.mtn
mtn --db=new_db.mtn pull localhost 'net.example*'
<kill mtn serve>
mv new_db.mtn old_db.mtn