Document: EOOPS - SCRUM MEETING - 2013-10-27.pdf - 371Kb

Preface

There are a number of federated networks that have been under review by the project admins of EOOPS on SourceForge.net these include Pump.io, Friendica, Diaspia, Lorea, Red, IndieWeb. Notably there is a lot of dead projects as well for EOOPS to skip past. These have been dabbled with and notably found to be rather complex in establishing network transient connect on the federated network.

EOOPS is a social networking module for XOOPS 2.6 it is still in the early development phase of its development life-cycle; we have had a couple of scrum meetings between the project admins wishcraft & michaelmd101. The common result in talking to people wanting to have a social network is to have the features of common networks which are syndicated like facebook.com not federated.

This means that people would like Comments, Channels, Advertisements, Groups, Pages, User Profile, Friends, Poking, Images Galleries, Video Libraries, Chat, Blogs, Notes, Status Updates, News, Likes, Dislikes, Blocking and other features based around the life expectancy of the facebook.com style profiles. Well first I would like to tell you about what the difference of a federated network is to a syndicated network.

We are looking for a team of developers from the XOOPS Information Systems as we will be developing EOOPS as a XOOPS 2.6+ Module similarly to Yogurt Module but as a federated network!

File structure of EOOPS social network Module

This is the folder layout for the pre-alpha planning development of EOOPS, you will find this reflective of the EOOPS Core section of the SVN on Sourceforge.net – it is designed to run with XOOPS 2.6.0


 
Federated network vs. Syndicated network

A syndicated network is classically the ones common place individuals are using at the moment, like facebook.com or twitter.com these are networks which offer syndication with other networks centralised within their structure of business planned outlay & functionality of the website!

A federated network is a serial type collaboration of many websites which user base spans the total routing vectors of the website and username look very similarly to email addresses. In EOOPS we have hoped and have been designing a S2S (Server 2 Server) system similar to the way torrents work but for suspending the federated network amongst many web server similar to the way Peer 2 Peer works this can also have social die-back and because the information federated exchange via the ‘eoops tracker’ which is a place to find other services and announcement of services around on the network, the information exchange is not done by the ‘eoops tracker’ this is done between web server and peer web server, much like how a torrent p2p system works!

The idea of Federated Networks is that they are spanned over many web services and don’t really have the ability to be tracked or sydnicated in survellance and intelligence systems like what was leaked by Edward Snowden with the PRISM system run the USA by the National Security Agency (NSA.gov).

Phase One – Prealpha Planning & Development

The tracker will be operational as the primary one onhttps://eoops.labs.coop orhttp://eoops.org which in its initial phase will be built out of XOOPS 2.6+ as well as the client and social networking module EOOPS for XOOPS 2.6.

We are hurrying slowly with this module as we don’t want to over complicate the environment of EOOPS, we have decided on an XML Document Exchange done through Header discovery of EOOPS.

The XML Document that EOOPS exchanges around the network is what defines the scope of the data allowing anything really as data to be transient of the modules installed on the XOOPS Webserver it is installed on; being exchanges and what connectors and or classes to interface with on the system to syndicate the data across the federated network between peer modules installed on XOOPS and matched groups for cross posting and referencing.

The idea of having XML Documents designed to define the data being exchanged is anyone for a XOOPS Module or other system can script a XML Document and mount the module on the federated network on-top of the existing framework of features requested as base design on the EOOPS XOOPS Module for people wanting to start a social network.

This allows the software to be elastic and transient in design taking the exchange from requested and provided XML Document exchange via the API in the module and the clients peer on the tracker.