matrix-org / matrix-org/matrix-spec

Streaming file transfers

Open
#432 4 comments 24 reactions 0 assignees View on GitHub
A-Client-Server feature
Dominant language
HTML
Stars
330
Forks
150
Avg merge
2h 21m
Merged PRs (30d)
3

Description

Once upon a time, before Matrix, we had a glorious feature of streaming file transfers - where one client would HTTP POST the file using Range headers as the other would HTTP GET it with Range headers also. It worked surprisingly well; good enough to livestream video and do low-latency push-to-talk whilst leaving copies of files on the media repo.

It'd be nice one day to have this in Matrix too. This would mean ensuring that we can send events *before* the media has finished up loading.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the issue's description of the former Range-header-based HTTP upload and download flow. No files, tests, or entry points are named, so first identify where Matrix media events and media upload completion are specified. Done would require an agreed protocol design that supports sending events before media finishes uploading.

Written by the indexing model from the issue text.

Assessment

Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.