Skip to main content

The event console catches up: join links, a calendar and SOS on the wall

· 3 min read
Massimo Di Stefano
FastGIS author

The server learned to invite riders by link, hand them a calendar file, start a group ride when an event goes live and tell the organisers when a rider raises an SOS. The desktop console now does all of it from the organiser's side.

On the Roster tab an organiser makes a join link, for 7 to 30 days, and the console shows it once beside its QR code: copy it, save the code as a picture to print for the meeting point, then close it. The server keeps only a fingerprint of the link, so it is never shown again; the list below says when each link was made, until when it works and how many riders it brought, with a button to revoke it. Anyone who opens it signed in is on the roster with an invitation to answer. The link carries no names. The phone side of opening it comes with the phone's event screens.

The calendar​

Next to the event's date, anyone on the roster can download the event as a calendar file: the start and end and every stop with a time, in the event's timezone and your language. Download it again after a change and your calendar updates what it already has.

What going live did​

When the owner switches the event to live, the console says what happened to the roster's group ride: it started on the event's route, a ride was already running and is used as it is, or the event is live without one and why, for example a route that is an edited line rather than a planned one. While the event is live a line under the title says how many riders are in the ride and who leads. Finishing says the ride ended for everyone and positions stopped.

An SOS on the wall​

If a rider who agreed to share alerts raises an SOS or crashes while the event is live, the live wall hears it on the push socket the moment the organisers' phones ring: a red banner with who, what and where, the browser tab's title flagged, a red marker where it was raised, and one line to copy for whoever is going to help. When the rider stands it down, the wall says so within half a minute. The wall also says plainly when the event is not live: positions and alerts reach it only in the live window.

Checked on staging with two test accounts: the link and its QR code, the calendar file, a ride started and one refused, an SOS raised on the event's route and stood down. The Events page has the details.