backend api support for advanced urls
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 46
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Investigate how to best add api support for user-set custom urls via /advanced/ or /m3u8/.
E.g. strims.gg/advanced/https://example.com works as expected but (probably) the "/" in the URL confuses the admin API for e.g. setting hidden attribute.
The bigger issue is probably that we use un-encoded URLs as "parameter" on the site (though it improves usability/readability...).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace how /advanced/ and /m3u8/ URLs are handled and how the admin API parses URL parameters. Investigate the unencoded slash behavior, then define the change as supporting custom URLs in admin operations such as setting the hidden attribute without breaking readable site URLs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100