Sources

Browse

Page browser · USS Bridger NCC-591
Pages

📡 Communicator

Open channel · USS Bridger NCC-591
Establishing channel…

System Status

CONDITION GREEN

Crew Manifest

STARDATE

Welcome Aboard

USS BRIDGER NCC-591
HERMES-CLASS SCOUT · MK VII · TELETEXT SERVICE ASSEMBLY SYSTEM · LCARS INTERFACE v0.1

Mission Briefing

You are aboard the USS Bridger, registry NCC-591 — a Mk VII Hermes-class scout, authorised for construction by Starfleet appropriation on stardate 0965. A vessel with a distinguished record: from 2270 to 2273 the Bridger mapped the far reaches near the Tholian Assembly, charting some of the most hazardous space in the quadrant. In 2336 she was dispatched to the Qizan Qal'at system to investigate the loss of contact with the USS Crockett. She has seen the edges of known space and returned.

In her current role the Bridger carries a different kind of cargo. This installation is the Bridger Teletext Service Assembly System — pulling pages from multiple source services across the network, assembling them into unified output services, and routing them to the on-air transmission system. All operations are logged. Access to ship's systems is governed by rank. Unauthorised modifications to active services are prohibited under Starfleet General Order 14.

Crew Ranks & Clearances

Ensign
Registered crew member. May browse all source archives and preview assembled services. Cannot modify ship's systems.
Lieutenant
Granted edit access to specific sources or services by their owner. May sync sources, adjust mappings and resolve conflicts within their assigned domain.
Commander
Owns one or more sources or assembled services. Full control over their own resources. May promote crew to Lieutenant within their domain. May publish services to the on-air system.
Captain
Full administrative authority over all ship's systems. May add, modify or remove any source or service. Manages crew roster. Appoints and relieves officers. The first crew member to register is automatically commissioned Captain.

Reporting for Duty

To access ship's systems you must establish your identity using a cryptographic key pair. Your private key never leaves your terminal — only your public key is registered with the ship's computer.

  1. 01
    Open the registration panel. Click Register in the top-right corner of any screen.
  2. 02
    Generate your key pair. Click Generate key pair. Your private key is created locally and stored only in this browser. Back it up — if you clear your browser data you will need a Captain to re-register you.
  3. 03
    Choose your callsign. Enter a nickname (2–32 characters, letters, digits, hyphens and underscores). This is how you will appear on the crew manifest.
  4. 04
    Complete registration. Click Register. If you are the first crew member aboard, you are automatically commissioned as Captain. Otherwise you join as Ensign pending assignment of duties.
  5. 05
    Sign in on subsequent visits. Click Sign in, enter your callsign. The ship's computer will issue a challenge which your terminal signs automatically using your stored private key. Sessions last 24 hours.
  6. 06
    Using a different address or machine. Your private key and session are stored in your browser's local storage, which is tied to the exact URL origin you registered from. If you registered at http://192.168.1.x:3005 your key will not be present at https://www.xenoxxx.com — they are treated as completely separate by the browser. Export your key backup from the original address and use Import / recover key on the new address before signing in.

Getting Started with Sources

Sources are the raw material of the teletext service. Each source is a repository of TTI page files fetched from a remote Git or SVN repository, a local directory, or a web feed. Sixteen well-known services are pre-loaded in the database.

To add a source: sign in, go to Sources, click + Add source, choose the type, enter the URL, and click Save & sync. The system will clone or fetch the repository. Once synced you can click Browse to view individual pages.

Assembling a Service

Go to Service builder and click + New service. Give it a name (this becomes the output directory name, so use lowercase letters and hyphens only). Add mappings — each mapping takes a range of pages from a source and places them at a destination page range in the output. The system detects conflicts automatically and offers auto-resolution. When satisfied, click Publish to write the assembled TTI files to the on-air directory.