Up for Debate: Subscription Center & User Plans (User Registration)

Open
#602 21 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
authorization, payments

Research direction

No files, tests, or entry points are named. Start by resolving the open questions about user plans, active-device limits, feature access, and PayPal before locating implementation areas. Done means the subscription model and scope are agreed, rather than merely discussed.

Written by the indexing model from the issue text.

Description

Discussion Enhancement

as pointed out by several users, a subscription system may be useful.
I am not against subscriptions necessarily, especially seeing as streama is sometimes used for custom content.
However, I think this requires some concept work.

  • What kinds of user plans are there supposed to be?
  • should certain plans limit the amount of active devices used per user?
  • should certain features only be available for certain user plans, such as direct download?
  • would paypal be good enough?

What are your thoughts guys? Does this break the spirit of the application or can there be good use for this?

Dominant language
JavaScript
Stars
9.8k
Forks
978
No merged PRs in 30d

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.

More from streamaserver/streama

All issues in streamaserver/streama

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.