Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature: Storing media (video, audio, image?)

Open
#1,065 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
aws, go

Research direction

The issue names no source files or tests; it describes possible media storage approaches, retention policies, and handling IDs for asynchronous model jobs. Start by reading the existing audio-file logging implementation and the plugin system mentioned in the discussion. The issue needs a concrete scope and acceptance criteria before work can be considered done.

Written by the indexing model from the issue text.

Description

Conversation from Discord:

Aziz
Hi SantiagoDePL I was curious about Video generation models. Following OpenAI's API specification, its a request and poll method. Where you call the endpoint /videos with a prompt and other variables, then you get back an ID and poll an endpoint until it says "completed".

Have you thought about how you would implement that for GoModel? I imagine it would need to have connections to a storage - or multiple options - type/platform. Could be file server, or buckets, etc.

Then also there's the time to live for the video itself. I think openai allows the videos to live for 1 hour before they're deleted. I didn't see this in the roadmap when I checked last.

SantiagoDePL
I still need to think about it - that’s why there is no details about it on the roadmap page.

Definitely database is a wrong place to store files. Today we log audio files there (when appropriate env variables is set to true). It will be changed.

I can imagine that in first implementation you will be able to set a path for file storage. For example ‘/mnt/files’ . In this case you will be able to mount any storage on Claude/Infra layer there (AWS EFS and S3 would work this way when configured properly).

Later perhaps I will add a native support for S3 and similar cloud services. (It might be done based on the plugins system I recently developed)

WDYT about this?
Of course it will be as much configurable as possible (for example a different retention period for different media types etc.)

Aziz
I think that sounds like a good plan. I think one point to consider is that GoModel needs to:
Store the ID and maybe poll for the user if the user is using a non-self-hosted model (from MiniMax, Gemini, OpenAI, etc.)

Edit: vLLM exposes /content and polling so this is not an issue

Dominant language
Go
Stars
1.2k
Forks
111
Avg merge
14h 43m
Merged PRs (30d)
142

Getting set up

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.

More from ENTERPILOT/GoModel

All issues in ENTERPILOT/GoModel

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.