Coccinella historical archive

Documentation archive

A guide to the ideas, not a current manual.

The former documentation routes are preserved as historical explanations. Configuration details from old releases may be insecure or obsolete.

How the client fit together

Coccinella was the desktop endpoint. A Jabber/XMPP server handled account identity, presence and message routing; federation could connect one server domain to another.

Accounts and servers

The historic site stated that users could choose a public Jabber server or deploy their own. Account-registration availability depended on the selected server. This archive does not provide accounts or recommend historic servers.

Presence and contacts

A contact list—often called a roster in XMPP—showed subscribed contacts and availability. Contacts could be grouped, renamed and displayed in compact or avatar-oriented styles.

Multi-User Chat

Service discovery could expose conference services and available rooms. XMPP Multi-User Chat supported room history and persistent identities beyond the basic model associated with IRC.

Whiteboard sessions

Users could invite a direct contact or a room into a synchronized whiteboard. The old gallery described all participants receiving an invitation when a whiteboard session was opened to a room.

Modern safety note

Do not rely on historical defaults.Old TLS versions, authentication methods, server addresses and third-party transports may no longer be secure or available. Treat surviving packages as research artifacts unless reviewed and isolated by an experienced operator.

For current XMPP information, consult the standards and community links on the resources page.