![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Apr. 7th, 2010 09:27 pmAs explained in this spec, the Named commenting level should allow users who do not have an account with Dreamwidth the ability to comment without being anonymous, but without registering.
Most modern blogging sites have some sort of Named Commenting form, usually asking for a Name and a URL to attach to the name.
Basics
The Named commenting level should ask for:
The Named commenting level could ask for:
Frontend
It would be most intuitive for users if the Anonymous commenting level and the Named commenting level were kept separate, to ensure no confusion over whether the user is posting with an entered Name and URL or if they are simply posting anonymously.
Journal Settings
The journal owner must be able to decide on a journal or per-entry basis if they want to force a commentor to provide a pseudonym or prevent pseudonyms from being used. If pseudonyms are prevented from being used, I assume anonymous commenting would also be disallowed on that entry/journal? I'm confused as to when pseudonyms would want to be disallowed but anonymous commenting allowed. Some clarification would be much appreciated.
E-mail System
If the e-mail system is created, it will be important to make sure that a commenter wants to receive e-mail about his/her comment. The e-mail should include a link to subscribe to further e-mails for that entry, and it should provide a link to unsubscribe from receiving e-mails about replies.
Should this unsubscribe them from all e-mails related to Named commenting from Dreamwidth or should it only unsubscribe them from that entry? The system could be abused (if the abuser knew a person's email) if the e-mails are only unsubscribed from that entry. It seems like unsubscribing them from all further e-mails about direct replies would make more sense, but what if they want to resubscribe at a later point?
Possibilities
Depending on how the project wants to advance, an automatically generated icon could be created for a Named commenter as described in the spec, but it would be most important to get everything else working first.
Most modern blogging sites have some sort of Named Commenting form, usually asking for a Name and a URL to attach to the name.
Basics
The Named commenting level should ask for:
- Name (Pseudonym)
- URL
The Named commenting level could ask for:
- E-mail (and send direct replies to the Named commenter's email)
Frontend
It would be most intuitive for users if the Anonymous commenting level and the Named commenting level were kept separate, to ensure no confusion over whether the user is posting with an entered Name and URL or if they are simply posting anonymously.
Journal Settings
The journal owner must be able to decide on a journal or per-entry basis if they want to force a commentor to provide a pseudonym or prevent pseudonyms from being used. If pseudonyms are prevented from being used, I assume anonymous commenting would also be disallowed on that entry/journal? I'm confused as to when pseudonyms would want to be disallowed but anonymous commenting allowed. Some clarification would be much appreciated.
E-mail System
If the e-mail system is created, it will be important to make sure that a commenter wants to receive e-mail about his/her comment. The e-mail should include a link to subscribe to further e-mails for that entry, and it should provide a link to unsubscribe from receiving e-mails about replies.
Should this unsubscribe them from all e-mails related to Named commenting from Dreamwidth or should it only unsubscribe them from that entry? The system could be abused (if the abuser knew a person's email) if the e-mails are only unsubscribed from that entry. It seems like unsubscribing them from all further e-mails about direct replies would make more sense, but what if they want to resubscribe at a later point?
Possibilities
Depending on how the project wants to advance, an automatically generated icon could be created for a Named commenter as described in the spec, but it would be most important to get everything else working first.
