LibreSocial · Documentation

LibreSocial — Architecture Overview

LibreSocial (formerly LifeSocial.KOM) is a fully decentralized, P2P-based social network: there is no server tier at all. Every user runs a peer (an OSGi/Equinox process); application features are plugins on top of a reusable P2P middleware framework. The framework is the real product of the project — the social-network plugins are a demonstration that it works.

Related overview literature: LibreSocial: A peer-to-peer framework (2020, __RELEVANT), Peer-to-Peer based Social Networks: A Comprehensive Survey (2020), LifeSocial.KOM platform paper (IEEE P2P 2010), P2P-Framework overview talk (2013), Graffi dissertation (2010).

Layer model

+------------------------------------------------------------------+
|  Application plugins (org.lifesocial.plugin.*)                   |
|  profile, wall, photos, forum, groups, events, voting, chat,     |
|  search, files, notifications, appstore, webprovider, commands   |
+------------------------------------------------------------------+
|  User interface (org.lifesocial.ui, Swing; webprovider bridge)   |
+------------------------------------------------------------------+
|  FRAMEWORK API (what plugins program against)                    |
|   MessageDispatcher    StorageDispatcher    Events/Notifications |
+------------------------------------------------------------------+
|  FRAMEWORK CORE (com.p2pframework.*)                             |
|   DDS (distributed sets/lists/trees)      Storage on PAST        |
|   Ring & node lifecycle, Adaptive Chord   Security / ECC crypto  |
|   Search (CapSearch)                      STUN / NAT traversal   |
|   Monitoring (SkyEye) + datacollection    Tester / unit tests    |
+------------------------------------------------------------------+
|  Overlay: rice.freepastry (FreePastry fork, merged w/ las2peer)  |
+------------------------------------------------------------------+

Everything above the overlay talks to Pastry only through the framework; plugins never see routing, keys, or replicas. Details per component on the linked pages.

Components

Component Package(s) What it provides Deep dive
Application kernel & launcher org.libresocial.launcher, org.lifesocial.core.* OSGi bootstrap (Equinox), configuration, logging, virtual filesystem, console app-kernel
Overlay (Pastry) rice.freepastry, com.p2pframework.network.* DHT routing, node ids, group/range routing, Kademlia-style maintenance overlay
PAST storage com.p2pframework.storage.past persistent content storage on overlay leaves, replication past-storage
StorageDispatcher com.p2pframework.storagedispatcher single local facade for get/put/remove of content + DDS objects; caching hooks storagedispatcher
Distributed Data Structures (DDS) com.p2pframework.DDS sets, lists, trees as replicated shared objects keyed in the DHT dds
Message dispatch com.p2pframework.message, com.p2pframework.messagedispatcher unicast/multicast/anycast messaging, pub/sub events, app message API messaging
Monitoring (SkyEye) com.p2pframework.monitoring, com.p2pframework.datacollection DHT-tree-based metric aggregation, probes, monitoring GUI monitoring
Security com.p2pframework.security, …security.ellipticcurves identities, login keys, access control, ECC-based encryption security
Search com.p2pframework.search DHT-keyword search, capacity-based result collection (CapSearch) search
NAT traversal com.p2pframework.stun STUN-based address discovery, symmetric-NAT handling nat-traversal
Tester & unit tests com.p2pframework.tester, …unittests virtual-network simulation, benchmark harness tester
App store com.p2pframework.appstore, plugin appstore decentralized plugin/JAR distribution and update appstore
Plugin system & UI org.lifesocial.plugin.*, org.lifesocial.ui 17 OSGi service plugins, Swing UI, webprovider bridge plugin-system

Core design decisions (why the system looks like this)

  1. Structured overlay (DHT), not unstructured Gnutella-style. Routing and object location need guarantees and predictable depth; monitoring and storage sit on the same DHT keyspace (Pastry, 2001; overview talk 2013).
  2. Monitoring on a DHT-derived tree (SkyEye), not centralized and not gossip. Centralized monitors violate the no-servers principle and create a bottleneck; gossip converges slowly and gives stale aggregates. The tree over the overlay gives fast, stable aggregation. Decided in Graffi's dissertation (2010), consolidated in SkyEye __RELEVANT (2017), hardened against malicious parents in Convex Hull Watchdog (2016).
  3. DDS instead of raw key/value pairs. Social data is collections (wall, friends, albums). DDS models them as replicated objects with merge semantics; later secured and access controlled (Sets/Lists/Trees 2016, Secure DDS 2014, Access Control 2017).
  4. Local dispatchers as the plugin API. Plugins call StorageDispatcher/MessageDispatcher locally; distribution is the framework's job — this kept the platform stable across all rewrites (2008 design, Podrajanski 2008; still the API in the 2026 code).
  5. Capacity-aware placement. Homogeneous DHTs ignore that social-network nodes differ in capacity; storage indirection and capacity management protocols fix this (Wette 2011 MA, Adaptive Chord 2013, Capacity Management 2020).
  6. OSGi modularity from day one. Features are bundles; the platform can be minimized or extended at runtime (Alvite 2008/2009, plugin practicum guide 2008).

Evolution and supersession notes