Closed mitra42 closed 4 years ago
how are we encoding the ids? I had thought that it was just as a hexstring in which case shoulding it by prefix bytes?
The original EphIds are 128 bits I believe. Yes - we are using a hexstring, though I think that was probably a bad idea and that we should use something more compressed, which is why I'd rather keep this prefix spec as bits.
ok, what do you want to use?
On Mon, Apr 27, 2020 at 7:13 PM Mitra Ardron notifications@github.com wrote:
The original EphIds are 128 bits I believe. Yes - we are using a hexstring, though I think that was probably a bad idea and that we should use something more compressed, which is why I'd rather keep this prefix spec as bits.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/mitra42/bct-server/issues/70#issuecomment-620335000, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAYRXDZJQG3U4NNIAV3WUTROY3S7ANCNFSM4MSNJLNA .
Live
Will add a signon endpoint - this will allow us to pass a number of pieces of information between client and server. It should run at startup and once a day. Note there is intentionally no link between this request/response and status/send or status/scan
There is a balance to be drawn here between providing info that makes the whole system work better, and so much info that privacy is violated.
Here is a straw-person, it might not strike the right balance.
Request fields (client to server)
Response fields (server to client)
Discussion of any of these can go in the comments,