rust-lang / rust-lang/rust-playground
Require Proof of Work to create share links
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 268
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
With #218 , if the solution is to add an "organization account", then the playground could be abused to generate gists. This could be prevented by requiring JS to provide a PoW if the user wants to create a share link.
The amount of work needs to be chosen carefully, I don't know if mobile devices need to be taken care of (because my guess is that the number of users programming on a mobile device in the playpen is rather low).
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
Start by reading #218 and tracing the playground's share-link creation flow. Determine where JavaScript could provide proof of work, how the work requirement should account for mobile devices, and what acceptance criteria would prevent abuse while preserving legitimate share-link creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100