Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to avoid building a walled garden?

Tags:

interop

Some friends and I have had an idea for a website and have started working on it. It will rely on people contributing to a shared knowledgebase, and people will also be able to create personal profiles with reasonable amounts of data. We intend people should be able to leverage their content on other sites (e.g.: flickr, youtube) when building their profile on our site.

It occurred to us that we want to be good internet citizens, and make our website accessible and useful for people regardless of whether they have an account or not. We also want to make sure that any data people contribute to our site is not 'locked in' and is available to other sites appropriately.

Are there any specific practices we should follow, and similarly ones we should avoid?

Thanks!

like image 829
Stewart Johnson Avatar asked Dec 18 '22 08:12

Stewart Johnson


2 Answers

I would suggest that you follow the example of this very site.

Use OpenID for non-anonymous accounts/login, but allow anonymous posting.

like image 149
Randolpho Avatar answered Mar 11 '23 08:03

Randolpho


You should look into attaching a particular license to the content on your site. For example, StackOverflow uses a Creative Commons Attribution-Share-Alike license for all content provided. Depending on what restrictions you want placed on usage of your sites content, you should investigate something similar.

like image 45
Ryan Brunner Avatar answered Mar 11 '23 10:03

Ryan Brunner