solid / solid/solidproject.org

Host meeting media

Open
#791 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
183
Forks
152
PR merge metrics
No merged PRs in 30d

Description

In order to assert essential authority over Solid community's media assets, in particular video and audio from meetings, the assets should be published under its own URI spaces. Likely under solidproject.org or solidcommunity.net, e.g.:

`https://solidproject.org/media/{yyyy}/{mm}/{dd}/{file}'

The URI space should a persistence policy. Either extend https://solidproject.org/terms#uri-persistence-policy or have its own policy (wherever it ends up).

It should be archivable by the Internet Archive / Wayback machine.

Media files can be pushed through GitHub (if no filesize limitations?) or Solid server ( https://github.com/solid/solidproject.org/issues/248 ).


For example, here is a very rough estimate from a Solid CG meeting recording in Jitsi

More details of ~150MB webm file, duration 20 minutes
Input #0, matroska,webm, from 'solid-cg_2023-06-21T14_38_36.268Z.webm':
Metadata:
encoder : Chrome
Duration:
00:19:01.58, start: 0.000000, bitrate: 1043 kb/s
Stream #0:0(eng):
Audio: opus, 48000 Hz, stereo, fltp (default)
Stream #0:1(eng):
Video: h264 (Constrained Baseline), yuv420p(tv, bt709, progressive), 1670x1078, SAR 1:1 DAR 835:539, 60 tbr, 1k tbn (default)

Putting any optimisations aside, we could expect 500MB for a 60 minute meeting. Say 26GB of diskspace for 52 meetings. I'm not sure what the bandwidth requirements would be at this time but we don't need anything too fancy, so just hosting raw files is fine.

What may be other technical requirements? What may be the costs?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing URI persistence policy at solidproject.org/terms#uri-persistence-policy and the related hosting discussion in issue #248. Compare GitHub and Solid server hosting against the stated URI, persistence, archiving, storage, and bandwidth requirements; done means a hosting approach and its technical requirements and costs are defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
content, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.