Re: [PHP-DOC] ca3.php.net with print function

2006-03-23 Thread Friedhelm Betz

Jean-Sébastien Goupil wrote:

Yo

When searching for print function on ca3.php.net, it returns CSS...
http://ca3.php.net/print

returns :

http://ca3.php.net/print.css

other servers return the print function...

What's wrong ?



Miror specific problem? Maybe you should write to [EMAIL PROTECTED]
Friedhelm


[PHP-DOC] Re: [PHP-NOTES] Note spam

2006-03-23 Thread Sean Coates
[resend: not sure why this didn't make it through, yesterday;
re-sending; sorry if it's a dupe -S]

Nuno Lopes wrote:
 Well we have already tried a couple of methods but none of them worked
 so far, including DNS blacklists, spamassassin and a simple words
 blacklisting.
 I've run out of ideas. Training spamassassin would probably work, but
 I'm not sure if it wouldn't cause disturbs in the mail server.

Did we drop the double opt-in idea?

- User submits a note (with valid email address)
- We send mail with a token URL
- User clicks URL
- Note is approved and posted

Max 5 notes per address per day. Or x notes per domain/IP per day..

Yes, the evil side COULD be automated, but it's a lot more difficult
than a simple post.

S


[PHP-DOC] Re: [PHP-NOTES] Note spam

2006-03-23 Thread Nuno Lopes

Nuno Lopes wrote:

Well we have already tried a couple of methods but none of them worked
so far, including DNS blacklists, spamassassin and a simple words
blacklisting.
I've run out of ideas. Training spamassassin would probably work, but
I'm not sure if it wouldn't cause disturbs in the mail server.


Did we drop the double opt-in idea?

- User submits a note (with valid email address)
- We send mail with a token URL
- User clicks URL
- Note is approved and posted

Max 5 notes per address per day. Or x notes per domain/IP per day..

Yes, the evil side COULD be automated, but it's a lot more difficult
than a simple post.

S



Well but who's gonna implement that? :) When will the to-be-approved list 
be cleaned? etc..


Nuno 


Re: [PHP-DOC] Re: [PHP-NOTES] Note spam

2006-03-23 Thread Friedhelm Betz

Sean Coates wrote:

[resend: not sure why this didn't make it through, yesterday;
re-sending; sorry if it's a dupe -S]

Nuno Lopes wrote:

Well we have already tried a couple of methods but none of them worked
so far, including DNS blacklists, spamassassin and a simple words
blacklisting.
I've run out of ideas. Training spamassassin would probably work, but
I'm not sure if it wouldn't cause disturbs in the mail server.


Did we drop the double opt-in idea?

- User submits a note (with valid email address)
- We send mail with a token URL
- User clicks URL
- Note is approved and posted


Do we need to approve? I guess we have not enough man-power for that.
Simply post the note after we receive the token.


Max 5 notes per address per day. Or x notes per domain/IP per day..


x notes per domain/IP per day will for sure not work. Think of people 
behind proxies


We should not limit the notes per day. To much to track, imho, no?


Yes, the evil side COULD be automated, but it's a lot more difficult
than a simple post.


I like this proposal, but Nuno's point stands: who's gonna implement that?

Friedhelm


Re: [PHP-DOC] Re: [PHP-NOTES] Note spam

2006-03-23 Thread Sean Coates
 Do we need to approve? I guess we have not enough man-power for that.
 Simply post the note after we receive the token.

That's what I meant. Note is approved when the token URL is clicked.

 Max 5 notes per address per day. Or x notes per domain/IP per day..
 
 x notes per domain/IP per day will for sure not work. Think of people
 behind proxies
 
 We should not limit the notes per day. To much to track, imho, no?

I suspect that these spammers would just register example.com and create
[EMAIL PROTECTED] [EMAIL PROTECTED] etc.

 Yes, the evil side COULD be automated, but it's a lot more difficult
 than a simple post.
 
 I like this proposal, but Nuno's point stands: who's gonna implement that?

Not sure. (-:
I'd love to find time to do it, but I don't have it right now.

Either way, notes are a mess.

S


Re: [PHP-DOC] Re: [PHP-NOTES] Note spam

2006-03-23 Thread Friedhelm Betz

Sean Coates wrote:

Do we need to approve? I guess we have not enough man-power for that.
Simply post the note after we receive the token.


That's what I meant. Note is approved when the token URL is clicked.


Ah, sorry, my misunderestimating or something this way ;-)


Max 5 notes per address per day. Or x notes per domain/IP per day..

x notes per domain/IP per day will for sure not work. Think of people
behind proxies

We should not limit the notes per day. To much to track, imho, no?


I suspect that these spammers would just register example.com and create
[EMAIL PROTECTED] [EMAIL PROTECTED] etc.


Yes, possible, but we can see and implement upperbound limit later ;-)




Yes, the evil side COULD be automated, but it's a lot more difficult
than a simple post.

I like this proposal, but Nuno's point stands: who's gonna implement that?


Not sure. (-:
I'd love to find time to do it, but I don't have it right now.

Either way, notes are a mess.


Yes.

Friedhelm


[PHP-DOC] cvs: phpdoc /en/reference/outcontrol/functions ob-get-flush.xml

2006-03-23 Thread Jean-S�bastien Goupil
jsgoupilFri Mar 24 02:44:11 2006 UTC

  Modified files:  
/phpdoc/en/reference/outcontrol/functions   ob-get-flush.xml 
  Log:
  Typo
  
http://cvs.php.net/viewcvs.cgi/phpdoc/en/reference/outcontrol/functions/ob-get-flush.xml?r1=1.3r2=1.4diff_format=u
Index: phpdoc/en/reference/outcontrol/functions/ob-get-flush.xml
diff -u phpdoc/en/reference/outcontrol/functions/ob-get-flush.xml:1.3 
phpdoc/en/reference/outcontrol/functions/ob-get-flush.xml:1.4
--- phpdoc/en/reference/outcontrol/functions/ob-get-flush.xml:1.3   Fri Mar 
11 16:11:51 2005
+++ phpdoc/en/reference/outcontrol/functions/ob-get-flush.xml   Fri Mar 24 
02:44:11 2006
@@ -1,5 +1,5 @@
 ?xml version='1.0' encoding='iso-8859-1'?
-!-- $Revision: 1.3 $ --
+!-- $Revision: 1.4 $ --
   refentry id=function.ob-get-flush
refnamediv
 refnameob_get_flush/refname
@@ -13,7 +13,7 @@
  typestring/typemethodnameob_get_flush/methodname
  void/
 /methodsynopsis
-parafunctionob_get_flush/function flushs the output buffer, return
+parafunctionob_get_flush/function flushes the output buffer, return
  it as a string and turns off output buffering.
  functionob_get_flush/function returns false; if no buffering is
  active.