Background

After temporary accounts are rolled out to test.wiki, the team can test the software interface between the client (the app) and the backend platform (mediawiki) to confirm/update our understanding of how it will work.

Current understanding: The engineering tasks in bold are where we have direct control over on the client (the app). The tasks we don't have direct control over on the backend platform (mediawiki) are in italic.

1. User creates a change on the client
2. Change is sent to backend platform unauthenticated
3. Change is approved to be committed by the backend platform (such as passing through abuse filter etc. )
4. To accept the change, a temp account is created and assigned in the backend platform
5. And edit success response is sent by the backend platform back to the client which includes a temp account cookie.
6. Temp account cookie is stored on the clienct
7. User creates a change on the client
8. Change is sent to backend platform authenticated with temp account cookie
9. Change is approved to be committed by the backend platform (such as passing through abuse filter etc. )
10. And edit success response is sent by the backend platform back to the client without a temp account cookie.
11. No change to temp account cookie stored in the client

Open questions:

• If we send that same cookie to another language wiki (that is participating in temporary accounts), will the same temporary account will be automatically created on that wiki and used?
• If the other wiki is not participating in temp accounts (language or wikidata), will the server will do nothing with that cookie, or will it instruct us to expire the cookie, or some other unexpected behaviour?

Task

• Confirm if the above process is how it works in practice on test.wiki and provide updated documentation if needed
• Answer open questions