What is EOOPS? It is module for XOOPS 2.6 (currently) that has all the behavioral mechanism of a federated social network to start with for the XOOPS 2.6 platform, we of course are looking later on to expand it to Drupal, Joomla and so on.
It is using Transient data modelling so the bare bones of it provides ‘Facebook‘ like features which is one of the most common thing asked for in any CMS/Portal Solution with these like functions however with introducing a simple XML Document to expand the transport of information you can get it to socially syndicate and function forums, polls, events basically any form of module for XOOPS as it is using an Elastic Open Object Data model, meaning the sociologies can expand in any direction necessary for the platform to expand. It has a tracker similar to a torrent system which I am building temporarily on www.eoops.org.
Would you be interested in joining this project that through development we hope to finally fill the gaps in social outfall, with the various emerging technologies of federated networks - that have been happening with regards to Federated Social Networks. One different it a document that is some node of data assigned a documented has a time to live, so eventually if the time is reach is deleted from the network, it also uses self-discovering system and scheduling as well for smaller system.
Unlike a syndicated network based in centralization, the EOOPS Social network stems many sites in a decentralized model. This means that forums can receive more posts from threads raised on one website, when the thread syndicated across the transport layer it becomes transient and may sit in many different forum modules for example, like newbb, phpbb, xforum and so on. As the article has been provide a unique document identification checksum based on the signing of the node (Your website) by the tracker in your hive this documented also has parent child relationships.
The network uses AES Encryption to simplify the transport layer from self-signed SSL or other forms, it is the same base encryption anyway! When you install EOOPS the tracker provides the installer with a service signature, node key and node salt, the signature is like the network address of your EOOPS installation.
However the key and salt are private to the service node and tracker if they are ever in transits outside of the tracker or your EOOPS client then they are either md5 or sha1 hashed as private data, these are used for encryption and transport layers.