me trying to somersault around convincing folks to start a new account and create a space and try it out.

I just want to throw them into the pool and let them learn how to swim that way.

"Niggaz wanna rap and rap and rap... maan, FUCK all that"

in other words, talking about metanotes doesn't do it justice, they should just be prompted to jump in or leave...

howdy!

It needs to flow better.

I sometimes toy with the idea of having an out of band chat in a panel.

You could have:

• space specific chats
• site-wide chats
• team chats.

...as a supplement to spaces.

Trying to note chat.

/spex/chat

Boot up Adobe Illustrator and you're asked soon - "create a new document"

if we made chatting work intuitively then you get folks asking questions of each other faster... also the walls we create together are totally unique to the walls we create for ourselves, right?

/persistence

http://metanotes.com/user/sri/launch/homepage/persistence

A strength has been the #persistence of login session. I love never being logged out!

If a new visitor to METANOTES comes to the home page and we present a Create Space dialog box that gets them right in there.

If you just create-a-new-space the second you enter metanotes.com then you are immediately immersed in it.

Walls built together have a very different feel. I have a few days away from work, so I'll put in some time toward MetaNotes while I'm in Portland.

When someone first stumbles on metanotes, what if we pop a Create Space dialog box right in their face? Like, create a space or move on dude...

If they aren't logged in, we give them the Log In box, and if they don't have an account, they can Create an Account. Then they are placed into the Space they created in step one.

The above could be streamlined later, like by improving the Create Space dialog box and integrating the Log In and Create an Account into one dialog box etc...

THE BIG UNDERSTANDING OF UNAMERICAN.COM IS THAT YOUR HOME PAGE IS A DRUG OF SORTS AND MUST BE ADDICTIVE IN SOME WAY.

It was never just about stickers, really, it was about a web page that dared to reach out into the actual world through stickers. That has not yet been topped, really, i think?

Get them excited to see the space, but then be like... whoops you gotta register first.

If you visit metanotes.com shouldn't you immediately create a new space there?

• They fill out a Create Space dialog box.
• If they're logged in, the space is created inside their /user directory and they're just sent there.
• If they aren't logged in, they get the login/createnewaccount dialog box right away. After that, the space is created and they're entered into it.

I wish I could just go to metanotes.com when I wanted to create a new space.

Just one URL to remember to type in to create a new space, rather than thinking "where should I start this space?" and having to navigate there etc....

Just keep coming to METANOTES.COM and creating spaces. Each time. Just go to one URL and do one thing over and over again.

http://metanotes.com/user/sri/launch

<--- how cool... how did that happen I wonder?

• Title
• Type - dropdown box QUESTION WISH GOAL ACTION ** TRUTH
• Private Space?
• Invite ** separate other usernames with commas

Both get you the user to go to the same URL over and over and over again: their home page. Get folks to use your homepage daily is the big game, maybe?

You open software not to learn about it but to USE it.

You just surf to metanotes.com anytime you want to create a space, and then you can sort out the spaces from the METASPACE.

<-- I know that could use some work.

I'm currently at Clojure/West.

The path is always fixed from the title and the height and width can be set to "massive", right?

if that is true then we could save a lot of space in this dialog box for type and invite.

I truly miss Portland.

If they are not logged in now then shouldn't we present them with the new account creation slash login dialog box after they hit Save in the Create Space dialog box?

You'd want to be able to move a space around in your ontology after you create it, probably, and that'd be done in the METASPACE, right?

...and we were blessed with great weather. It's nice and sunny out today.

Using Facebook Login with Existing Login Systems

Some developers may prefer to build their apps with both a custom login mechanism and Facebook Login. This guide will cover some of these scenarios and give you tips for handling a person's experience using these apps.

Overview Adding Facebook Login info to an existing login account Merging Facebook Login accounts and separately created accounts Adding manual login info to a Facebook Login created account Overview

Developers can choose to implement their own login system where a person signs up for the app using their email and password and an account is created for them. Typically, apps will use an email verification step in this case to authenticate identity.

Alternatively they may choose to use Facebook Login completely for their login system. In this case a person signs up for the app using Facebook Login, an account is created for them, and the authentication step is taken care of by Facebook.

In addition to these simpler scenarios, apps will need to handle more complex situations:

A person signs up for the app using their email and password, but later they want to use Facebook Login to obtain data from their Facebook account, to post to their timeline, or just to use to log in with in future. A person signs up for the app using their email and password, but later chooses to log in with Facebook separately. (Note: this guide makes the assumption that the email they supplied first and the primary email that is associated with their Facebook account are the same) A person signs up for the app using Facebook Login and later wants to also be able to log in to this account using an email address and password. The guides below will outline what we think are the best ways to handle these situations.

Associating Facebook Login with an already logged-in account

This section covers the situation where someone uses an app's custom login system to create an account, and later, while they are still logged in, wants to associate their Facebook account with it. For example, people can sign up to Spotify with an email address and a password, but they can later choose to associate that account with their Facebook account using Facebook Login, such as when they want to publish their listening activity to their timeline.

1. Add a Facebook Login flow to your app

You can read our guides to using a Facebook Login flow in your app to complete this step. In the Spotify example, you would begin Facebook Login flow to the point in the app where the person indicates that they'd like to publish their listening activity, or you might offer an explicit option to link their account with their Facebook account.

1. Handle merging of account information

Once a person has logged in to your app using your own login system, and then completes the Facebook Login flow, your app will have two very important things that must now be merged:

The account created by the app Information from Facebook identifying that person's Facebook account In the majority of apps, the original account will have been stored in a database table, so the simplest approach is to associate the Facebook account information with that account in the database.

It is generally better to create a new table in which you store the person's Facebook account information. The advantage to keeping a separate table in lieu of adding more columns to your existing account table is that it enables you to quickly support other OAuth account logins over time. In the future, if the same person chooses to log in to your app, you can match the information stored in the database to log them in using either method seamlessly.

Merging separately created accounts with Facebook Login

In this situation, a person has logged in to your app with their own credentials (an email and password for example) and later, when logged out, chooses to sign in to your app using Facebook Login. Your app will now have two accounts for the same person, one created via the app login system, the other created via the Facebook Login flow. In order to provide the best experience for that person, your app should attempt to merge these accounts into one.

This guide assumes that each account created by your app has an email address associated with it. However, it is possible that the person has used a different email to create their existing account than the one they have associated with their Facebook account. In this case, you should offer people an explicit 'Account Merging' option somewhere in your app and then allow the person to manually specify the two separate accounts that they wish to merge. Additionally, if your own custom accounts do not store an email address, then again, you will need to allow the person to manually specify the accounts that they wish to merge.

1. Modify your Facebook Login flow to request permissions for email

If your app's own custom login system uses an email address to uniquely identify each account, you should also ask for the person's email address (using the email permission) during the Facebook Login flow. Read our guide to requesting permissions to find out how to do this.

1. Merge the Facebook Login account and the app account

After a successful login using Facebook, you will have the person's email address, Facebook ID, and access token. Your app should search for an existing account that has been created with that same email address. If one exists, you should merge the two accounts and add the Facebook info to the existing account - as recommended above.

At this point, you should log in the person as you normally would.

If there is not an existing entry in your database with that email address, then you should consider them to be a new user.

Adding manual login info to a Facebook Login created account

This situation occurs when someone creates their account in your app using Facebook Login, but later wants to also log in to the account using a unique credential and a password. For example, Netflix has a web app that uses Facebook Login alongside a regular login system, and also an Xbox 360 app where people can only use the regular login system.

1. Ensure the Facebook Login email address is verified

If you use an email address as the unique credential which identifies each account, your app should verify that the email address associated with the person's Facebook account (and obtained during Facebook Login) is valid. You can do this by creating code in your app to send a verification email to the address obtained after Facebook Login (you will probably need to have this step as part of your regular login system anyway).

1. Ask the person to supply a new password (and other credentials)

Once the email address is verified, you can now request that the person supplies a password, indicating to them that they can use this to log in to your app in future in conjunction with their email address. Once supplied, you can add this to the same part of your database where you are currently storing account information.

If your app's login system doesn't use an email address as the identification and uses something user-generated like a username instead, then you should also request that the person supplies this at the same time as a password.

People might also expect that your app offer the ability to remove Facebook account association from their login account - this should simply involved stripping your account database table of the Facebook info for that particular person.