LibreSocial — Feature Overview (with examples)
Two audiences: users (what the social-network application does) and developers (what the framework offers to bundles). Each feature names the component that implements it.
User-facing features (application plugins)
| Feature | Plugin | What it does / example | Built on |
|---|---|---|---|
| Profiles & login | loginplugin, profileplugin |
Create a profile; login is keyed (ECC identity), no account server. First run generates/loads your key pair. | security, DDS |
| Wall / status posts | wallplugin |
Post a status; friends read it from your wall — a distributed list object replicated on storage nodes. | DDS (lists) |
| Friend management | friendsplugin |
Friend requests + friend set; friend-of-friend trust used for access decisions. | DDS (sets), security |
| Photo albums | photosplugin |
Upload photos; images stored as content on PAST, albums as DDS lists; albums are access-controlled per friend/group. | past-storage, DDS, security |
| Groups | groupsplugin |
Group creation, membership, group wall — group data are shared DDS objects maintained by members. | DDS |
| Forum | forum |
Threaded discussions as distributed tree structures. | DDS (trees) |
| Private messaging / live chat | messageplugin, livechatplugin |
Direct messages routed over the overlay to the recipient peer; presence via lifeness checks. | messaging, ring |
| Events / calendar | calendar |
Create events, invite friends; 2026: table-based calendar UI, invalid date-range validation. | DDS, UI |
| Voting | voting |
Polls among friends/groups, results in shared objects. | DDS |
| File storage / sharing | filestorage |
Share files: metadata in DDS, content in PAST with references. | past-storage, DDS |
| Search | searchplugin |
Keyword search across peers; capacity-based result collection (CapSearch) avoids overload of small nodes. | search |
| Notifications | notifications |
Event bubbles for posts, friend requests, birthdays — driven by the framework event system. | messaging/events |
| Commands console | commands |
Text commands (e.g. for storage stats, monitoring access) — modern successor of the 2009 LifeSocial command reference. | messaging, kernel |
| App store | appstore |
Browse/install plugins from a decentralized repository of JARs; updates propagate peer-to-peer. | appstore, kernel |
| Monitoring GUI | monitoring UI bundle | Metrics of the overlay: E2E delays, per-region statistics in a tree-aggregated view. | monitoring |
| Web access bridge | webprovider |
Serves a web frontend against the local peer; TLS support added 2026. | UI, webprovider |
Example: how a wall post travels through the system
wallplugincreates a post object and callsStorageDispatcher.addContent(post, key)— a local, synchronous-looking call (plugin API).- The dispatcher stores the content on the PAST leaf responsible for the key (your user-key range), with replicas for availability.
- Your wall's
DistributedSet/DistributedListDDS object is updated; the object's replicas (on other storage nodes) merge the delta. - Friends' peers subscribe to your wall object; the event/notification system pushes the update; the UI renders it.
- Throughout, SkyEye collects the storage round-trip times for the metrics view.
Example: plugin development (developer view)
A bundle obtains framework services via OSGi (service-oriented design since 2008):
// inside a plugin bundle's Activator
StorageDispatcher sd = context.getService(StorageDispatcher.class);
MessageDispatcher md = context.getService(MessageDispatcher.class);
DistributedSet<String> wall = sd.createDistributedSet("wall/" + userKey, this, AccessType.PRIVATE);
wall.add("Happy birthday, Alice!"); // replicated, merged, persisted on the DHT
md.send(new LifeSocialMessage(recipientId, MessageType.PRIVATE, payload)); // routed over Pastry
The plugin never handles routing, keys, replicas or encryption — the framework does.
(WallPlugin, StorageDispatcher.java etc. in Source/ show current signatures; see
plugin-system.)
Platform features (the framework's selling points)
| Capability | Example / evidence | Component |
|---|---|---|
| No servers | All 2026 test clusters run N equal peers (Docker cluster); even monitoring is decentralized. | whole system |
| Scalable DHT storage | Content is addressed by hash keys and stored at overlay leaves with replication; benchmarks to thousands of simulated nodes. | past-storage, tester |
| Shared collections | Friends, walls, albums, forums as first-class DDS sets/lists/trees with conflict merging. | dds |
| Access control | Read/owner rights per DDS object using ECC keys; friend-of-friend trust for social privacy. | security |
| Self-observation | Overlay-wide metrics (delays, availability) aggregated over a monitoring tree; convex-hull watchdog against malicious nodes. | monitoring |
| Capacity awareness | Search and storage steer work to nodes that can handle it (CapSearch, capacity management protocol). | search |
| NAT traversal | STUN integration so home-Internet peers participate. | nat-traversal |
| Extensibility | Install a new plugin at runtime through the app store — demonstrated by the 2008/2011–2013 student plugin waves. | appstore |
| Reproducibility | Virtual-network tester replays full platform behaviour offline. | tester |
Feature history (which paper introduced what)
- 2008: platform + plugins concept (ISM 2008, practicum guide); monitoring (SkyEye 2008).
- 2009–2011: security features (LCN 2009), monitored platform (CCNC 2011), flagship platform description (P2P 2010).
- 2014–2015: secure DDS (CTS 2014), app store (Modasia 2015), data synchronization (Gao 2015).
- 2016–2017: canonical DDS, structure cache, access control, CapSearch, SkyEye consolidation (see architecture links).
- 2020: capacity management, caching structures, full system evaluation (dissertation).
- 2026: modernized build, Docker cluster, TLS webprovider, calendar fixes (see timeline).