-
Notifications
You must be signed in to change notification settings - Fork 685
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Journalist API v2 #5104
Comments
For more effective sync, we'll also want to consider ideas like:
|
@redshiftzero @kushaldas @eloquence I would love to start some work on API v2. Let me know if I can start some work on it. |
Flagging for in-depth discussion at a future tech mtg, potentially followed by a clearer requirements spec. |
I'd like to hear more about this idea @eloquence! (My first thoughts are: would that involve comparing two states? Would the clients have to provide some information about their own current state, or the last state they retrieved?) I got here from freedomofpress/securedrop-client#1285 (comment) |
Description
this is a list of endpoints we want to change/modify/add for the next version of the journalist API:
GET /sources
should only grab source metadata without key information (see us needing to memoizeCryptoUtil.getkey
in Cache CryptoUtil.getkey (redshiftzero's idea) #5100 to make the v1 version fast enough for the beta workstation release)GET /sources
should omit the number of submissions/repliesGET /sources/<source_uuid>/key
endpoint that gets the key detailsnote: this ticket right now is just for ideas and needs further discussion prior to implementation
The text was updated successfully, but these errors were encountered: