# Tactical Media Broadcast Hub

## Many collectives. Many minds. Many signals.

Media activists often face the same problem: a group wants to work together, but the tools are organized around individual accounts.

One person ends up holding the passwords. A few people become bottlenecks. New contributors cannot help without being given dangerous levels of access. Work gets scattered across chats, documents, drives, and platform dashboards.

The Tactical Media Broadcast Hub is designed to change that.

It gives collectives a shared place to organize, create, review, and publish media without turning one person into the gatekeeper of every account.

**Speak with us, not for us.**

## What Groups Can Do

### Work together without sharing passwords

People get the access they need for the work they are doing, not the keys to everything.

A contributor can be allowed to:

- Prepare a post.
- Edit a video description.
- Review another person’s work.
- Publish to a specific channel.
- Manage a group or project.
- Remove their own access when they move on.

The group can see who has access and change it when responsibilities change.

### Organize around projects and campaigns

Create groups for a campaign, a local action, a publication, a show, or a temporary media team.

Each group can have its own members, conversations, files, drafts, approval process, and publishing permissions. Groups can work independently while still sharing material and supporting one another.

### Create channels together

Groups can build media channels that span several platforms instead of treating every platform as a separate job.

The same team can coordinate:

- Video and livestreams.
- Social posts and threads.
- Telegram and Matrix conversations.
- Press statements and newsletters.
- Archives, show notes, and background material.

The Hub helps people adapt work for each place without losing track of the original source, the people who made it, or the decisions around publication.

### Produce livestreams and TV-style channels

Groups can produce more than individual posts. They can operate live and scheduled channels with:

- Multiple live sources and remote contributors.
- Playlists, scheduled programs, and looping broadcasts.
- Scene layouts, picture-in-picture, shared screens, and source changes.
- Lower thirds, logos, chyrons, clocks, and other on-air graphics.
- Preview and program feeds so a team can prepare the next moment before taking it live.
- Live switching, source replacement, and graceful recovery when a source drops.
- Simultaneous distribution to PeerTube and other supported platforms.
- Recordings, replays, clips, and show archives after the broadcast.

This makes a group channel feel like a small community television station: live when something is happening, scheduled when it is not, and built from the work of many contributors.

### Edit documents together

Groups can work together on statements, articles, scripts, captions, briefings, and press materials.

Office documents such as ODT files can be edited collectively. People can review changes, prepare a final version, and keep the publication history with the project instead of passing files around in private messages.

### Use shared pads for fast work

Every project also needs a lightweight space for unfinished thoughts.

Shared pads are useful for:

- Live event notes.
- Breaking-news coordination.
- Interview preparation.
- Production schedules.
- Run sheets and checklists.
- Meeting notes.
- Quick drafts that do not need a full document workflow.

Pads are for moving quickly. Documents are for work that needs editing, review, and a lasting home.

### Find group files and media

Files should not disappear into one person’s private drive.

Groups can keep shared images, audio, video, documents, exports, source material, and finished work together with useful context:

- Which group owns or manages it.
- Where it came from.
- Who contributed it.
- When it was created.
- What project or campaign it belongs to.
- Whether it is a draft, approved, published, or archived.

Members should be able to find the file connected to a conversation, a campaign, or a published piece without searching through somebody else’s account.

### Curate and amplify voices

The Hub is for finding, organizing, contextualizing, and amplifying work made by people and communities.

It is not a machine for speaking on behalf of them. Attribution, consent, authorship, and editorial decisions remain visible to the people doing the work.

## How A Group Uses It

1. A collective creates a group for a project, campaign, channel, or event.
2. Members receive roles that match their responsibilities.
3. The group gathers conversations, files, source material, and drafts.
4. Members edit and review work together.
5. The group decides what is ready to publish.
6. Approved work is adapted for the platforms where people will see it.
7. The group keeps a record of what was made, who contributed, and where it went.

## What This Is Not

- Not a replacement for the communities using it.
- Not a single centralized newsroom.
- Not a reason to hand one administrator every password.
- Not an advertising or engagement farm.
- Not a system that hides editorial decisions behind one organization.
- Not a request for someone else to provide or operate servers.

## A Network Of Independent Collectives

Each collective should be able to decide how it works, who it trusts, where it stores its material, and what it shares.

The Hub helps groups cooperate without requiring them to become one organization. A local media team, a campaign group, a publication, and a network of independent channels can all coordinate while keeping their own identities and responsibilities.

The long-term aim is a horizontally coordinated network of media-making communities:

**Many collectives. Many minds. Many signals.**

## For Groups Who Want To Run It Themselves

The Hub can be run independently by a collective or network. They do not need to depend on the original maintainers for access to their own work.

An independent operator needs:

- A reliable computer or hosted machine.
- A stable internet connection and a domain name.
- A secure place for shared files and media.
- Someone responsible for updates, backups, and member access.
- A clear agreement about who can publish, administer, and recover the system.

The system is designed so large files and media live in durable object storage rather than filling the application machine. Small records about groups, permissions, conversations, and file locations still need to be protected and backed up.

For a larger deployment, it is best to separate the everyday coordination tools from heavy video processing. A group can begin small and add dedicated capacity for livestreaming, video production, collaborative documents, and search as its work grows.

Self-hosting should include:

- Separate storage areas for chat media, shared files, and application media.
- Regular backups of both the files and the records that describe them.
- Secure delegated connections to publishing platforms.
- Clear rules for access, departures, moderation, and recovery.
- A policy for which group conversations can have files copied into the shared library.

Encrypted conversations need special care: a server cannot automatically read or archive files from a conversation it cannot decrypt. Groups can choose designated archive spaces for material that needs to be searchable and shared across the wider media system.

## Closing

**Tools to curate and amplify voices.**

**Speak with us, not for us.**