[CAAN] Request for Hierarchical Category List

  Would someone contribute a hierarchical list of categories to help CAAN 
to have the feature 'Browse by category'?

Thanks in advance.

CAAN - Citizens for the Abatement of Aircraft Noise
CAAN - Citizens for the Abatement of Aircraft Noise, Inc. If you're
a Washington DC metro resident who's tired of the all the airport ...
www.caan.org/ - 5k - 26 Dec 2002 - Cached - Similar pages

Canadian Aboriginal AIDS Network Index
Welcome to the. Canadian Aboriginal AIDS Network. Bienvenue
au. R�seau Canadien Autochtone du SIDA. Please choose.
Description: Provides leadership, support and advocacy for Aboriginal
people living with and affected by HIV or AIDS
Category: Society > Ethnicity > ... > Canadian > British Columbia
www.caan.ca/ - 3k - Cached - Similar pages




> "xern" <xer...@cpan.org> wrote in message
> news:Pin...@realTao.org...
>
> Would someone contribute a hierarchical list of categories
> to help CAAN to have the feature 'Browse by category'?
>
> Thanks in advance.
>


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.431 / Virus Database: 242 - Release Date: 17/12/2002

And what do you mean?

On Fri, 27 Dec 2002, Andrew Carpenter wrote:

> CAAN - Citizens for the Abatement of Aircraft Noise
> CAAN - Citizens for the Abatement of Aircraft Noise, Inc. If you're
> a Washington DC metro resident who's tired of the all the airport ...
> www.caan.org/ - 5k - 26 Dec 2002 - Cached - Similar pages
> 
> Canadian Aboriginal AIDS Network Index
> Welcome to the. Canadian Aboriginal AIDS Network. Bienvenue
> au. R嚙編eau Canadien Autochtone du SIDA. Please choose.
> Description: Provides leadership, support and advocacy for Aboriginal
> people living with and affected by HIV or AIDS
> Category: Society > Ethnicity > ... > Canadian > British Columbia
> www.caan.ca/ - 3k - Cached - Similar pages
> 
> > "xern" <xer...@cpan.org> wrote in message
> > news:Pin...@realTao.org...
> >
> > Would someone contribute a hierarchical list of categories
> > to help CAAN to have the feature 'Browse by category'?
> >
> > Thanks in advance.
> >
> 
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.431 / Virus Database: 242 - Release Date: 17/12/2002
> 
> 
> 

[lots of different CAAN's]

xern wrote:
> And what do you mean?

I think his point is that there are different things called CAAN.
Which are you talking about ?
What are you talking about ? please explain it for us clueless people.

- CeeJay

On Fri, 27 Dec 2002 22:02:08 +0100, "CeeJay" <new...@ceejay.cjb REMOVEthisSPAMfilterTOreply .net> wrote:

>[lots of different CAAN's]
>
>xern wrote:
>> And what do you mean?
>
>I think his point is that there are different things called CAAN.
>Which are you talking about ?
>What are you talking about ? please explain it for us clueless people.
>
>- CeeJay
>

CAAN in this case, "Comprehensive Ascii Art Network" 
http://realtao.org/caan/about.html

But is associated with any of the others listed in the previous
post or a stand alone project ?

Xern also wrote --

 "Would someone contribute a hierarchical list of categories to help CAAN 
to have the feature 'Browse by category'?"
-----------------------------------------------------------------------

I think the a few reason why no one may be incline to contribute yet

1. Selling or distributing E-mail address Found nothing saying
   it would or would not be done
2. Pre Pre alpha stage
3. Tis the season, its starting to wind down a bit

lgbeard

"lgbeard" <lgb...@bullreguard.nut> wrote in message
news:di0...@4ax.com...
> On Fri, 27 Dec 2002 22:02:08 +0100, "CeeJay" <new...@ceejay.cjb
REMOVEthisSPAMfilterTOreply .net> wrote:
>
> Xern also wrote --
>
>  "Would someone contribute a hierarchical list of categories to help CAAN
> to have the feature 'Browse by category'?"
> -----------------------------------------------------------------------
>
> I think the a few reason why no one may be incline to contribute yet
>
> 1. Selling or distributing E-mail address Found nothing saying
>    it would or would not be done
> 2. Pre Pre alpha stage
> 3. Tis the season, its starting to wind down a bit

This is mostly directed at Xern, and wanders a bit off topic.

I'm sort of in anti-spammer mode atm, so a few words on email addresses:

Decide if you really really need email addresses. If you do:

What you use the address for should be clearly stated on the site. Note that if
you sell or give addresses to anybody else, it's a very bad thing and will lose
you contributors, but state you do so. Communication to that address should be
limited to stuff related to the site. Any communication to the address beyond
what results directly from a users action on the site should require the user to
explicitly request it and default to off. e.g. they need to check a box to get
it (having to uncheck it is not acceptable and will probably result in you
getting more cries of spam then necessary)

Email addresses should *NOT* appear *ANYWHERE* without the person's explicit
consent. It should default to off and has the same requirements as above.

When someone signs up the system should send them a confirmation mail that they
have to either reply to or click a link before any further mail is sent (and it
would be sensible to not allow any additional web site access before
confirmation). This should use a strong unique token, but it must *NOT* be
derived from the email address. If a valid token can be created from any given
email address, spammers will abuse it.

If/when the site grows to a respectable size you are bound to get some
complaints about spam, misguided or otherwise. Make sure you have working
contact addresses to deal with complaints and you do so promptly. Hopefully
it'll never happen but it pays to be prepared :)

All that said, IMHO you probably should require valid email addresses, and the
above will go a long way to ensuring cries of spam are few and you have
validated email addresses for all users.

The site seems like a good idea to me. Though, I completely agree with what
lgbeard says above about its current state. These things don't happen overnight,
though, and I wish you luck :)

obascii: not very good, small can of spam
.----.
|----|
|SPAM|
`----'

Culpa mea est.
I have made an addendum about use of email address and other personal data.

- Your email address and other personal data are only used for account verification
and communication between CAAN and you. CAAN will NOT redistribute your personal data
or let them appear in any public area of CAAN without your explicit consent.

"xern" <xer...@cpan.org> wrote in message
news:Pin...@realTao.org...
> Culpa mea est.
> I have made an addendum about use of email address and other personal data.
>
> - Your email address and other personal data are only used for account
verification
> and communication between CAAN and you. CAAN will NOT redistribute your
personal data
> or let them appear in any public area of CAAN without your explicit consent.
>

Great :) How are you verifying email addresses, btw ?

T.

In fact, currently I just want to make sure that every user's email is 
valid. So, I send letters to each newly registered user. If I get bounces, 
I may think the registration is invalid. While it's preprealpha, I don't 
want to do in a verbose way. If no bounces, user's account is created.

On Sat, 28 Dec 2002, Tom Bampton wrote:
> 
> "xern" <xer...@cpan.org> wrote in message
> news:Pin...@realTao.org...
> > Culpa mea est.
> > I have made an addendum about use of email address and other personal data.
> >
> > - Your email address and other personal data are only used for account
> verification
> > and communication between CAAN and you. CAAN will NOT redistribute your
> personal data
> > or let them appear in any public area of CAAN without your explicit consent.
> >
> 
> Great :) How are you verifying email addresses, btw ?
> 
> T.
> 

"xern" <xer...@cpan.org> wrote in message
news:Pin...@realTao.org...
> In fact, currently I just want to make sure that every user's email is
> valid. So, I send letters to each newly registered user. If I get bounces,
> I may think the registration is invalid. While it's preprealpha, I don't
> want to do in a verbose way. If no bounces, user's account is created.

Please don't top post. A bounce can take upto or over 5 days to arrive for
addresses that are temporarily down. If you rely solely on that, when you
implement a "real" system for verifying mails, you should confirm all existing
addresses in the database before sending any additional mail to them. With your
system as it is now, anyone can enter anyone elses email address in there.
Whilst you dont intend it, anything sent to addresses not entered by the owner
*is* spam.

Like you say, it probably doesnt matter so much for now, but once it becomes
alpha or beta you'll need to make some changes :) Oh, one thing I forgot to
mention before, make sure you keep copies of all verifications and
registrations, including IP address of those enterring info in the form. This
way if/when someone complains you have the data there to present to them (and
from the IP it should be fairly obvious if the complainer has a legitimate
complaint or has just forgotten they did it).

T.

> Please don't top post.

Why not ???

BoD



Tom Bampton wrote:

"BoD" <Bo...@JRAF.org> wrote in message
news:3e0e4eaf$0$26166$626...@news.free.fr...
> > Please don't top post.
>
> Why not ???

Because it makes it harder to read the message. It reverses the natural flow of
conversation, requiring you to read the end before the beginning. It also pisses
off the majority of people reading Usenet.

On Sat, 28 Dec 2002, Tom Bampton wrote:
> 
> "xern" <xer...@cpan.org> wrote in message
> news:Pin...@realTao.org...
> > In fact, currently I just want to make sure that every user's email is
> > valid. So, I send letters to each newly registered user. If I get bounces,
> > I may think the registration is invalid. While it's preprealpha, I don't
> > want to do in a verbose way. If no bounces, user's account is created.
> 
> Please don't top post. A bounce can take upto or over 5 days to arrive for
> addresses that are temporarily down. If you rely solely on that, when you
> implement a "real" system for verifying mails, you should confirm all existing
> addresses in the database before sending any additional mail to them. With your
> system as it is now, anyone can enter anyone elses email address in there.
> Whilst you dont intend it, anything sent to addresses not entered by the owner
> *is* spam.
> 
> Like you say, it probably doesnt matter so much for now, but once it becomes
> alpha or beta you'll need to make some changes :) Oh, one thing I forgot to
> mention before, make sure you keep copies of all verifications and
> registrations, including IP address of those enterring info in the form. This
> way if/when someone complains you have the data there to present to them (and
> from the IP it should be fairly obvious if the complainer has a legitimate
> complaint or has just forgotten they did it).
> 
> T.
> 

  The current scheme works now. An account is created before sending 
email. Any registered user is presumed valid and it may not be an abuse. Providing
a verification link can also cause abuse too. Adding that is not difficult, but the
current one works fine now and http://cpan.org works in a similar way.

  Every user's registration and access log are saved for user's right.

  CAAN provides just an alternative way to publish ascii art, not an replacement
of other media. I trust ascii artists, and I hope CAAN is trusted too.

BoD wrote:
> Tom Bampton wrote:
> >
> > Please don't top post.
> 
> Why not ???

Found in a newsgroup:

    A. Because context is important.
    Q. Why is top-posting bad?


-- 
  #####       c    ^                       OO        /\\\\
#####  |     /|\    `^^^^^^^%--           '||`      |  \\\\
####-[.]\    / \      "   "  \ ha ha ha    dd      /[.]-\\\|
###   _|                                            |_   \\|
###  (_  http://www.ludd.luth.se/~vk/cgi/asciichat/  _)}  ==
 \    /        A S C I I  A R T  C H A T             #    ||\

Tom Bampton wrote:
> "BoD" <Bo...@JRAF.org> wrote in message
> news:3e0e4eaf$0$26166$626...@news.free.fr...
> > > Please don't top post.
> >
> > Why not ???
>
> Because it makes it harder to read the message. It reverses the
> natural flow of conversation, requiring you to read the end before
> the beginning.

You don't want to read the beginning (you already have read it in the
previous message in the thread).
But you want to include it because it may be of importance as reference
material. But less important than the new content, thus behind it.

> It also pisses off the majority of people reading
> Usenet.

Prove it :)


Anyway, I guess this conversation has already taken place many times, in
many other places. My point is: don't tell people how they should format
their text because this is really a question of taste, and subjective, and
there is no "best" way.

BoD

"BoD" <Bo...@JRAF.org> wrote in
news:3e0faac6$0$17186$626...@news.free.fr: 

> You don't want to read the beginning (you already have read it in the
> previous message in the thread).

That's not always true depending on what type of nr and when the reader 
has checked the ng and other factors. On regular occasions I don't have 
access to previous messages to a thread.

> But you want to include it because it may be of importance as
> reference material. But less important than the new content, thus
> behind it. 

When you consider that others might reply and quote from your post and 
also leave some of what you quoted then it does become messy because you 
top posted. If everything reads top to bottom (like this comment on a 
snipped bit of your post) then it makes more sense in later messages.

>> It also pisses off the majority of people reading
>> Usenet.
> 
> Prove it :)

Well I vote "please don't top post". That's 2 to 1 so far.

> Anyway, I guess this conversation has already taken place many times,
> in many other places. My point is: don't tell people how they should
> format their text because this is really a question of taste, and
> subjective, and there is no "best" way.

I find the general agreement is not to top post, I've never heard anyone 
say "please don't bottom post". But by all means exercise your freedom to 
do whatever the hell you like :)

PS You are telling people what to do by telling them not to tell you what 
to do!

-- 
"Loving kindness, warm hearts and a, "Life is mostly froth and bubble,
 Stretched out hand of tolerance,     Two things stand like stone,
 All the shining gifts,               Kindness in another's trouble,  
 That make peace on Earth." - tBW     And courage in your own." - ALG

[ABCGi]:
>
>   Well I vote "please don't top post". That's 2 to 1 so far.

3 to 1. :-)

>   I find the general agreement is not to top post, I've never heard
>   anyone say "please don't bottom post". But by all means exercise
>   your freedom to do whatever the hell you like :)

I heard it once, from a blind lady with shoddy software.  it was
awkward for her to scroll past old material on her screen reader, so
she preferred it to be at the bottom.  never mind that some news
clients, like Gnus, allow you to condense quotes into just the last
line.

-- 
Kjetil T.			|  read and make up your own mind
				|  http://www.cactus48.com/truth.html

BoD wrote:
> Tom Bampton wrote:
> > "BoD" wrote :
> > > Some unknown person whose name got snipped wrote:
> > > >
> > > > Please don't top post.
> > >
> > > Why not ???
> >
> > Because it makes it harder to read the message. It reverses the
> > natural flow of conversation, requiring you to read the end before
> > the beginning.
> 
> You don't want to read the beginning (you already have read it in the
> previous message in the thread).

How can you be so sure about that?

* There are different ways to sort messages.
* Some people prefer not to "thread" the messages (e.g.
  they read in chronological order, or favourite authors
  first, or ...)
* Sometimes a message doesn't reach your server (or is
  removed from the server, or they can be in response to
  somebody you killfiled, ...).
* Servers get full and dump old messages. Sometime I only
  have access to 2-3 days' worth of messages in some groups.
  If I go away for a week the beginning of a thread may
  not be available to me.
* etc etc etc

> But you want to include it because it may be of importance as reference
> material. But less important than the new content, thus behind it.

When you reply to bits of posts (like I do now) top posting can really
mess up the context. Replies in chronological order don't suffer from
that problem.

You can't know how people will reply to your message.

> Anyway, I guess this conversation has already taken place many times, in
> many other places. My point is: don't tell people how they should format
> their text because this is really a question of taste, and subjective, and
> there is no "best" way.

There is the traditional way (clue: classics become classics for a
reason).


-- 
  #####       c    ^                       OO        /\\\\
#####  |     /|\    `^^^^^^^%--           '||`      |  \\\\
####-[.]\    / \      "   "  \ ha ha ha    dd      /[.]-\\\|
###   _|                                            |_   \\|
###  (_  http://www.ludd.luth.se/~vk/cgi/asciichat/  _)}  ==
 \    /        A S C I I  A R T  C H A T             #    ||\

 _.--- BoD spoke in alt.ascii-art --------._ 
>> Please don't top post.
> 
> Why not ???

A: Because it upsets the natural flow of reading.
Q: Why is top posting so rude?
			  -- Springfield


'---...____ Faux_Pseudo ________________...---~~~

-- 
 .-'))  http://asciipr0n.com/fp   ('-.  | It's a damn poor mind that
' ..-  .:" )  New content  ( ":.  -.. ' | can only think of one way to
 ((,,_;'.;'     10 / 30     ';. ';_,,)) | spell a word.
       ((_.;'*Faux_Pseudo*':._))        | - Andrew Jackson

 _.--- Kjetil Torgrim Homme spoke in alt.ascii-art --------._ 
> [ABCGi]:
>>
>>   Well I vote "please don't top post". That's 2 to 1 so far.
> 
> 3 to 1. :-)

s/3/4

'---...____ Faux_Pseudo ________________...---~~~

-- 
   ICQ=66618055  :  (Now Playing)  http://asciipr0n.com/fp  updated=10/30
 YIM=faux_pseudo : Rev: /nin/purest_feeling_ii/12-Head.mp3
 A half truth is : Now: /nin/purest_feeling_ii_import/12_-_head.mp3
   a hole lie    : Fwd: )_-_03_-_Heresy_-_The_Electric_Hellfire_Club.mp3