Open social

to iron out order, etc.

See also Comms#RSS_and_Atom, Chat#Jabber.2FXMPP, Data#Semantic_Web

Movements and initatives

and communities

• https://en.wikipedia.org/wiki/Distributed_social_network
• https://en.wikipedia.org/wiki/Comparison_of_software_and_protocols_for_distributed_social_networking

• http://tantek.com/2010/281/b1/what-is-the-open-web

• https://en.wikipedia.org/wiki/OASIS_(organization)

• http://www.w3.org/wiki/Open_Web_Platform

OpenSocial

2007

• OpenSocial is the industry's leading and most mature standards-based component model for cloud based social apps.
  • Wikipedia:OpenSocial is a public specification that defines a component hosting environment (container) and a set of common application programming interfaces (APIs) for web-based applications. Initially it was designed for social network applications and was developed by Google along with MySpace and a number of other social networks. In more recent times it has become adopted as a general use runtime environment for allowing untrusted and partially trusted components from third parties to run in an existing web application. The OpenSocial Foundation has also moved to integrate or support numerous other open web technologies. This includes Oauth and OAuth 2.0, Activity Streams, and portable contacts, among others.

• http://www.youtube.com/watch?v=M2x_AugZwqs

DataPortability

November 2007

• Data portability is the ability for people to reuse their data across interoperable applications. The DataPortability Project works to advance this vision by identifying, contextualizing and promoting efforts in the space.
  • http://en.wikipedia.org/wiki/DataPortability

There are numerous open standards that are considered to advance the vision, such as RDF, RDFa, microformats, APML, FOAF, OAuth, OpenID, OPML, RSS, SIOC, the XHTML Friends Network (XFN), XRI, and XDI.

• http://hueniverse.com/2007/12/reflections-on-the-open-web-community/
• http://techcrunch.com/2008/05/05/twitter-can-be-liberated-heres-how/
  • http://chrissaad.wordpress.com/2008/05/05/decentralized-microblogging-twitter-20/
• http://www.niallkennedy.com/blog/2008/01/data-portability-authentication-authorization.html
• http://web.archive.org/web/20100706024305/http://2008.xtech.org/public/schedule/detail/565 - Data Portability with SIOC and FOAF. May 2008.
• http://web.archive.org/web/20110516032810/http://www.semanticscripting.org/SFSW2008/papers/11.pdf
• http://web.archive.org/web/20090414050007/http://faradaymedia.com/syncstream
• http://www.johnbreslin.com/blog/2008/05/09/prototype-for-distributed-decentralised-microblogging-using-semantics/
• http://forrester.typepad.com/groundswell/2008/01/the-open-social.html
• http://mrtopf.de/blog/plone/what-is-the-future-of-content-management-systems-related-to-social-networks/
• http://www.mediamatic.net/26386/en/federating-social-networks-the-technology
• http://www.mediamatic.net/26605/en/federating-social-networks
• http://ralphm.net/publications/berlin_2007/

DiSo

December 2007

• DiSo Project (dee • soh) is an initiative to facilitate the creation of open, non-proprietary and interoperable building blocks for the decentralized social web. Silo free living. Social networks are becoming more open, more interconnected, and more distributed. Many of us in the web creation world are embracing and promoting web standards — both client-side and server-side. Microformats, standard APIs, and open-source software are key building blocks of these technologies. This model can be described as having three sides: Information, Identity, and Interaction. Our first target is WordPress, bootstrapping on existing work and building out from there.

• http://wiki.factoryjoe.com/w/page/12283844/DistributedSocialNetwork
• http://factoryjoe.com/blog/2007/12/06/oauth-10-openid-20-and-up-next-diso/

• https://singpolyma.net/plugins/actionstream/

OStatus / StatusNet

via Identi.ca, 2008

• http://en.wikipedia.org/wiki/OpenMicroBlogging - prior system

• OStatus is an open standard for distributed status updates that references a suite of open protocols including Atom, Activity Streams, PubSubHubbub, Salmon, Webfinger, that allows different messaging hubs to route status updates between users in near real-time. - 2010
  • http://en.wikipedia.org/wiki/OStatus
  • http://www.w3.org/community/ostatus/

• Status.net - formerly Laconica, powered Identica
  • http://en.wikipedia.org/wiki/StatusNet

• http://chrismdp.com/2012/09/ostatus-like-twitter-but-open/ [1]

• https://rstat.us/

• http://p2pfoundation.net/Social_Publishing_with_Drupal
• http://www.istos.it/blog/social-network/supporting-activity-streams-drupal
• http://status.net/2010/07/21/federated-social-web-summit-wrapup
• http://evan.prodromou.name/files/fedsocweb/fedsocweb.html
• http://www.devcomments.com/OpenSocial-and-OStatus-at246411.htm

• http://wordpress.org/plugins/ostatus-for-wordpress/

august 2010

• http://groups.google.com/group/ostatus-discuss/browse_thread/thread/329e440ed44131f9
• http://www.istos.it/blog/federated-social-web/federated-social-web-and-drupal-notes-drupalcon-bof-meeting

• https://groups.google.com/forum/#!topic/ostatus-discuss/fxXfMW1sFNM

aug 2013; @tantek | previous efforts at directly designing decentralized protocols (without selfdogfood) always result in overly complex protocols that not enough people can implement. e.g. Salmon

now part of GNU Social

rssCloud

2009

• http://web.archive.org/web/20120111041741/http://rsscloud.org/ - Dave Winer
• http://web.archive.org/web/20100825193645/http://blog.rsscloud.org/
• http://www.rsscloud.org/

• http://scripting.com/stories/2012/07/25/anOpenTwitterlikeEcosystem.html

Federated Social Web

2010, 2012

• http://www.w3.org/community/fedsocweb/ - Federated Social Web Community Group
• http://www.w3.org/2005/Incubator/socialweb/ - Federated Social Web Incubator Group, prior

• http://planet.federatedsocialweb.org/

• http://www.w3.org/2005/Incubator/federatedsocialweb/wiki/Protocols

• http://www.w3.org/2005/Incubator/federatedsocialweb/wiki/SWAT0
• http://www.w3.org/2005/Incubator/federatedsocialweb/wiki/SWAT1_use_cases

• http://78.47.176.118/wiki/index.php?title=Main_Page

• http://www.w3.org/community/rww/

Drupal related

old

• http://web.archive.org/web/20090502082311/http://www.shareduniverse.net/

• http://groups.google.com/group/openid
• http://groups.google.com/group/dataportability-public
• http://groups.google.com/group/diso-project
• http://groups.google.com/group/oauth
• http://groups.google.com/group/activity-streams/
• http://groups.google.com/group/ostatus-discuss
• http://groups.google.com/group/federated-social-web
• http://groups.google.com/group/open-web-discuss
• http://groups.drupal.org/microformats-in-drupal
• http://groups.drupal.org/activity
• http://groups.drupal.org/semantic-web

onesocialweb

2011?

• http://onesocialweb.org - XMPP based
  • http://onesocialweb.org/developers-protocol.html

• https://github.com/onesocialweb

pump.io

2012, succeeds OStatus / StatusNet

• http://pump.io/ - successor to StatusNet
  • https://github.com/e14n/pump.io/blob/master/API.md

• http://www.skilledtests.com/wiki/Pump.io
• http://www.h-online.com/open/news/item/StatusNet-transforms-into-Node-js-driven-pump-io-1771646.html
• http://opensource.com/life/13/7/pump-io

• http://lwn.net/Articles/544347/

a general-purpose Activity Streams engine. It diverges from OStatus in a few other respects, of course, such as sending activity messages as JSON rather than as Atom, and by defining a simple REST inbox API instead of using PubSubHubbub and Salmon to push messages to other servers. Pump.io also uses a new database abstraction layer called Databank, which has drivers for a variety of NoSQL databases, but supports real relational databases, too. StatusNet, in contrast, was bound closely to MySQL. But, in the end, the important thing is the feature set; a pump.io instance can generate a microblogging feed, an image stream, or essentially any other type of feed. Activity Streams defines actions (which are called "verbs") that handle common social networking interaction; pump.io merely sends and receives them.

• https://urmf.net/

App.net

2012

• http://app.net - $ ecosystem
  • https://en.wikipedia.org/wiki/App.net

Tent

2012

• Tent is the protocol for decentralized communication. Tent uses HTTPS and JSON to transport posts between servers and apps.
  • Tent - use data and posts across your apps and send and receive posts from friends. Right now, most people use Tent to share short 256 character long status posts with friends. Many independent developers are building other apps that use the Tent protocol.

• https://cupcake.io/ - service

#indieweb

• http://indiewebcamp.com/Main_Page
  • http://indiewebcamp.com/Projects

• http://www.wired.com/wiredenterprise/2013/08/indie-web/

• http://tantek.com/2013/113/b1/first-federated-indieweb-comment-thread
• http://bret.io/2013/06/28/indiewebcamp-2013-roundup/

activitystrea.ms, rel-me/indieauth, webmention, etc.

• http://indiewebcamp.com/plaintext

• http://indiewebcamp.com/2012/Open_Checkins

• http://indiewebcamp.com/webactions
• http://indiewebcamp.com/POSSE#CRUD

• http://sandeep.shetty.in/2013/06/really-simple-social-blogging.html

• http://benwerd.com/2013/04/02/the-progressive-profitable-web/

• http://idno.co/
• https://github.com/converspace/converspace

• http://aralbalkan.com/notes/indie-data/

• http://news.indiewebcamp.com/

• http://activitypush.org/

• http://nomoresharecropping.org/

Semantic

See also Comms#RSS and Atom and Data#Semantic Web

• http://stackoverflow.com/questions/14307792/what-is-the-relationship-between-rdf-rdfa-microformats-and-microdata
• http://manu.sporny.org/2011/uber-comparison-rdfa-md-uf/

• http://tantek.com/presentations/2004etech/realworldsemanticspres.html

Microformats

2003

• microformats are extensions to HTML for marking up people, organizations, events, locations, blog posts, products, reviews, resumes, recipes etc. Sites use microformats to publish a standard API that is consumed and used by search engines, browsers, and other tools.
  • http://microformats.org/wiki/history-of-microformats
  • http://microformats.org/wiki/microformats-2
  • http://microformats.org/wiki/exploratory-discussions
  • http://microformats.org/wiki/identity-consolidation

• http://microblog.reallysimple.org/

RDFa

2004. RDFa 1.1 reached recommendation status in June 2012.

• RDFa is an extension to HTML5 that helps you markup things like People, Places, Events, Recipes and Reviews. Search Engines and Web Services use this markup to generate better search listings and give you better visibility on the Web, so that people can find your website more easily.
  • https://en.wikipedia.org/wiki/RDFa

• http://www.w3.org/TR/rdfa-core/
• http://www.w3.org/TR/rdfa-primer/
• http://www.w3.org/TR/rdfa-lite/

• HTML+RDFa 1.1 - Support for RDFa in HTML4 and HTML5 [2]

Sitemaps

2005

• Sitemaps are an easy way for webmasters to inform search engines about pages on their sites that are available for crawling. In its simplest form, a Sitemap is an XML file that lists URLs for a site along with additional metadata about each URL (when it was last updated, how often it usually changes, and how important it is, relative to other URLs in the site) so that search engines can more intelligently crawl the site.
  • https://en.wikipedia.org/wiki/Sitemaps

Microdata

2009

• http://www.w3.org/TR/microdata/
• http://www.w3.org/TR/html5/microdata.html

• https://en.wikipedia.org/wiki/Microdata_(HTML)

• http://manu.sporny.org/2013/microdata-downward-spiral/

Open Graph Protocol

2010

• http://ogp.me/ - facebook
  • https://en.wikipedia.org/wiki/Open_Graph_protocol

• http://factoryjoe.com/blog/2010/04/22/understanding-the-open-graph-protocol/

Schema.org

2011

• Schema.org provides a collection of schemas, i.e., html tags, that webmasters can use to markup their pages in ways recognized by major search providers. Search engines including Bing, Google, Yahoo! and Yandex rely on this markup to improve the display of search results, making it easier for people to find the right web pages.

Twitter Cards

2012

• Twitter Cards make it possible for you to attach media experiences to Tweets that link to your content. Simply add a few lines of HTML to your webpages, and users who Tweet links to your content will have a "card" added to the Tweet that’s visible to all of their followers.

• http://semanticweb.com/twitter-the-new-kid-on-the-semantic-web-block_b29982

Authentication

See also Communication#Identity

OpenID

2005

• http://openid.net/
  • https://en.wikipedia.org/wiki/OpenID

• http://wiki.openid.net/w/page/12995226/Run-your-own-identity-server

• http://norman.rasmussen.co.za/107/xmpp-auth-for-openid/ [3]

• http://www.cse.wustl.edu/~jain/cse571-07/ftp/websso/

OAuth

OAuth - 2006-2010, OAuth 2 - 2012

• http://oauth.net/
  • https://en.wikipedia.org/wiki/OAuth
  • http://www.ietf.org/mail-archive/web/oauth/current/maillist.html

OAuth began in November 2006 when Blaine Cook was developing the Twitter OpenID implementation. Meanwhile, Ma.gnolia needed a solution to allow its members with OpenIDs to authorize Dashboard Widgets to access their service. Cook, Chris Messina and Larry Halff from Ma.gnolia met with David Recordon to discuss using OpenID with the Twitter and Ma.gnolia APIs to delegate authentication. They concluded that there were no open standards for API access delegation.[citation needed]

The OAuth discussion group was created in April 2007, for the small group of implementers to write the draft proposal for an open protocol. DeWitt Clinton from Google learned of the OAuth project, and expressed his interest in supporting the effort. In July 2007 the team drafted an initial specification. Eran Hammer joined and coordinated the many OAuth contributions, creating a more formal specification. On October 3, 2007, the OAuth Core 1.0 final draft was released.

Because OAuth 2.0 is more like a framework rather than a defined protocol, any OAuth 2.0 implementation is unlikely to naturally be interoperable with any other OAuth 2.0 implementation. Further deployment profiling and specification is required for any interoperability.

• http://web.archive.org/web/20110305071413/http://blog.behindlogic.com/2007/12/oauth-is-key-to-future-longings-of.html
• http://homakov.blogspot.co.uk/2013/03/oauth1-oauth2-oauth.html
• http://hueniverse.com/2012/07/oauth-2-0-and-the-road-to-hell/

• https://github.com/Mashape/mashape-oauth/blob/master/FLOWS.md

• https://oauth.io
  • https://github.com/oauth-io/oauthd
  • https://github.com/oauth-io/oauth-js

OpenID Connect

2010

• http://openid.net/connect/
• http://openid.net/wg/connect/

• http://factoryjoe.com/blog/2010/01/04/openid-connect/
• http://factoryjoe.com/blog/2010/05/16/combing-openid-and-oauth-with-openid-connect

• https://npmjs.org/package/openid-connect

WebID

2011

• http://webid.info/

• http://www.w3.org/wiki/WebID - FOAF+SSL
  • https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/index.html
  • http://lists.w3.org/Archives/Public/public-webid

• http://buddypress.org/support/topic/webid-versus-openid-connect/
• http://semanticweb.com/time-for-another-look-at-webid_b21579
• http://bblfish.net/tmp/2010/08/05/webid-related.respec.html
• http://news.softpedia.com/news/W3C-Launches-WebID-Development-Group-for-Browser-Authentication-178496.shtml

• http://trueg.wordpress.com/tag/foaf/

• http://clerezza.apache.org/
  • https://github.com/apache/clerezza

• https://drupal.org/project/webid

BrowserID / Persona

• https://login.persona.org
  • https://developer.mozilla.org/en/docs/Mozilla/Persona
  • https://developer.mozilla.org/en/BrowserID/Quick_Setup
  • https://developer.mozilla.org/en/docs/Persona/Identity_Provider_Overview

• https://en.wikipedia.org/wiki/Mozilla_Persona

• https://github.com/mozilla/id-specs/blob/prod/browserid/index.md
• https://github.com/mozilla/browserid

• http://tools.ietf.org/html/draft-jones-json-web-key-01 - A JSON Web Key (JWK) is a JSON data structure that represents a set

  of public keys.

• http://datatracker.ietf.org/wg/jose/charter/

• https://github.com/mozilla/eyedee.me

• https://checkmyidp.org/
• http://123done.org/

• https://github.com/mozilla/tincan

IndieAuth

• http://microformats.org/wiki/web_sign-in
• http://microformats.org/wiki/RelMeAuth

• IndieAuth is a way to use your own domain name to sign in to websites. It's like OpenID, but simpler! It works by linking your website to one or more authentication providers such as Twitter or Google, then entering your domain name in the login form on websites that support IndieAuth.
  • http://indiewebcamp.com/IndieAuth

• http://spec.indieauth.com/

• http://aaronparecki.com/articles/2013/07/15/1/password-less-logins-from-your-own-domain-with-a-pebble-watch

Discovery

XRD

• https://en.wikipedia.org/wiki/XRDS

• http://docs.oasis-open.org/xri/xrd/v1.0/os/xrd-1.0-os.html
• https://wiki.oasis-open.org/xri/XrdOne/SpecHome

• http://hueniverse.com/2009/03/xrd-vs-xrds-side-by-side-comparison/
• http://hueniverse.com/2009/03/xrd-document-structure/
• http://hueniverse.com/2009/11/xrd-alignment-with-link-syntax/

WebFinger

• WebFinger is a protocol on the Internet that aims to provide information about people by their E-mail addresses.[1] It moves the old UNIX Finger protocol to the web by relying on HTTP only. It provides meta data about the user behind the E-mail address, for example public encryption keys and OpenIDs. The WebFinger protocol is used by the federated social networks StatusNet and Diaspora to discover users on federated nodes and pods as well as the remotestorage protocol used by e.g. ownCloud.
  • http://code.google.com/p/webfinger/wiki/WebFingerProtocol
  • https://en.wikipedia.org/wiki/Webfinger
  • http://webfinger.org/

• http://webfist.org/

.well-known

• https://tools.ietf.org/html/rfc5785
• http://tools.ietf.org/html/draft-jones-simple-web-discovery-02

JSON Resource Descriptor

openid connect

• JSON Resource Descriptor (JRD) is a simple JSON object that describes a "resource" on the Internet, where a "resource" is any entity on the Internet that is identified via a URI or IRI. For example, a person's account URI (e.g., acct:bob@example.com) is a resource. So are all web URIs
• http://hueniverse.com/2010/05/jrd-the-other-resource-descriptor/

Web Intents

• Web Intents is a framework for client-side service discovery and inter-application communication. Services register their intention to be able to handle an action on the user's behalf. Applications request to start an Action of a certain verb (share, edit, view, pick etc.) and the system will find the appropriate Services for the user to use based on the user's preference. Web Intents puts the user in control of service integrations and makes the developer's life simple.

Profile

• http://microformats.org/wiki/rel-me

hcard

• http://microformats.org/wiki/h-card

avatar

• http://pavatar.com/
• https://www.libravatar.org/

attention

• http://www.apml.areyoupayingattention.com/
  • https://en.wikipedia.org/wiki/Attention_Profiling_Mark-up_Language
• http://www.bbc.co.uk/blogs/radiolabs/2008/05/were_playing_your_song_persona.shtml

Feeds / Activity

RSS

• https://en.wikipedia.org/wiki/RSS

• http://en.wikipedia.org/wiki/News_aggregator

• http://blog.superfeedr.com/state-of-readers/
• http://www.marco.org/2013/03/26/power-of-rss

• https://github.com/samuelclay/NewsBlur

• http://battellemedia.com/archives/2013/02/an-apology-to-my-rss-readers-but-i-had-to-do-it.php

• https://news.ycombinator.com/item?id=5750057

Atom / APP

• http://atompub.org/
• https://tools.ietf.org/html/rfc4287 - The Atom Syndication Format
• https://en.wikipedia.org/wiki/Atom_(standard)

• http://web.archive.org/web/20130402064019/http://atomenabled.org/

• http://bitworking.org/projects/atom/rfc5023.html - The Atom Publishing Protocol
• http://datatracker.ietf.org/wg/atompub/charter/
• http://www.youtube.com/watch?v=T04fKsD56LU

• http://xmpp.org/internet-drafts/draft-saintandre-atompub-notify-07.html

• http://tools.ietf.org/html/rfc4685#page-1 - Atom Threading Extensions
• http://bblfish.net/work/atom-owl/2006-06-06/AtomOwl.html

Clients

• http://brassreader.com/

• http://www.rssowl.org/

Web aggregation

• http://en.wikipedia.org/wiki/Planet_(software) - old skool

• http://rsslounge.aditu.de/

• http://selfoss.aditu.de/

• http://tt-rss.org/redmine/projects/tt-rss/wiki

• https://github.com/swanson/stringer

• http://www.commafeed.com/
  • https://github.com/Athou/commafeed

• http://www.sismics.com/reader/#!/home

• https://feedbin.me/
  • https://github.com/feedbin/feedbin

Services

• http://readable.cc/ - nicely minimal
• https://yoleoreader.com/

Library

• https://github.com/simplepie/simplepie

Activity Streams

2009

• http://ui-patterns.com/patterns/ActivityStream

• http://activitystrea.ms/
  • https://github.com/activitystreams/json-activity

• http://microformats.org/wiki/activity-streams
• http://indiewebcamp.com/ActivityStreams

• pump.io - Social server with an ActivityStreams API

Linkbacks

• https://en.wikipedia.org/wiki/Linkback

• https://en.wikipedia.org/wiki/Trackback

• https://en.wikipedia.org/wiki/Pingback

• http://webmention.org/ - A modern alternative to Pingback.
  • http://indiewebcamp.com/webmention
  • https://en.wikipedia.org/wiki/WebMention

• http://webmention.io/

Comments

• http://web.archive.org/web/20120504100446/http://wellformedweb.org/story/9
  • http://intertwingly.net/blog/2006/04/15/commentRss

• http://indiewebcamp.com/comment

Salmon

• Salmon Protocol is a message exchange protocol running over HTTP designed to decentralize commentary and annotations made against newsfeed articles such as blog posts. It allows a single discussion thread to be established between the article's origin and any feed reader or "aggregator" which is subscribing to the content. Put simply, that if an article appeared on 3 sites A (the source), B and C (the aggregates), that members of all 3 sites could see and contribute to a single thread of conversation regardless of site they were viewing from.
  • https://en.wikipedia.org/wiki/Salmon_(protocol)

Interaction

• http://webintents.org/
  • http://www.w3.org/TR/web-intents/
  • https://en.wikipedia.org/wiki/Web_Intents

• http://www.oexchange.org/
  • http://hueniverse.com/2010/06/an-introduction-to-oexchange/

Graph

FOAF

2000

FOAF (from "friend of a friend") is an RDF based schema to describe persons and their social network in a semantic way. FOAF could get used within many wikis for annotating user pages, or describing articles about people.

• http://www.foaf-project.org/
  • http://en.wikipedia.org/wiki/FOAF_(software)

• http://www.foaf-o-matic.org/

• http://semanticweb.org/wiki/FOAF
• http://www.w3.org/wiki/FoafSites

• http://rdfweb.org/foaf/

See Open web#WebID

XFN

2006

• https://en.wikipedia.org/wiki/XHTML_Friends_Network

• http://gmpg.org/xfn/

• http://gmpg.org/xfn/and/foaf

Portable Contacts

2008

• http://portablecontacts.net/
  • http://wiki.portablecontacts.net/w/page/17776140/FrontPage
  • https://en.wikipedia.org/wiki/Portable_Contacts

The protocol is a combination of OAuth, XRDS-Simple and a wire-format based on vCard harmonized with schema from OpenSocial.

Networks

See also Comms, Network#Projects

• https://docs.google.com/spreadsheet/ccc?key=0AtXMsLaocacrdDAwTzdPeGdPNlhZSHFMelg0MnQ2N2c#gid=0

Diaspora

• Diaspora
  • https://wiki.diasporafoundation.org/Main_Page
  • https://wiki.diasporafoundation.org/Federation_Protocol_Overview

• https://news.ycombinator.com/item?id=5733297

GNUnet

• GNUnet is a framework for secure peer-to-peer networking that does not use any centralized or otherwise trusted services. A first service implemented on top of the networking layer allows anonymous censorship-resistant file-sharing. Anonymity is provided by making messages originating from a peer indistinguishable from messages that the peer is routing. All peers act as routers and use link-encrypted connections with stable bandwidth utilization to communicate with each other. GNUnet uses a simple, excess-based economic model to allocate resources. Peers in GNUnet monitor each others behavior with respect to resource usage; peers that contribute to the network are rewarded with better service. GNUnet is part of the GNU project. GNUnet can be downloaded from GNU and the GNU mirrors.

• http://secushare.org/

• https://news.ycombinator.com/item?id=6194553

GNU Social

uses older OStatus

• GNU Social

• http://activismlabs.org/

• http://programmingisterrible.com/post/39438834308/distributed-social-network
• http://we-need-a-free-and-open-social-network.wikispaces.com/Federated+Social+Network+Applications

Jappix

• https://jappix.com/ - xmpp based

• http://jappix.org/
  • https://github.com/jappix/jappix

buddycloud

• http://buddycloud.com/
• https://buddycloud.org/ - XMPP

Sneer

• http://sneer.me/project.html

Other

• https://github.com/oakes/Nightweb

SOCML

• http://www.w3.org/2005/Incubator/federatedsocialweb/wiki/SOCML_proposal
• http://www.w3.org/2005/Incubator/federatedsocialweb/wiki/SOCML_Standard
• http://www.w3.org/2005/Incubator/federatedsocialweb/wiki/SOCML_Technical

Aggregation

PubsubHubBub

PuSH

• http://code.google.com/p/pubsubhubbub/

• http://disattention.com/notes/pubsubhubbub/

• http://indiewebcamp.com/PubSubHubbub

trsst

• http://www.trsst.com/
  • https://news.ycombinator.com/item?id=6280727

• http://threads2.scripting.com/2013/march/makeATwitterOutOfRss
• http://www.wired.com/wiredenterprise/2013/08/trsst/

http-subscriptions

via webhooks

• https://github.com/progrium/http-subscriptions/blob/master/SPEC.md

to sort

• http://www.wikiservice.at/user/milk/wiki.cgi?ContentManagementSystemsAndDataPortability

• https://we.riseup.net/cgdev/similar-applications

oEmbed

• http://oembed.com/
  • https://en.wikipedia.org/wiki/OEmbed

• https://code.google.com/p/jquery-oembed/

Hyperlocal

• http://en.wikipedia.org/wiki/Hyperlocal

• http://daviswiki.org/Front_Page

• http://openblockproject.org/