On 25 Oct 21 14:25:39, G00R00 said the following to Paul Hayton:
G> I'll build a new pre-alpha if you'd like to test it. One thing to note thou
G> is that this build requires you to reset the dupe database (delete
G> echodupes.dat)
FYI, in the "I have a recipe for boiling water" catagory, I published a new
version of D'Bridge which checks for duplicate MSGID's. It does this not by
logging everything in one huge database but a seperate database per-system of
message received, with the ability to place a cap on the number of entries to
maintain. D'Bridge uses a Base36 formula for naming these tiny files.
I admit its still an overtly sloppy concept no matter what; I don't understand
how MSGID came to be accepted as a "standard" for dupe-checking when CRC's of
the header, Seen-by and circular Path detection works best. To me MSGID is just
lazy programming. The vast majority of dupes over the years has been
from Sysops inadvertently rescanning their message-bases; which could be
nuked by just checking for dates X amount in the past.
I know about the Reply kludge and how it appeals to the obsessive-compulsive
types to have threaded replies... but still... Ahh well. You get what I mean.
Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)
|
