Suggestions relating to identifying twiddles, stopping twiddle escalation

[KTKate]

So yesterday 3 of us were trying to work out an issue and using twiddles to demonstrate. With all the sharing of twiddle links back and forth it became difficult to tell if you were working on your own twiddle that could be saved, or someone else's twiddle that couldn't be saved. More than a couple times I've seen someone edit a twiddle and think they can share their changes but they didn't realize it was someone else's twiddle and lost what they did. Also when multiple people are working on twiddles everyone ends up forking twiddles so the number of twiddles tends to increase exponentially just to make small edits.

Some solutions to this that came to mind were:

• URL slugs with the title of the twiddle so when there are 3-4 twiddle links in Slack you can tell which one is which.
• Some kind of indication on the top bar (where the title and your user name are displayed) that shows if it's your twiddle or someone elses.
• an indication of whether the twiddle is save-able/forkable.
• setting a twiddle as locked so only the owner can edit & save or as public so anyone can edit & save

We ended up linking a twiddle to an issue in the ember repo. So I don't want to change the twiddle accidentally myself and no longer have it demonstrate the issue when people view the ember issue. I think being able to set a 'read only' mode where you have to maybe uncheck a checkbox to edit the twiddle(or fork it when forking ones own twiddle is available) would be nice in that kind of situation.

[Gaurav0]

So on canary.ember-twiddle.com you keep and save your changes when you fork. Does this work for you?

[KTKate]

This definitely helps. Perhaps when you are not the owner of the current twiddle the 'save' menu item should be disabled. There is the indicator that says 'saved' or 'unsaved' but it's easy to overlook if you've mistakenly tried to save on someone else's twiddle.