pycs-devel archive weblog

A blog for archiving the pycs-devel mailing list

SunMonTueWedThuFriSat
1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30

python community server
pycs developers
also available in XML
Copyright (c) 2002 Phillip Pearson
spread the dot

2002-11-28

Dean Goodmanson: Re: [PyCS-devel] Feature: comment admin user

Thanks for the details, the blog will appreciate it.



I've used the comment management. Very nice.



> The new extension lets a sysop do the same thing for

> all blogs ...



In specific, I was trying to point +1 the feature.



Feel free, as Sysop of PyCS, to bit-bucket any

comments you see on my site that are as I described.



The whole google locale issues was absense of rtfs

(and other things ;O) on my part.



- Dean

Phillip Pearson: Re: [PyCS-devel] Feature: comment admin user

> Good point.

>

> Personally, I like the thought of a Sysop blasting

> rogue comments on my blog: Spam, Double click dual

> posts, horrendously innapropriate, etc.



BTW, you can do that too. It's not documented, but if you visit the

following url:



http://www.pycs.net/system/login.py



... and log in with the e-mail address and password you gave Radio

when you created the blog, then go back to a comment page on your

blog, you should see a 'Delete' button under each comment.



The new extension lets a sysop do the same thing for all blogs ...



> p.s. All of the Google referrer links on pycs.net

> point to google.de ;-) At first I thought I was

> actually getting hits from Germany searches, but later

> remembered the implementation context. Phil, would

> you mind switching PyCS over to google.com ? Might

> need to check with Martin Gerber, though...I can live

> with it if it's handy to him. Killer feature, btw.

> Next week I'll post some referrers for AllTheWeb.com

> and Vivisimo.com for analysis.



Martin's already answered this one, but I think you really are getting

search hits from Germans ;-)



The search tracking page just looks for referrers with 'google' (and

various other things) in them. Check out pycs.net/sqr/referrers.html

for a really detailed analysis of your hits.



Cheers,

Phil :)

Georg Bauer: Re: [PyCS-devel] Feature: additional search engines supported



Hi!



> Oh, I just checked in a little patch to searches.py so that it now

> recognizes altavista searches. I actually didn't get any up to now, but

> Phil does, and so I thought it would be nice if they showed up in the

> list, too :-)



And MSN, too (as I got some from there).



bye, Georg

Georg Bauer: Re: [PyCS-devel] Feature: comment admin user

Hi!



> p.s. All of the Google referrer links on pycs.net

> point to google.de ;-) At first I thought I was

> actually getting hits from Germany searches, but later

> remembered the implementation context. Phil, would



Hmm? I don't think we have something in there that points explicitly to

google.de - it just takes the referrer from the http headers, that's

all. I just did a grep -r -i google.de on the source-tree and didn't

find any hardcoded google.de stuff (it might have happend, as I usually

would insert google.de automatically if I was to hardcode something like

that, just out of habit). I would say that you actually _do_ get hits by

german (or german IP range) searches :-)



Google does a bit of trickery: when your IP falls into some ranges, it

forcebly switches you over to google.de because of the censorship stuff

they implemented there (yes, we in germany get censored with google

search results!), so maybe you are bitten by this, as google seems to

switch a bit more IPs than is actually needed.



Or it just happens that I searched a _lot_ of stuff lately and that I

often stumbled over pycs.net and so it's just me ...



Oh, I just checked in a little patch to searches.py so that it now

recognizes altavista searches. I actually didn't get any up to now, but

Phil does, and so I thought it would be nice if they showed up in the

list, too :-)



bye, Georg

Dean Goodmanson: Re: [PyCS-devel] Feature: comment admin user

> Actually that would go nicely with my "BBS" theme,

> as we used to have

> several "sysops" to run the system. More finegrained

> control often isn't

> really needed - I see that every time with Zope, you

> very seldom use the

> full power of the authencation and rights mechanism,

> usually the

> "user <-> manager" type of distinction is more than

> enough.

>



Good point.



Personally, I like the thought of a Sysop blasting

rogue comments on my blog: Spam, Double click dual

posts, horrendously innapropriate, etc.



- Dean



p.s. All of the Google referrer links on pycs.net

point to google.de ;-) At first I thought I was

actually getting hits from Germany searches, but later

remembered the implementation context. Phil, would

you mind switching PyCS over to google.com ? Might

need to check with Martin Gerber, though...I can live

with it if it's handy to him. Killer feature, btw.

Next week I'll post some referrers for AllTheWeb.com

and Vivisimo.com for analysis.

Georg Bauer: Re: [PyCS-devel] Feature: comment admin user

Hi!



> has been working on: the ability to designate an 'admin user' who has

> the power to delete comments on all blogs.



Ah, good. I am still not back to normal speed, but I think I will sync

with CVS in the next days and will have a look at it.



> [btw, we've had three different authentication methods for ages now -

> time to try and merge them? or does it make sense to leave it as it

> is, with an 'overall admin password', per-blog logins for comments,

> and separate logins for viewing restricted pages...?]



Hmm. Are they really mergeable? The overall admin password is like some

external administrator, the guy who keeps stuff running. The per-blog

logins are in-system-administration within the limits of PyCS code. And

the separate logins for viewing restricted pages are for exactly that -

not blog based or user based, but based on the structure of the system.



Can we merge something diverse like that? Or would be better go and look

what mechanism to use for what stuff? I usually like web-integrated

administration for web systems, so I would put that stuff under the

login.py authentication. pycsadm on the other hand is for automatted

stuff, so I think it's ok to have it's own password - it's on it's own

sublevel in the innards of the machine, if you understand what I'm

saying. The only stuff where I currently (!! this might change) don't

have a use for is the authentication for restricted pages.



So I think with your first "admin" feature it's the right way. Only

difference is that I would like to have a flag in the user record that

you can set for example with pycsadm and say "this user is an admin".

Just to have more than one admin. And administrative stuff only works if

one of the admins first uses login.py and then visits the administrative

(or normal) pages.



Actually that would go nicely with my "BBS" theme, as we used to have

several "sysops" to run the system. More finegrained control often isn't

really needed - I see that every time with Zope, you very seldom use the

full power of the authencation and rights mechanism, usually the

"user <-> manager" type of distinction is more than enough.



bye, Georg