Dave Johnson wrote:
On Oct 22, 2005, at 6:22 PM, Allen Gilliland wrote:
It's a bit unfortunate because we've gotten a bit behind with the 1.3
release and now we are in a situation where we pratically have 2
versions ready for release (1.3 2.0).
I don't think that's a big issue. Roller
On Mon, 2005-10-24 at 13:14, Dave Johnson wrote:
On Oct 24, 2005, at 3:05 PM, Allen Gilliland wrote:
i'm still unsure of how to proceed with this. it seems as if we won't
be able to settle on a column definition that works for all databases,
so i am fine moving forward with a set of
When we voted on the 1.3 release, we planned on releasing it on
Java.Net. If there's going to be a hold-up posting the release on
Apache infrastructure and we can't do it by the end of this week, I'm
going to fall back on that original plan.
- Dave
On Oct 24, 2005, at 10:53 AM, Dave Johnson
good summary.
one thing i think is worth evaluating is what effectiveness are we
currently having with preventing spam using what we have now? and where
specifically are we being ineffective?
for example, with one of the comment authenticators enabled, how much
spam are people really getting?
On 10/25/05, Allen Gilliland [EMAIL PROTECTED] wrote:
I have made an attempt at resolving this problem by defining 2 new
variables for the sql scripts ... TIMESTAMP_SQL_TYPE_NULL and
ALTER_PUBTIME_ALLOW_NULL
the TIMESTAMP_SQL_TYPE_NULL is used for the pubtime column of the
createdb script
On 10/25/05, Allen Gilliland [EMAIL PROTECTED] wrote:
good summary.
one thing i think is worth evaluating is what effectiveness are we
currently having with preventing spam using what we have now? and where
specifically are we being ineffective?
for example, with one of the comment
Hi Everyone!
This issue is of urgent importance to me. Che Blogs is being flooded
with trackback, referer and comment spam without mercy for the past few
months.
The situation is totally out of hand and I have tried everything that I
can think of (with suggestions from Dave and others.).
I
