* MHonArc should understand most non-numeric timezones. May need
some education. Logs show MHonArc is ignorant of AEST, MET;
no errors reported under fukuzawa. See resource.
* A single clock incorrectly set far in the future can do
very large damage. More than enough to offset the gains
Tomoyuki,
Confirmed there is a problem. It didn't take too long to stumble
across fukuzawa poster Dana Buntrock, whose computer thinks it is
1999. So of course her messages are acculmulating at the head of the
date index. I'm not sure what else is messed up with dates or sorting,
but this alone
[JB]
Tomoyuki,
If sorting by the Date: field is causing big problems for fukuzawa, we
will switch back to sorting by recieved time, and find another way
tohandle archive imports. (Let me coordinate this with the folks who
arecurrently importing archives; this may take a day or two.)
[AL]
Thanks, w
Albert,
You've outlined an excellent path for establishing a good growth
model. The path requires, however, a fair amount of work, and we're
not even close to a limit on the HTTP traffic side. I don't want to
expend the effort until the service is bigger, i.e. a time when the
effort has a more i
This is a list of ceilings that will be bumped into assuming service
continues growth. First limiting factor appears to be disk space,
which needs attention at or before 4x growth. (Estimate: 1 to 1.5
years fromn now, unless things get exciting.) All resources can be
expanded as necessary, and al
Archive imports must be automatic, or not allowed. (I'm laying down
the law here; a core value of the service is automation, and I am not
going to do manual imports of list archives) Is archive-date: a
standard field? If so, do you have the RFC number?
A few other (unsavory) possiblities, off th
"mailto:"; links are the cleanest, simplest, and most convenient
solution. I wish I felt comfortable using them. Several months ago,
spammers started harvesting email addresses from the archives and I
thought they would destoy the service. I made a lot of anti-spam
changes to discourage them, but
Tomoyuki,
If sorting by the Date: field is causing big problems for fukuzawa, we
will switch back to sorting by recieved time, and find another way to
handle archive imports. (Let me coordinate this with the folks who are
currently importing archives; this may take a day or two.)
Let me ask thi
>
> this new setup is very incovenient because the new messages
> (that i haven't seen yet) don't get appended at the top, but
> get buried somewhere several lines below.
>
this sorting scheme is especially bad in the "fukuzawa"
archive, where many of the msgs are comin
From: Jeff Breidenbach
>
> * find a way to get From: email addresses on page (recurring request)
>-> 1) Just do it and hope Brabec's spambot shield works
>-> 2) Include the address, as a .gif
>-> 3) Some other way. (Mangle it slightly?)
interface of what Lynx does with Usenet:
you say you made the change "the other day".
well, so i must have noticed it right away.
this new setup is very incovenient because the new messages
(that i haven't seen yet) don't get appended at the top, but
get buried somewhere several lines below.
the better way to merge / import exis
11 matches
Mail list logo
