Difference between revisions of "Linden Lab Official talk:Registration API"
Jump to navigation
Jump to search
(Three questions from Watty Berkson.) |
m (re-read, updated, and rephrased question about allowable API use) |
||
| Line 6: | Line 6: | ||
* Q: Implementing and providing a custom registration process comes with all sorts of legal implications as outlined by section 2.3.1 (Registration API Additional Terms) of the SL API Terms of Use posted on the Second Life website. However, the RegAPI does not provide a way to indicate "end user agreement to the ToS" to Linden Lab. So, are there any audit requirements that a 3rd party registration site must meet in order to prove ToS was acknowledged and agreed to by each end user at a specific date/time and IP address, etc.? | * Q: Implementing and providing a custom registration process comes with all sorts of legal implications as outlined by section 2.3.1 (Registration API Additional Terms) of the SL API Terms of Use posted on the Second Life website. However, the RegAPI does not provide a way to indicate "end user agreement to the ToS" to Linden Lab. So, are there any audit requirements that a 3rd party registration site must meet in order to prove ToS was acknowledged and agreed to by each end user at a specific date/time and IP address, etc.? | ||
* Q: Are 3rd party registration sites required to provide a security image code confirmation function to prevent automated account registration attempts via their sites? | * Q: Are 3rd party registration sites required to provide a security image code confirmation function to prevent automated account registration attempts via their sites? | ||
* Q: | * Q: For purposes of clarification, what is an example of usage that is NOT permitted by the following statement? | ||
** ''You may not use the Registration API other than as a means of collecting Account registration information from Your Website.'' (section 2.3.1 of API Terms of Use - http://secondlife.com/developers/api/tos.php) | ** ''You may not use the Registration API other than as a means of collecting Account registration information from Your Website.'' (section 2.3.1 of API Terms of Use - http://secondlife.com/developers/api/tos.php) | ||
Revision as of 10:11, 18 May 2007
Post questions about the Registration API here. If you can answer a question, please do. If not, Linden Lab will try to provide an answer.
- Q: Capabilities for the RegAPI expire - how do I know and what can I do about it?
- A: They expire every 30 days, unless you acquire the capabilities at the point when someone hits the reg page; then those capabilities won't expire. (Glenn Linden, 5/10/07)
- Q: When are we going to get the ability to: (a) Start users with inventory (b) Use the new default avatar choices (c) Provide additional avatar choices (d) Start a user wearing something (like a HUD) (e) Start users in a group (f) Flag users as only accessing a specific sim, estate, PG / M, or custom list of locations? (g) Get referral bonuses through Reg API for premium accounts?
- Q: Implementing and providing a custom registration process comes with all sorts of legal implications as outlined by section 2.3.1 (Registration API Additional Terms) of the SL API Terms of Use posted on the Second Life website. However, the RegAPI does not provide a way to indicate "end user agreement to the ToS" to Linden Lab. So, are there any audit requirements that a 3rd party registration site must meet in order to prove ToS was acknowledged and agreed to by each end user at a specific date/time and IP address, etc.?
- Q: Are 3rd party registration sites required to provide a security image code confirmation function to prevent automated account registration attempts via their sites?
- Q: For purposes of clarification, what is an example of usage that is NOT permitted by the following statement?
- You may not use the Registration API other than as a means of collecting Account registration information from Your Website. (section 2.3.1 of API Terms of Use - http://secondlife.com/developers/api/tos.php)