Ian Clarke wrote: [snip] > Again, my core gripe is that something that worked fine was modified > without any good reason. The specifics of the way in which it was > modified (being in HEX and being in seconds since the epoch) are also > annoying, but secondary. Of these two issues, I think the HEX encoding > is the least easy to justify, but both strike me as being unnescessary. > > It just annoys me when people try to fix something that isn't broken.
I totally agree with you Ian, but I have somehow the feeling that our "not fixing fixing what's not broken" approach seems to become a seven-headed hybris monster, being larger than anyone could justify. I liked thelemas simplistic approach: a) Hex is the culprit -> switch to decimals b) seconds since epoch are the culprit -> switch to the old style DBR I remember very good your *very* active attack when we discussed browser plugins. You opposed with all means to make Freenet links be dependent on these certain browser plugins. I know that it is a bad comparision, but I would rather like to avoid to have other FProxies (i.e. there is a C++ fcpproxy) implement these advanced date parsing routines. Why can't we simply add a ?dbrdate=DD/MM/YYYYY (or MM/DD if we go for the US scheme) option to fproxy just like the ?htl=... which will overrride any hex date schemes. Voil?, everybody is happy. (more or less) Sebastian -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2301 bytes Desc: S/MIME Cryptographic Signature URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20011203/caf947b8/attachment.bin>
