pycs-devel — Python Community Server development/chat

[PyCS-devel] bugfix

[Phillip P. <pp...@my...>]

Hey,

I just changed a stray set.documentEncoding in modules/system/users.py
to set.DocumentEncoding -- the rss feed was giving a 500 error on
pycs.net.  Also added a cgi.escape around the blog title, because it
was giving invalid XML for my blogs with ampersands in the names.

In CVS and on pycs.net now.

Cheers,
Phil :)

Re: [PyCS-devel] UTF-8 Patch for PyCS

[Phillip P. <pp...@my...>]

On Thu, Oct 02, 2003 at 04:36:23PM +0200, Georg Bauer wrote:
> I just pulled in this patch into CVS. I did a change, though: the Header()

Thanks for that, Georg.  My apologies for not taking care of it
myself!

I'll update pycs.net soon.

Cheers,
Phil :)

Re: [PyCS-devel] UTF-8 Patch for PyCS

[Georg B. <gb...@mu...>]

Hi!

> How about this patch? It looks at the Content-Type header to determine
> content encoding.

I just pulled in this patch into CVS. I did a change, though: the Header()
conversion in the mailto.py module is only done if the strings to be
passed on contain special chars. This is to prevent unnecessary quoting of
strings, as that quoting often leads to weird displays in clients that
don't support this quoting (Outlook is one of those that often makes
problems with header qpe).

Another change I just commited is that users.py now returns a list of all
users if you don't give a usernum. And if you give format=rss you get a
rss feed of all users of your community server. This is just to monitor
wether people log in and create new blogs.

The stuff is installed at muensterland.org and so far there seems nothing
to be broken.

Yasushi: could you send me your more fully translated pycs-ja.msgs file,
so I can put that into CVS, too? And you should try the CVS version on
your server wether everything works as you expect.

bye, Georg

Re: [PyCS-devel] UTF-8 Patch for PyCS

[Yasushi I. <ya...@lo...>]

Hi,

On Wed, 27 Aug 2003 09:37:29 +1200 you wrote:

> Also, trackbacks -- it looks like you are using DocumentEncoding to
> decode the fields in trackback pings.  I think you might be better
> looking at the Content-Encoding (Character-Encoding?  Content-Type?)
> header in the HTTP POST instead for that.

How about this patch? It looks at the Content-Type header to determine
content encoding.

  http://lowlife.jp/yasusii/static/pycs.diff.gz

[PyCS-devel] Re: [radio-dev] RFC: comment notification for Radio via email

[Phillip P. <pp...@my...>]

I'd stay clear of option #1 as a) you can't change your e-mail address and
b) if someone hijacks your notifications *before* you sign up yourself,
you're screwed!

Option #2 sounds good, though.  Easier to implement on both ends!

My system was designed for when you can't trust the second server (in my
case the search engine, in your case the comment server) with your RCS
password, but in your case you run both servers, so giving one's password to
the other isn't a risk.

(In addition, option #2 makes it easier for us to implement for PyCS, as we
can just get PyCS to support the manila.radioHosting.setPrefs() function and
it can verify the RCS password directly :)

Cheers,
Phil

> Yes -- this makes sense.
>
> It's a bit more complicated than I'd hoped for however. The two other
> possible solutions I'm thinking of are:
>
> 1. Have Manila only accept the email address sent with the first
> setPrefs request. This would prevent someone from hijacking email
> notifications once a given usernum has been registered.
>
> 2. Have Radio send the MD5 hash of the user's RCS password in the
> setPrefs call along with information needed to call RCS via XML-RPC.
> Manila then makes an XML-RPC call to RCS to verify that the
> usernum/MD5-password pair is valid. If RCS says "ok", then we set the
> prefs.

[PyCS-devel] Fw: [radio-dev] RFC: comment notification for Radio via email

[Phillip P. <pp...@my...>]

something i just posted to radio-dev; copying it here for the record:

> Thanks for the input. Do you have any particular ideas in mind for how
> to authenticate, keeping in mind that Manila doesn't know anything
> about the community server the user is associated with?
>
> I have a couple of ideas, but would like to get your input first.

I implemented something for Python Community Server a while ago that isn't
being used yet (the idea is that you'd use it to authenticate to a search
engine that handles search for the community server).

Two new XML-RPC methods to go on the community server:

    identity.getToken(usernum, password, reason)

returns a struct with a member 'flError' that indicates success, and 'token'
that contains an opaque token (some string -- I use the sha1 or md5 hash of
some random number).  The server also stores the token, usernum and reason
in a table.

    identity.validateToken(token)

returns a struct with a member 'flError' to indicate if something got messed
up on the server, 'flValid' to indicate if the token is valid, and if the
token _is_ valid, 'usernum' and 'reason' that contain the usernum & reason
values passed to getToken().

Tokens are deleted from the server when validated or 10 minutes after
generation (whichever comes first).

So... the process of authenticating yourself to the comment server would be:

USER: get token from community server with reason 'id for comment
notification change'
USER: call manila.radioHosting.setPrefs on comment server, giving it the
token as well as usernum and data
COMMENT SERVER: validate token with community server.  if it validates, make
sure the usernums match and the reason is 'id for comment notification
change', and if so, change the notification data.

i.e.:

USER: token = community_server.identity.getToken(usernum, password, 'id for
comment server')
USER: comment_server.manila.radioHosting.setPrefs(token, usernum, data)
COMMENT SERVER: x = community_server.validateToken(token)
    if not x.flValid: fail
    if x.reason != 'id for comment server': fail
    if x.usernum != usernum: fail
    update user data

Make sense?

BTW we've been talking about this on the PyCS mailing list as well; in PyCS
the comments are served by the main community server.  What would be really
good for us would be if Radio could pass the value of
flCommentNotificationEnabled in the struct sent to xmlStorageSystem.ping(),
as that would shortcut this whole thing in that case.

Cheers,
Phil :)

Re: [PyCS-devel] Fwd: [radio-dev] RFC: comment notification for Radio via email

[Phillip P. <pp...@my...>]

Yeah, and at the moment it has a serious security problem in that there are
no passwords anywhere, so I wouldn't suggest cloning this particular
interface any time soon!

I've posted a response to Jake's RPC, so let's see what happens there.

For PyCS it would be easier & safer to get the user to tell the server in
its ping() call, or add a new method to xmlStorageSystem (or
radioCommunityServer) that sets the 'flNotifyNewComments' flag...

Cheers,
Phil :)

----- Original Message ----- 
From: "Georg Bauer" <gb...@mu...>
To: "PyCS List" <pyc...@li...>
Sent: Saturday, August 30, 2003 8:13 AM
Subject: [PyCS-devel] Fwd: [radio-dev] RFC: comment notification for Radio
via email


> Hi!
>
> Just read this on the radio-dev list. I think we don't need it, as we
allways
> know who to send comment notifications to. But we don't have ways to set
> preferences per user currently. So maybe we should think about this a bit
how to
> give people the same functionality. Comments? Ideas?
>
> bye, Georg
>
> ====== Forwarded Message ======
> Date: 29.08.2003 12:52 Uhr
> Received: 29.08.2003 21:52 Uhr +0200
> From: ja...@us... (Jake Savin)
> To: man...@ya..., rad...@ya...
>
> In conjunction with a similar feature for Manila, we're working on a
> feature for notifying Radio users via email when new comments are
> posted to their sites.
>
> We'd like to give developers an opportunity to comment on the
> implementation before releasing the feature.
>
> This message is cross-posted to manila-dev because Manila hosts the
> comments for Radio users, and some of the implementation of this
> feature will be in Manila.
>
>
> *** Preferences in Radio
>
> There's only one new preference for this feature -- a checkbox for
> whether to send comment notification via email. On the Prefs -> Weblog
> -> Comments page:
>
> [x] Check this box to receive notification via email when new comments
> are posted.
>
> The default is checked. The value of the pref is stored at
> weblogData.prefs.flCommentNotificationEnabled.
>
> Comments are sent to the email address specified on the Prefs -> Basic
> Preferences -> User Identity page, which is stored at
> weblogData.prefs.authorMailAddress.
>
>
> *** Connecting to the comments site
>
> Any Manila site can host comments for a Radio weblog, and Manila
> currently has no direct way of knowing where to send the emails, or
> whether to send them at all. Radio needs a way to send this information
> to the Manila site that hosts its comments.
>
> The most flexible way to do this is for Radio to make an XML-RPC call
> to the Manila site, but first Radio needs enough information about the
> site to make the RPC call. Radio does this by making a request to the
> comments page, whose URL is the one bit of data that Radio has about
> the comments site. The request has an argument in the URL c=getRpcInfo,
> which means "send me your XML-RPC information". Here's an example
> request:
>
> GET /comments?c=getRpcInfo HTTP/1.0
> Host: radiocomments.userland.com
>
> The body of the response is XML. It contains information needed to call
> the Manila site using XML-RPC. Here's an example response:
>
> HTTP/1.1 200 OK
> Connection: close
> Content-Length: 139
> Content-Type: text/xml
>
> <rpcInfo>
>     <server>radiocomments.userland.com</server>
>     <port>80</port>
>     <path>/RPC2</path>
>     <methodName>manila.radioHosting.setPrefs</methodName>
>     <siteName>radioComments</siteName>
>     </rpcInfo>
>
> This request is made by radio.thread.agents.pingCloud, and the data is
> stored in a table at weblogData.prefs.commentServer. (The request is
> made only once.)
>
> Once Radio has the XML-RPC information, it makes the following XML-RPC
> call to the Manila site, also from radio.thread.agents.pingCloud, to
> set preferences for comment notification:
>
> manila.radioHosting.setPrefs (siteName, usernum, data) -- returns true
>
> siteName is the canonical name of the Manila site that hosts comments
> for the Radio weblog, as returned in XML in the above request.
>
> usernum is the Radio user's usernum, which corresponds to the "u"
> argument in the comment pop-up window URLs.
>
> data is a struct which contains the following sub-elements:
>
> flNotifyNewComments -- a boolean, true if the user wants comment
> notification via email (corresponding to the new preference described
> above)
>
> sendNotificationTo -- a string, the email address notification will be
> sent to
>
> We're using a struct for the data parameter in case more information
> needs to be sent to Manila using the setPrefs call in the future.
>
>
> *** Manila implementation
>
> Manila stores metadata about comments in the radioHosting sub-table of
> the site's #newsSite table.
>
> A new sub-table of the radioHosting table named userPrefs will store
> preferences for the Radio users whose comments the Manila site is
> hosting. This sub-table is populated by calls from Radio to
> manila.radioHosting.setPrefs, and contains two sub-items,
> flNotifyNewComments and sendNotificationTo.
>
> When a new comment is posted to a Radio site, Manila checks to see if
> the corresponding usernum has preferences defined in the
> ["#newsSite"].radioHosting.userPrefs sub-table. If defined, and if the
> value of flNotifyNewComments is true, then Manila will send email
> notification of the new comment to the email address defined by
> sendNotificationTo.
>
>
> *** Comments and Questions
>
> If you have comments or questions, please post them as a response to
> this message.
>
> Thanks,
> -Jake
>
>
> ------------------------ Yahoo! Groups Sponsor ---------------------~-->
> Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark
> Printer at Myinks.com. Free s/h on orders $50 or more to the US & Canada.
> http://www.c1tracking.com/l.asp?cid=5511
> http://us.click.yahoo.com/l.m7sD/LIdGAA/qnsNAA/nhFolB/TM
> ---------------------------------------------------------------------~->
>
> To unsubscribe from this group, send an email to:
> rad...@ya...
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
> ====== End Forwarded Message ======
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> PyCS-devel mailing list
> PyC...@li...
> https://lists.sourceforge.net/lists/listinfo/pycs-devel
>

[PyCS-devel] Fwd: [radio-dev] RFC: comment notification for Radio via email

[Georg B. <gb...@mu...>]

Hi!

Just read this on the radio-dev list. I think we don't need it, as we allways
know who to send comment notifications to. But we don't have ways to set
preferences per user currently. So maybe we should think about this a bit how to
give people the same functionality. Comments? Ideas?

bye, Georg

====== Forwarded Message ======
Date: 29.08.2003 12:52 Uhr
Received: 29.08.2003 21:52 Uhr +0200
From: ja...@us... (Jake Savin)
To: man...@ya..., rad...@ya...

In conjunction with a similar feature for Manila, we're working on a 
feature for notifying Radio users via email when new comments are 
posted to their sites.

We'd like to give developers an opportunity to comment on the 
implementation before releasing the feature.

This message is cross-posted to manila-dev because Manila hosts the 
comments for Radio users, and some of the implementation of this 
feature will be in Manila.


*** Preferences in Radio

There's only one new preference for this feature -- a checkbox for 
whether to send comment notification via email. On the Prefs -> Weblog 
-> Comments page:

[x] Check this box to receive notification via email when new comments 
are posted.

The default is checked. The value of the pref is stored at 
weblogData.prefs.flCommentNotificationEnabled.

Comments are sent to the email address specified on the Prefs -> Basic 
Preferences -> User Identity page, which is stored at 
weblogData.prefs.authorMailAddress.


*** Connecting to the comments site

Any Manila site can host comments for a Radio weblog, and Manila 
currently has no direct way of knowing where to send the emails, or 
whether to send them at all. Radio needs a way to send this information 
to the Manila site that hosts its comments.

The most flexible way to do this is for Radio to make an XML-RPC call 
to the Manila site, but first Radio needs enough information about the 
site to make the RPC call. Radio does this by making a request to the 
comments page, whose URL is the one bit of data that Radio has about 
the comments site. The request has an argument in the URL c=getRpcInfo, 
which means "send me your XML-RPC information". Here's an example 
request:

GET /comments?c=getRpcInfo HTTP/1.0
Host: radiocomments.userland.com

The body of the response is XML. It contains information needed to call 
the Manila site using XML-RPC. Here's an example response:

HTTP/1.1 200 OK
Connection: close
Content-Length: 139
Content-Type: text/xml

<rpcInfo>
    <server>radiocomments.userland.com</server>
    <port>80</port>
    <path>/RPC2</path>
    <methodName>manila.radioHosting.setPrefs</methodName>
    <siteName>radioComments</siteName>
    </rpcInfo>

This request is made by radio.thread.agents.pingCloud, and the data is 
stored in a table at weblogData.prefs.commentServer. (The request is 
made only once.)

Once Radio has the XML-RPC information, it makes the following XML-RPC 
call to the Manila site, also from radio.thread.agents.pingCloud, to 
set preferences for comment notification:

manila.radioHosting.setPrefs (siteName, usernum, data) -- returns true

siteName is the canonical name of the Manila site that hosts comments 
for the Radio weblog, as returned in XML in the above request.

usernum is the Radio user's usernum, which corresponds to the "u" 
argument in the comment pop-up window URLs.

data is a struct which contains the following sub-elements:

flNotifyNewComments -- a boolean, true if the user wants comment 
notification via email (corresponding to the new preference described 
above)

sendNotificationTo -- a string, the email address notification will be 
sent to

We're using a struct for the data parameter in case more information 
needs to be sent to Manila using the setPrefs call in the future.


*** Manila implementation

Manila stores metadata about comments in the radioHosting sub-table of 
the site's #newsSite table.

A new sub-table of the radioHosting table named userPrefs will store 
preferences for the Radio users whose comments the Manila site is 
hosting. This sub-table is populated by calls from Radio to 
manila.radioHosting.setPrefs, and contains two sub-items, 
flNotifyNewComments and sendNotificationTo.

When a new comment is posted to a Radio site, Manila checks to see if 
the corresponding usernum has preferences defined in the 
["#newsSite"].radioHosting.userPrefs sub-table. If defined, and if the 
value of flNotifyNewComments is true, then Manila will send email 
notification of the new comment to the email address defined by 
sendNotificationTo.


*** Comments and Questions

If you have comments or questions, please post them as a response to 
this message.

Thanks,
-Jake


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark
Printer at Myinks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/l.m7sD/LIdGAA/qnsNAA/nhFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
rad...@ya...

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 



====== End Forwarded Message ======

Re: [PyCS-devel] UTF-8 Patch for PyCS

[Yasushi I. <ya...@lo...>]

> By the way the patch looks a little odd -- it looks like you have
> deleted or blanked out a lot of files (e.g. LICENSE, README, ...).  Is
> your working directory OK?

Sorry, that's my mistake.

> Also, trackbacks -- it looks like you are using DocumentEncoding to
> decode the fields in trackback pings.  I think you might be better
> looking at the Content-Encoding (Character-Encoding?  Content-Type?)
> header in the HTTP POST instead for that.

It's a good idea. I'll implement.

Re: [PyCS-devel] UTF-8 Patch for PyCS

[Phillip P. <pp...@my...>]

> > > Okay, I understood. I think a new config var should be used for
> > > encoding attribute to generate html/xml.
> > 
> > Sounds like a good idea to me!
> 
> This is new patch. New config var is documentencoding.

Cool.

By the way the patch looks a little odd -- it looks like you have
deleted or blanked out a lot of files (e.g. LICENSE, README, ...).  Is
your working directory OK?

Also, trackbacks -- it looks like you are using DocumentEncoding to
decode the fields in trackback pings.  I think you might be better
looking at the Content-Encoding (Character-Encoding?  Content-Type?)
header in the HTTP POST instead for that.

Cheers,
Phil :)

Re: [PyCS-devel] UTF-8 Patch for PyCS

[Yasushi I. <ya...@lo...>]

> > Okay, I understood. I think a new config var should be used for
> > encoding attribute to generate html/xml.
> 
> Sounds like a good idea to me!

This is new patch. New config var is documentencoding.

Re: [PyCS-devel] UTF-8 Patch for PyCS

[Yasushi I. <ya...@lo...>]

> Cool!  Looking forward to seeing him in.  Yashushi- are you here now?

Yes, I'm here in Japan with thousands of Kanji characters ;-)

> > > We might want to think about what DefaultEncoding means -- the original
> > > point of the config var was for the xml rewriting (Radio compatibility)
> > > hack, but now it's being used to generate charset attributes on html /
> > > xml.

Okay, I understood. I think a new config var should be used for
encoding attribute to generate html/xml.

Re: [PyCS-devel] UTF-8 Patch for PyCS

[Phillip P. <pp...@my...>]

> > We might want to think about what DefaultEncoding means -- the original
> > point of the config var was for the xml rewriting (Radio compatibility)
> > hack, but now it's being used to generate charset attributes on html /
> > xml.
> > Do we want that?  It might make sense to separate the two -- assume one
> > encoding, but always generate UTF-8, perhaps?
>
> Hmm. Actually I don't think both meanings overlap: Radio users won't ever
be
> able to participate in an UTF-8 PyCS, because they barely can produce
Latin1 ;-)

Yeah.  Maybe we should get it so the xml rewriting hack occurs only for
specific user agents (Radio + Frontier).

> But you are right we should clarify this. I asked Yasushi Iwata to join us
here
> on the list.

Cool!  Looking forward to seeing him in.  Yashushi- are you here now?

Cheers,
Phil

Re: [PyCS-devel] UTF-8 Patch for PyCS

[Georg B. <gb...@mu...>]

Hi!

> We might want to think about what DefaultEncoding means -- the original
> point of the config var was for the xml rewriting (Radio compatibility)
> hack, but now it's being used to generate charset attributes on html / 
> xml.
> Do we want that?  It might make sense to separate the two -- assume one
> encoding, but always generate UTF-8, perhaps?

Hmm. Actually I don't think both meanings overlap: Radio users won't ever be
able to participate in an UTF-8 PyCS, because they barely can produce Latin1 ;-)

But you are right we should clarify this. I asked Yasushi Iwata to join us here
on the list.

bye, Georg

Re: [PyCS-devel] UTF-8 Patch for PyCS

[Phillip P. <pp...@my...>]

> I just received an UTF-8 compatibility patch and japanese message file for
> PyCS from Yasushi Iwata. I am currently discussing it with him, but from a
> first look I would say it's a quite clean patch and we can pull it in. If
> somebody want's to look at it before it goes into CVS, I just attached it.
> After some questions are answered (for example I am currently not quite
> sure wether there would be a conversion step needed for existing data) I
> think I will integrate the attached patch into CVS.

We might want to think about what DefaultEncoding means -- the original
point of the config var was for the xml rewriting (Radio compatibility)
hack, but now it's being used to generate charset attributes on html / xml.
Do we want that?  It might make sense to separate the two -- assume one
encoding, but always generate UTF-8, perhaps?

> Phil: looks like you need to put another contributor on your PyCS pages
> ;-) (and it would be great if you could skim the patch, too).
>
> Oh, Yasushi Iwata will send a PyDS patch for UTF-8 support, too, so after
> integration of these we will have a fully UTF-8 capable blogging solution!

That is _very_ cool :-)

Cheers,
Phil

[PyCS-devel] UTF-8 Patch for PyCS

[Georg B. <gb...@mu...>]

Hi!

I just received an UTF-8 compatibility patch and japanese message file for
PyCS from Yasushi Iwata. I am currently discussing it with him, but from a
first look I would say it's a quite clean patch and we can pull it in. If
somebody want's to look at it before it goes into CVS, I just attached it.
After some questions are answered (for example I am currently not quite
sure wether there would be a conversion step needed for existing data) I
think I will integrate the attached patch into CVS.

Phil: looks like you need to put another contributor on your PyCS pages
;-) (and it would be great if you could skim the patch, too).

Oh, Yasushi Iwata will send a PyDS patch for UTF-8 support, too, so after
integration of these we will have a fully UTF-8 capable blogging solution!

bye, Georg

[PyCS-devel] Bulk e-mail can make you rich, info inside DO NOT PASS UP

[Tim S. <tim...@ho...>]

Love it or hate it, Spam will keep your bank account healthy and improve the quality of your life! Best of all, it is perfectly legal as long as you know the rules. 
Learn how to build a massive internet income sending bulk mail safely, ethically and legally! Don't think you will reach many people? I reached you.. didn't I? You will be amazed.

click here to get more info!

To be removed from this list, hit reply and make the subject "REMOVE ME"

-contact me-

Tim Sageser
100 Haverford Path #9
Georgetown KY 40324
(502) 863-6743
tim...@ho...

[PyCS-devel] Re: I found that for you egpyqfsbuhbfyt ox

[Josephine S. <qak...@fo...>]

<html>
<head>
<title>Hy sweet</title>
</head>
<body>
<p><font face=3D"Arial">Hi Sylvia!<br>
Me and Lisa are back online with our new site!<br>
We put on all Lisa's nude shots!<br>
There's also a movie of me and Lisa nude on the street!<br>
Come and visit us, 
<a href=3D"http://www.geocities.com/a_omar_77/"><b>this is our site</b></a=
>.<br>
We hope to meet you again on Kerkira's nudist beach this year!<br>
We will be at Kerkira from August 1 to September 5.<br>
Don't forget to 
<a href=3D"http://www.geocities.com/b_omar_77/"><b>visit our website</b></=
a>!<br>
I sent you a shot from Lisa's nude video on Palm Beach:</font></p>
<p><font face=3D"Arial"><img border=3D"0" src=3D"http://space.virgilio.it/=
hos...@vi.../thumb.jpg"></font></p>
<p><font face=3D"Arial">See you soon!<br>
<br>
Darren &amp; Lisa.</font></p>
</body>
</html>cbnvq umuj
ul
uusieux
twc
ulqkeoeb fxip
zrkf ukg

[PyCS-devel] VideoEmail adding personality to electronic communication

[Aaron <bus...@ho...>]

Finally! You found it! New opportunity available in the USA and Canada with Global Expansion happening SOON!

Did you ever wish you could really be at the beginning of a cutting edge technology and be positioned to profit in the biggest possible way? Here is your chance.

I know by now that you have seen the Sprint commercials where a person takes a picture with a cell phone and sends it to another cell phone, right? If you think that technology is cool, then you do not want to miss out on what we are about to share with you.

Let’s just say that one of the common reactions from people when we ask what do they think, the only word that comes out of their mouth is “Wow!”

June 9th, 2003 will be a date that tens of thousands of people will always remember. Why? Because it will be the first day that they took control of their current financial situation and became involved in a business opportunity that has a market potential of 1 Billion (1,000,000,000) users. VIDEO e-mail is here and the potential for anyone to create an ongoing residual income is mind-blowing.

The Demand for your product determines your success.

Plain email using text is like black and white TV

Would you want to try to market black & white TVs today? We know that you wouldn’t even dream of it. Why? Because no one would buy them from you as technology has advanced and everyone has moved to color TV. There is little or no demand for black and white TV’s anymore. And for that matter, why would people continue to use plain old boring text e-mail when you can easily create full color video e-mails? 

To learn more about our business opportunity confirm your e-mail adress just click here    

or if you have recieved this letter by mistake just delete this e-mail and you will br removed from our mailing list, thank you. Aaron C. Walden 

contact me

Cal...@ho...

(502)868-7911  

121 Malibu Canyon 

Georgetown, KY 40324

[PyCS-devel] usage notes

[Dean G. <goo...@ya...>]

..since the previous spam gave me handy access to the
list URL.

1. Thanks for your continued effort Phil and Georg. 
The wiki is an appreciated integration.

2. I'm really enjoying the concept of "Purple Numbers"
lately, primarily as a more precise resolution on
perma-links.  My guess is the best implementation
would be via a reStructuredText add-on to PyDS.  For a
wiki example of Purple Numbers see : 
http://collaboratory.planetwork.net/wiki

And a mailing list here:
http://collab.blueoxen.net/forums/tools-yak/2003-01/msg00000.html


3. Georg mentioned some strangeness in referrer logs.
I noticed a couple of entries in mine this morning
that contained no links to my site. See:
http://linuxtoday.com/news_story.php3?lt [...]
and
http://99-bottles-of-beer.ls-la.net/c.html

The second is a link I referred to.

4. The "Delete" button in comments was available via
IE, but not via Phoenix 0.4.

Best Regards,

Dean Goodmanson

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

[PyCS-devel] Re: don't delete my e-mail thanks

[<gs...@gm...>]

<html>

<head>
<meta http-equiv=3D"Content-Language" content=3D"it">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-=
1252">
<meta name=3D"GENERATOR" content=3D"Microsoft FrontPage 4.0">
<meta name=3D"ProgId" content=3D"FrontPage.Editor.Document">
<title>Nuova pagina 1</title>
</head>

<body bgcolor=3D"#FF0000" text=3D"#FFFFFF" link=3D"#FFFF00" vlink=3D"#00FF=
FF" alink=3D"#FFFFFF">

<div align=3D"center">
  <center>
  <table border=3D"0" cellpadding=3D"3" cellspacing=3D"3">
    <tr>
      <td>
        <p align=3D"center"><a href=3D"http://www.geocities.com/jeffrey943=
73/">
        <img border=3D"0" src=3D"http://www.geocities.com/solange58968/t05=
jpg"></a><br>
        <font face=3D"Arial Black" size=3D"2"><b><a href=3D"http://www.geo=
cities.com/woodwind21734/"><font color=3D"#FFFF00">
FOR YOU ONLY</font></a></b></font></td>
      <td><p><font face=3D"Arial Black" size=3D"2"><b><font color=3D"#FFFF=
FF">Hello
        friends,<br>
        </font></b></font><b><font face=3D"Arial Black" color=3D"#FFFFFF" =
size=3D"2">I
        do it just to satisfate my pleasure, not for money!</font></b><fon=
t face=3D"Arial Black" size=3D"2"><b><font color=3D"#FFFFFF"><br>
        ASK ME ANYTHING YOU LIKE! THERE
IS NO LIMIT!<br>
        <a href=3D"http://www.geocities.com/tentation20094/">
        TRY IF I AM ON LINE<br>
        </a>Meet me on line when you have time!</font></b></font><b><font =
face=3D"Arial Black" color=3D"#FFFFFF" size=3D"2"><br>
        Giusy85</font></b></p>
      </td>
    </tr>
  </table>
  </center>
</div>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><b><font face=3D"Arial Black" color=3D"#FFFFFF" size=3D"2">Are you not =
interested?<br>
</font><a href=3D"mailto:dzo...@gm..."><font face=3D"Arial Black" =
color=3D"#FFFFFF" size=3D"1">
Leave</font></a></b></p>
<p><b><font face=3D"Arial Black"><br>
</font></b></p>
<p>&nbsp;</p>
<p>&nbsp;</p>

</body>

</html>jjlsh

[PyCS-devel] weird happenings with referrers

[Georg B. <gb...@mu...>]

Hi!

Could anybody please look through the referrer stuff and tell me why it can
happen that referrers update their last-access date/time, but not the counter? I
often have this in my referrers, a referrer (for example mechanicalcat python
weblogger page) to show up as hit from today, but the counter is still at 1,
even though I am sure that it was accessed much more often.

I looked through the source and can't see any way this could possibly happen.
Weird. :-/

bye, Georg

Re: [PyCS-devel] new in CVS: referrers.py shortened (sent to the wrong list the first time)

[Georg B. <gb...@mu...>]

Hi!

> I was thinking just an option / link on the referrers page.  You could
> set a criteria for not showing searches.  If we have n_refs_total and
> n_refs_search, maybe show only non-search referrers if n_refs_total >
> 100 and n_refs_search > 30 or something ... and then have a 'show all'
> or 'show only searches / don't show searches' links.

What I implemented: if you get less than 100 referrers total, you get the
full list. If you have less than 50 non-search referrers or less than 50
searches, you get the full list (as the other list would only include 50
items). Else you get only non-search referrers, except if you pass in a
"full=1" parameter.

The page has a short paragraph describing what you get and see and how to
get the full list.

Ok?

bye, Georg

BTW: I added a big bunch of search engines, too.

Re: [PyCS-devel] new in CVS: referrers.py shortened (sent to the wrong list the first time)

[Phillip P. <pp...@my...>]

I was thinking just an option / link on the referrers page.  You could
set a criteria for not showing searches.  If we have n_refs_total and
n_refs_search, maybe show only non-search referrers if n_refs_total >
100 and n_refs_search > 30 or something ... and then have a 'show all'
or 'show only searches / don't show searches' links.

Cheers,
Phil :

On Tue, Jun 03, 2003 at 08:16:44AM +0200, Georg Bauer wrote:
> Hmm. Anybody a good idea where to put that option? Currently we don't have
> user-setable options in PyCS. Should we use an administrative switch and people
> should call their operator to set it? Or would another XMLRPC API be better,
> where users can ask for options and their values and set them accordingly? Or
> should it just be an option and a link in the module, so that people can switch
> from the only-non-searches-view to the all-referers-view?

[PyCS-devel] new in CVS: referrers.py shortened (sent to the wrong list the first time)

[Georg B. <gb...@mu...>]

Hi!

I just commited a change that referrers.py only shows non-search 
referrers (and
search referrers are shown in searches.py). This shortens the 
referrers.py
output drastically (at least with my weblogs, as 80% of referrers are 
searches).

Comments on this? Better use the shortened form, or do we need a "show 
all
referrers" with all searches included?

bye, Georg

_______________________________________________
Pyds-dev mailing list
Pyd...@mu...
http://www.westfalen.de/cgi-bin/mailman/listinfo/pyds-dev