On Fri, 15 Mar 2002, Amir Abiri wrote: > That's the part i was thinking of. > The "Normalized" way to do it would be to make author a foriegn key for the > authors / users table. and then only users post. That doesn't mean only > admins and privileged users, but it means that you can't post if you haven't > registered yet, and that you have to login.
no, no... not at all. tihs is the way to kill any community - by forcing them to register. i know i stay away from most sites that require registration - and i certainly wouldn't write anything to a site if i had to register first - i'd just go away. > If we don't want to hold a users table other then for admins and not track > any passing user, we're not a giant corporation trying to make money, that wants to track down users. it simply does not make any sense, and is just an obstacle. if we'll need that in the future - we'll change things. >then this field will hold the user's name, and another > field will hold his email. Then every user that posts has to re-enter his > details, or they are cookied after the first post. the user's details aren't that many - a name, an optional email address and an optional 'dept'. we're not asking the user to fll up 10 fields just to post a little comment. just 1 mandatory field, and 2 optional fields. don't add on those. > I think the first approach is better. for a money-making-wanna-be commercial site, perhaps. not for a community site, with such a small community as iglu. 'featuritis' is a deadly desease for web sites usability. -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy ---------------------------------------------------------------------------- To unsubscribe, send a message to [EMAIL PROTECTED] Archives available at http://www.mail-archive.com/[email protected]/
