Feature idea: Managing gists (with revisions) per user

This is more of a dream idea, bringing it up anyway in case there are low hanging fruits to improve the situation. The problem: How to easily manage "all my playgrounds".

My initial approach to this was to use the permalink feature, and store each permalink in a local bookmarks collection. When iterating on a snippet, I had to load the bookmark from the bookmarks list, and later add the update bookmark in the bookmark collection. Problems were:

• Organizing (manually naming) the bookmarks is a bit tedious.
• When I had a new revision I often wanted to keep the old revision available as well, ending up with many bookmarks v1, v2, v3, ...
• When I'm on a different PC, I did not had access to my playgrounds.

My next approach was to create the playgrounds directly as gists on GitHub. In the first line I would place a comment containing an appropriate URL for loading the gist on Rust Playground. So the workflow becomes: Go to GitHub gists, open gist, copy URL to new browser tab, iterate on the snippets on Rust Playground. When done, I go back to GitHub, edit the gist, and copy/paste the updated content. This avoids the bookmark mess and makes working with revisions easier, but is still slightly inconvenient.

Solving the problem within Rust Playground would probably require the following (most likely difficult) features:

• Discovering all gists of a GitHub user. I guess this is what #584 is about.
• Saving back a gist as a revision of the user gist, if it was loaded from a user.

I'm not even sure if that would be possible theoretically.

Start by reading issue #584, which is identified as the related work for discovering a GitHub user's gists. Then map how Rust Playground currently loads and saves playgrounds, if those entry points are documented in the repository. Done would mean a concrete, agreed scope for discovering user gists and preserving revisions, rather than the broad dream described here.