The Socknet

From The Socknet

(Redirected from ReadMe)
Jump to: navigation, search

Note: The spam got to be too much, so you now need a username if you want to edit this wiki.

The Socknet is a collection of separate websites that make up a single social network. This means that you can have an account on one website and make friends with people on any website. You can even host your own Socknet website.

But that's not all.

Ask questions in the FAQ or on the page you have questions about.


Contents

News

  • The code for foolishmortal.org is on the verge of going Beta. --Dan 16:48, 25 August 2010 (UTC)
  • We sent an open letter to the Diaspora team suggesting that they start their project with someone else's work (and implying that it should be the Socknet, of course). They never responded. -- Dan 26 May 2010

The First Socknet Provider

The first Socknet provider is now being developed at http://foolishmortal.org. It is currently in the alpha phase. Registration is open.

And its code is on SourceForge. You can use it to host your own Socknet provider, if that's your style.

How to Help

Here are some ways that you can quickly get helping.

If you've got questions or feedback on any article, please edit its discussion page. (You'll need to register first.) Don't worry if you don't know anything about wiki's, it's easy to edit and we can fix anything. Bad edits are a lot more valuable than no contributions at all. If you need help, contact User:Dan.

Anyone Can Help

  • Get an account on http://foolishmortal.org, the first Socknet provider.
  • Look at TODO: give your opinion.
  • The documentation contains some technical matters, but it is also a description of the objectives. You opinion counts there too.
  • If you're familiar with Wiki software, add links and See Also sections to articles.
  • Subscribe to the RSS feed, and/or follow @socknet on Twitter.
  • Tell your friends about the Socknet.

If You're a Programmer

How to

How to Launch a Socknet Provider

Currently there are two options:

  1. Use the software being developed for http://foolishmortal.org
  2. Develop your own. If you choose this option, use Functions on Providers as your main reference.

We'll try to flesh out this section once foolishmortal.org hits beta.

How to Access a Socknet Provider

If you want to send a user a message, get a list of his friends, or any of several other tools, you'll need to:

  1. Learn about Functions.
  2. Review the functions available on Providers.

To make it all easier, check out the Socknet Libraries.

How to Help Users Share Your Content

If you want to enable your website's content to be shared easily by users, there are a few things you can do, in order of complication:

  1. The easiest thing to do is provide Socknet GUID's on your webpages. Generally you'll want to point them at a URL that has a summary of the page's content in JSON format. This allows you to control how your pages look in the Socknet.
  2. The next thing you can do is provide a share button. This involves asking the user for their OpenID and using some simple server-side code to redirect them to a URL.
  3. Finally, if you want to receive comments from users about your content, you need to support the API.

The Specification

Core

  1. Glossary
  2. Central Concepts
    1. Functions
      1. Provider URL
      2. IP Verification
    2. Users
    3. Services
  3. Functions
    1. All Functions by Name
    2. Success and Failure
    3. Remote Function Calling
    4. Extending the Protocol

How To

  1. How To - Make Friends
  2. How To - Subscribe
  3. How To - Access a User's List of Friends
  4. How To - Exchange Messages
    1. How To - Collect Messages
    2. How To - Forward Messages
    3. How To - Direct Post
    4. How To - Reply
    5. How To - Find Messages
    6. How To - Format Messages
    7. How To - Share Internet Content
  5. Services
    1. How To - Register a Service
    2. How To - Use Tokens to Enhance Security
    3. How To - Discover Registered Services
  6. How To - Change an ID
  7. How To - Convert an App to Work With Socknet Profiles
  8. How To - Create "Groups"

Best Practices

  1. Best Practices - Caching
  2. Best Practices - Profile
  3. Best Practices - URL Processing
  4. Best Practices - Identifying Spam
  5. Best Practices - Providers vs Services
  6. Best Practices - Gagging
  7. Best Practices - OpenSocial

Unenforcable Requirements

Things that Providers should always do to stay on the good side of users.

  1. Data Mobility
  2. Socknet Providers as OpenID Providers
  3. Rogues
  4. Boycotts

Concepts

These further concepts apply to the Socknet. They are not required for it to operate, but they are helpful.

  1. Trust
  2. Trust Assignment
  3. Socknet Client Protocol
  4. foaf
  5. onion Domain
  6. Protocols
    1. RSS2
    2. Calendar

Commentary

Some of these items are things that providers and service creators should consider. Others are rants.

  1. Why JSON is Awesome
  2. Why OAuth is Not Used
  3. Why We Don't Do Prelogin
  4. You Can't Tell Lies on the Socknet
  5. The Protocol is Secure Against CSRF, But You Need to Consider It
  6. Application Platforms Are Unnecessary
  7. Herds Are No Longer Safe
  8. Always Protect Against XSS Attacks

Community

  1. Logo

Credits

My name shows up a lot in the histories, but in fact I got a lot of help from User:Clint and User:Chris in meetings outside the wiki. I also got concept help from User:Sam, and design related advice from everyone in Special:ListUsers. So here's a section mentioning them. --Dan 22:04, 11 November 2009 (UTC)

Retrieved from "http://socknet.net/w/The_Socknet"
Personal tools