#259 Owners can fork their own timelines repeatedly, and see Propose changes on them
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#259
- issue
- state:closed
On timescale.info, the owner of `athan/usmc` could "Fork on server" into their own account, then fork that fork, and so on: nothing limits how many copies one account makes on the server (no rate limit, no one-fork rule), which is a way to fill the database. And on their own timeline, which they can save directly, "Propose changes" (with "Submit pull request") is offered. - An owner doesn't fork their own timeline (Duplicate makes a copy); a fork of a timeline one already has a fork of opens that fork. - Server copies (forks and duplicates) are rate-limited per account. - Propose changes is for people who can't save directly. - A fork offers "Propose saved changes" only once it has saved changes of its own. https://github.com/openchronology/timeline-app/issues/259
Related
- #261 Background catalogue text refresh can fail with "Broken timeline index" while timelines are deleted
- #262 Owners duplicate, others fork, once; propose only without write access (#259)
- Merge pull request #262 from openchronology/fix/fork-rules
- Owners duplicate, others fork, once; propose only without write access (#259)