-
Notifications
You must be signed in to change notification settings - Fork 0
Thoughts
Jonah edited this page Nov 21, 2017
·
1 revision
User should be able to create gists from one or multiple files
User should be able to list gists created from files
Should we display:
- Gist name
- Gist description
- Gist creation date
- Gist version
- Gist creator
- Gist comments #
- Gist publicity
- Gist type
- Gist size
- Gist id
- Gist change status
- Gist url
User should be able to pull gists created from files
User should be able to delete gists created from files
The module should keep at local database of gists created from files
- Should there be some kind of way to keep a remote database of created gists?
- Should a login be required?
- Are gists the best idea for this?
- Alternatives?
- What if the user wants to save images or something else than code - can gists do that?
What if the user doesn't need the whole file, but knowns there is, for example, a single function within that file that needs to be copied? We could implement gistr tmppull that automatically removes the pulled gist after a while through zombie process or we could implement gistr removelatest, which locally removes the latest pulled file.
- Should the user be able to update gists created from files?
- Should we keep track of gist versions?
- Is the user interested in, say, usage statistics?
Possible analytics:
- Created gists
- Removed gists
- Pulled gists
- Should the user be able to easily export the local database of created gists?
- Should the user be able to easily import a local database of created gists?
- Are gists rate-limited somehow?
- Should we take care of limiting spam-requests to Github or leave that to Github?
- Should we be worried about others being able to access gists created by some user?
- Gists can be anonymous and secret, but is that safe enough?