Flat-file PHP publishing backend

Ship screen-recording links, not infrastructure.

MojoLoom Share Server is the server-side companion for MojoLoom Desktop: resumable uploads, unlisted public playback pages, playlists, trash and restore, analytics, and direct Apache byte-range MP4 delivery without a database or framework.

Open Developer Guide Service Health

5 MiBChunked binary uploads built for reliable retries

1 Share URLStable links across media replacement and restore

0 DBPortable storage made from JSON, manifests, and MP4s

Desktop-first by design

MojoLoom Desktop stays in charge of metadata, replacement, trash, and synchronization. The browser only handles playback.

Portable data model

Migrate by copying the application and storage trees. No database dump, background worker, or hidden external state.

Operational hardening

Hashed API keys, strict identifier validation, denied writable storage, account-wide share disablement, and locked atomic writes.

Shared-hosting viable

Built around Apache, PHP, cron-compatible maintenance commands, and direct static MP4 delivery for efficiency.

Focused capabilities, not platform bloat.

A compact publishing stack for large screen-recording files and remote video management.

Video lifecycle

Reserve identities before upload, resume chunks out of order, verify whole files, atomically replace media, and preserve share URLs.

Core API

Public playback

Serve unlisted video and playlist pages with mobile-friendly HTML5 playback, speed controls, pending-state polling, and unavailable states.

Viewer UX

Library sync

Enumerate account-owned videos and playlists with signed cursors, revisions, and deterministic ordering for desktop resynchronization.

Desktop sync

Maintenance

Run cleanup, analytics compaction, consistency checks, key rotation, and account-wide public share suspension through CLI commands.

Operations

Analytics

Collect pseudonymous visits, starts, completions, heartbeats, and playlist selections without storing raw IP addresses.

Privacy-aware

Start with the guide. Integrate with the contract. Operate with simple files.

The documentation covers the upload state machine, route-prefix hosting quirks, operator commands, migration approach, and the gotchas that matter during real desktop integration.

Read Help API.md Security

Deploy in any web-accessible folder and configure clients with that folder's exact api/api.php URL. Configuration, source, and storage records are intentionally not public.