sync.day

sync.day (约时间) collects availability for a fixed-length event, like When2meet. Flow: create_event (or parse_event_text first to turn a sentence into settings) -> share the returned url -> each person calls submit_availability with the start keys they can make -> get_event shows the ranked starts. Slot keys are candidate START times in the form YYYY-MM-DDTHH:MM (naive local time, no timezone). Once 2+ people answered, get_event.voteOptions lists the starts EVERYONE can make; people approve any number of them with vote_time, and the organiser settles it with decide_time (which locks picking and voting until decided with start=null). Identity: submit_availability and vote_time take an `identity` string: a random secret of at least 16 chars that you generate and keep per person (e.g. 32 hex chars) — never a plain user id or name, because anyone who guesses it can act as that person on every event. The server stores only its hash; the same identity later updates the same row, votes need an identity that already submitted at least one start, and names are display only (they may repeat). Keep the adminKey/adminUrl private: it is needed for update_event, remove_participant and decide_time.