Some document about the social gateway project.

diff --git a/doc/FORMATS b/doc/FORMATS
new file mode 100644 (file)
index 0000000..fee9840
--- /dev/null
+++ b/doc/FORMATS
@@ -0,0 +1,4 @@
+activitystreams
+atom
+json
+rfc822

diff --git a/doc/GATEWAYS b/doc/GATEWAYS
new file mode 100644 (file)
index 0000000..64e5a63
--- /dev/null
+++ b/doc/GATEWAYS
@@ -0,0 +1,7 @@
+atompub
+email
+pumpio
+rss
+statusnet
+tentio
+xmpp

diff --git a/doc/IDENTITY b/doc/IDENTITY
new file mode 100644 (file)
index 0000000..e6df87b
--- /dev/null
+++ b/doc/IDENTITY
@@ -0,0 +1,9 @@
+Is it possible to migrate? Change your address, but keep your contacts
+and subscriptions and others' subscriptions?
+
+Hard to do if there are multiple identities already, because of gateways.
+
+
+openid
+openpgp
+persona

diff --git a/doc/MIGRATION b/doc/MIGRATION
new file mode 100644 (file)
index 0000000..2382fae
--- /dev/null
+++ b/doc/MIGRATION
@@ -0,0 +1,12 @@
+How do I integrate with identi.ca/pump.io/tent.io with the possibility
+of migrating my data?
+
+1) Store most of the original data.
+2) Solve identification problem: in my case, use subdomains of
+cascardo.info for each service and keep those after I "migrate" working
+as gateways.
+
+3) How do I get out of identi.ca and keep my friends subscribed to me
+and my subscriptions? Do I link to my account in there and repost? Many
+people are getting out, so this may be a chance to get them to subscribe
+to my original accounts.

diff --git a/doc/PROTOCOLS b/doc/PROTOCOLS
new file mode 100644 (file)
index 0000000..c84ac16
--- /dev/null
+++ b/doc/PROTOCOLS
@@ -0,0 +1,4 @@
+HTTP
+XMPP
+SMTP
+IMAP

diff --git a/doc/README b/doc/README
new file mode 100644 (file)
index 0000000..06c1b47
--- /dev/null
+++ b/doc/README
@@ -0,0 +1,15 @@
+Conquer the world!
+
+Integrate multiple systems.
+
+Federated systems should work pretty much integrated.
+
+Legacy systems users may migrate off, and try to keep some access by
+using their passwords. The only purpose of supporting this is the
+network effect. This should be done by using plugins or gateways.
+
+Users that don't want to get out of legacy systems won't be able to
+subscribe to federated users. If the legacy system is a silo, it won't
+be possible to subscrite to its users without an account.
+
+Pick up a single native protocol and write gateways.

diff --git a/doc/USECASES b/doc/USECASES
new file mode 100644 (file)
index 0000000..d1ba8f8
--- /dev/null
+++ b/doc/USECASES
@@ -0,0 +1,17 @@
+Share picture.
+
+I take a picture in a family party and I want to share it with my
+family. I can simply send an e-mail to all my family contacts. Or I can
+share with them by using their prefered method, and make it easier to
+search the picture by submitter, tag, etc. And I want to allow them to
+comment, etc. Damn! E-mail allows all of that, and has allowed for many
+years.
+
+OK. Subscriptions and channels are good features (mailing lists solve
+that as well).
+
+Where is it stored? Locally, on every subscriptors computer? Do
+store-and-forward just like MTAs do? What does the network look like? Is
+anybody going to keep their computers on, and share the load? What are
+the guarantees? Use supernodes? Use tor or tor-like onion routing? Or
+simply end-to-end encryption?

diff --git a/doc/WORKING b/doc/WORKING
new file mode 100644 (file)
index 0000000..2b8f5f0
--- /dev/null
+++ b/doc/WORKING
@@ -0,0 +1 @@
+Agregate from the gateways. Post to all the gateways.