* Originally in bama   
   * Crossposted in fidosoft.husky   
      
   31 Oct 16 13:06, you wrote to me:   
      
    ml>>>> with more dupes flying around, old school slash old style dupe   
    ml>>>> databases can get overrun pretty quickly...   
      
    WV>>> Eh... You are only storing a checksum of the first original. More   
    WV>>> dupes doesn't mean more space needed in the dupe database! ;)   
      
    ml>> that depends on the database format ;)   
      
    WV> It shouldn't!   
      
   again, that depends on the database format...   
      
    WV> Dupes have by definition the same dupe-checksum as the original, so   
    WV> storing them is useless!   
      
   maybe to you but to another developer who may be doing other things than   
   /just/ dupes, it may be needed or desired... don't be so square that your mind   
   is closed to other possibilities and thought processes... perhaps someone is   
   keeping count of duplicate MSGIDs and needing also to store the CRC/hash for   
   each of them...   
      
   example: yesterday i saw two messages with exactly the same MSGID, header,   
   time stamps, and what looks to be the exact same message body... the seenbys   
   and paths were different yet HPT with its HASH+MSGID dupe checking missed   
   seeing the second one as a dupe... both were back-to-back in my message base   
   so it was easy to flip back and forth between them to try to see any   
   differences... golded+'s [I]nfo showed that they were virtually identical but   
   there looked to be one space character immediately after the MSGID that was in   
   one post and not the other... now, get this, both MSGIDs, even though they are   
   the same, are in the dupe database but with different hashes...   
      
   )\/(ark   
      
   Always Mount a Scratch Monkey   
   Do you manage your own servers? If you are not running an IDS/IPS yer doin' it   
   wrong...   
   ... We have no free press any more. It is bought and paid for.   
   ---   
    * Origin:  (1:3634/12.73)