I was checking the wiki today to see how many open tickets there are,
checking to see what current changes have gone through since I last
did a trunk jump ... etc, etc. Preparing for the next jump basically
Anyway the spam is getting a bit ridiculous isn't it? How are you
contributors
Hey, I recently started running the SVN of Typo and was fiddling withgetting a
desktop client to access it via xmlrpc, however I get thefollowing error. It
seems like something internal to my ruby install(mostly from gem, but on ubuntu
dapper). If someone could point me inthe right direction
As a follow up to this I know there's a bit of a debate around Trac
development itself regarding editing comments. You can't currently
delete these spam comments unless you do it via the database.
http://projects.edgewall.com/trac/ticket/454
But is it not possible to enable the permissions
Hi all...
I don't know if anyone else has noticed this lately, but there has been a lot
of spam on my blog as of late even though non-AJAX commenting is disabled
*and* anti-spam is enabled.
Although the spam is completely useless -- it doesn't even contain a link to
any site -- I'm sure it's
Trac spam sucks. Trac spam that *re-opens closed tickets* sucksreally, really
hard.
Scott
On 3/12/06, Steve Longdo [EMAIL PROTECTED] wrote: It would be nice if Trac
could limit entries containing more than say 5 links... On 3/12/06, Gary
Shewan [EMAIL PROTECTED] wrote: As a follow up to
That looks like a problem with your setup. None of the code there is
from Typo, it's all from rails+dependencies.
On Mar 12, 2006, at 8:56 AM, Kevin Kubasik wrote:
Hey, I recently started running the SVN of Typo and was fiddling
withgetting a desktop client to access it via xmlrpc, however
Huh. My impression with trackbacks was a lot of it was automated
through blog software (looking at links in your post and checking
them for trackback URLs). A javascript implementation like this would
completely break that functionality.
On Mar 12, 2006, at 12:50 PM, Marco van Hylckama
Ok, cool, that's what I thought. It actually seems to be an issue withwritely's
implementation of the mt API. I'll file a bug with them.
Cheers,Kevin Kubasik
On 3/12/06, Kevin Ballard [EMAIL PROTECTED] wrote: That looks like a problem
with your setup. None of the code there is from Typo, it's
Marco van Hylckama Vlieg wrote:
Nope, that's pingback. Similar to trackback, but different.
Sending a trackback requires a manual action by the blogger who wants
to send one. Pingback however is done automatically.
Typo seems, at least on the surface, to consider the two to be exactly
the
On Mar 12, 2006, at 4:50 PM, Trejkaz wrote:
You can get round CAPTCHAs too by re-serving the captcha images as
legitimate captchas on, say, your porn sites and feeding the punter's
response back to the spammed site. Even if you miss the timeout 9
times out of 10, there's always another punter.
Getting the image doesn't do much without the session ID. You should
destory the session anyway.
On 3/12/06, Kevin Ballard [EMAIL PROTECTED] wrote:
On Mar 12, 2006, at 4:50 PM, Trejkaz wrote:
You can get round CAPTCHAs too by re-serving the captcha images as
legitimate captchas on, say,
Daejuan Jacobs wrote:
The spammer, who also runs a porn site, hits up your blog, sees your
captcha, copies the image and re-serves it as the captcha for someone
visiting his porn site. That unknowing person successfully deciphers
the captcha, and the spammer takes the result and feeds it back
Uhh, what? The spammer serves back the result in the same session
they got the captcha in the first place. This is an automated process
so it has the potential to be fast enough.
On Mar 12, 2006, at 5:53 PM, Daejuan Jacobs wrote:
Getting the image doesn't do much without the session ID.
Leslie Titze wrote:
Could anyone point me to a solution for this?
As you might expect, creating the cache directory inside the Rails
root solves this (perhaps Typo could add the cache directory to the
repository so that people don't have to think when doing an install.)
TX
Sounds like the Typo process doesn't have permissions to create a
cache directory in the root of Typo. You should either create the
directory or give the Typo process permission to do so.
Oh, and edge rails doesn't work with Typo right now. Stick with Rails
1.0
On Mar 12, 2006, at 6:20
I see what you're saying, but if my server deletes the session after
you access the page to get the image (or timeout), than what you're
tying to server me is invalid.
On 3/12/06, Kevin Ballard [EMAIL PROTECTED] wrote:
Uhh, what? The spammer serves back the result in the same session
they got
Yes, that's called a timeout. And Piers Cawley had it right when he said
Even if you miss the timeout 9 times out of 10, there's always
another punter.
There's no way for you to know, serverside, whether the access is by
a spammer or by a real user, so as long as the spammer gets an answer
17 matches
Mail list logo
