Feature Requests — Video Controls Plus | Vote & Suggest

The Video Controls Plus feature requests page is a public roadmap and voting system. Users submit ideas, the community upvotes them, and the most-voted requests typically ship in the next one or two release cycles. The page is the single source of truth for the project's near-term direction — what is already shipped, what is in progress, what is planned, and what has been declined with a written reason. There is no email gate; signed-out visitors can read and search, signed-in users can vote and submit.

Use cases

Suggesting a feature that solves your specific workflow

If a feature would unlock a daily task — say, exporting saved A-B loops as a JSON manifest — submit it. The maintainer triages every submission and either accepts (queued by votes), rejects (with reason), or merges (with an existing request).

Voting on existing ideas to influence the roadmap

Even without submitting, voting matters. Items with more votes ship sooner; items with fewer votes drift down the queue. Five minutes of voting once a month meaningfully shapes the roadmap.

Researching whether a request you have is already filed

Before filing, search the page. About 30% of new "feature requests" turn out to be duplicates of an existing item — adding your vote to that one moves it up faster than filing a new ticket.

Tracking when an accepted request ships

Each item has a status: Submitted, Accepted, In Progress, Shipped, Declined. Accepted items show the target version; you can subscribe to status changes via email.

How it works

1. Browse or search. The page lists all open and closed requests. Search by keyword; filter by status (Open, Accepted, In Progress, Shipped, Declined).
2. Vote. Sign-in required. One vote per request per user. Removing a vote is allowed; vote-stacking is detected and reverted.
3. Submit. A short form: title, description, expected workflow, willingness to test. The maintainer reviews within 7 days.
4. Track status. Subscribe to a request to get an email when its status changes (e.g. Accepted → In Progress → Shipped).

Examples

• A user requests "JSON export of saved loops". Submitted → 12 votes in the first week → Accepted with target v15.0 → ships ~6 weeks later → marked Shipped with a link to the changelog entry.
• A user requests "video downloading". Submitted → flagged as duplicate of an earlier request → merged → that request reaches Declined status with reason "out of scope per project mission; use a dedicated downloader".

Frequently asked questions

How are requests prioritized?

Vote count is the primary signal. Maintainer judgement (technical feasibility, scope alignment) shapes the order within similar vote tiers. Items below ~5 votes typically wait until they accumulate more support.

Why was my request declined?

Declined requests have a written reason — usually "out of scope" or "duplicate" or "would add unsustainable maintenance burden". The reason appears on the request page.

How long until an accepted request ships?

Median 4–8 weeks. Items with a target-version label have a more specific commitment.

Can I withdraw a request I submitted?

Yes — open the request and click Withdraw. Other users' votes on the request are released.

Is there an SLA on response time?

Maintainer aims to triage every submission within 7 days. Nothing is contractual; the project is volunteer-run.

Can I submit anonymously?

No. Sign-in is required to prevent vote-stuffing. Your username is shown on the request; you can use a pseudonym.

Tips

• Search before filing. Duplicates are common; adding a vote to an existing request is more effective than starting fresh.
• A specific workflow description ("during practice I want X so that Y") gets more votes than a vague feature pitch.
• Vote thoughtfully — five concentrated votes on the items you really want move the roadmap more than 50 scattered votes.
• Subscribe to your top 5 requests. Email alerts when they change status mean you do not need to check the page weekly.

Limitations

• Sign-in required for voting and submitting (not for reading) to prevent vote-stuffing.
• Triage SLA is informal: 7 days is a goal, not a contractual commitment.
• Some requests are declined for scope reasons (e.g. video downloading, DRM bypass). The decline reason explains why.

Last updated 2026-05-06 by Ahsan Mahmood, maintainer.