Confirmed users
888
edits
Privacy/HowTo/WebReg: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 23: | Line 23: | ||
If you don't '''add an opt-in for communications''' (see above), you will not be able to send an email survey to your users in the future (ex: about how they use the site, what about it works (and doesn't work) for them, and how it could be made more useful, as well as what they'd like to get out of working with the community.) | If you don't '''add an opt-in for communications''' (see above), you will not be able to send an email survey to your users in the future (ex: about how they use the site, what about it works (and doesn't work) for them, and how it could be made more useful, as well as what they'd like to get out of working with the community.) | ||
== | =User Names= | ||
If the user name will be displayed publicly, make that clear with a notice. Here's an example from Firefox Flicks: | If the user name will be displayed publicly, make that clear with a notice. Here's an example from Firefox Flicks: | ||
| Line 31: | Line 30: | ||
"Your name will be displayed publicly with your video." | "Your name will be displayed publicly with your video." | ||
Other text ideas: | |||
"Your username will be permanent, choose wisely." | |||
==Page Text== | |||
Your page text should contribute to the principle of no surprises. It should be clear from the text what you are asking the user to do. | |||
If a user may wonder why you're asking something, answer their question next to the request. For example, a travel provider might ask for zipcode. They would add: | If a user may wonder why you're asking something, answer their question next to the request. For example, a travel provider might ask for zipcode. They would add: | ||