You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Event federation would be very handy, if we assume that the operating environment will remain as it is currently with each guild running its own event system.
The idea here would be that organizations could import events from other organizations' event systems ("origin server") in their event system ("local server"). One could sign up for the events on either organization's website. It might also allow both sides to administrate the event.
Potential
How this might work:
Add randomly generated federation key to each event
Allow authenticating to relevant event admin APIs with federation key (per event)
Create DB model for external events (or add fields to regular events)
Allow admins to import events with ID and federation key
Fetch external event details from origin server (for event list, at least)
Add webhook for re-fetching updated events, send that to origin server, call registered hooks when event updated
We have some implementation options here.
Event details stored only on origin server, local server has only event list data, client calls origin server with CORS
All details cached on local server, client calls local server
Implementation 1 would be much simpler server-wise. It would also ensure that signups are fair for everyone. However, it requires a bit more thought in how we ensure everyone's frontends work well.
Federated administration
We also need to choose if federated admins can edit events or view signups. This also affects which APIs the federation key should be valid for.
In order to preserve audit loggability, federated administration might require servers to explicitly trust and authenticate each other (signed JWTs?), instead of just allowing access with a shared per-event key.
The text was updated successfully, but these errors were encountered:
Event federation would be very handy, if we assume that the operating environment will remain as it is currently with each guild running its own event system.
The idea here would be that organizations could import events from other organizations' event systems ("origin server") in their event system ("local server"). One could sign up for the events on either organization's website. It might also allow both sides to administrate the event.
Potential
How this might work:
We have some implementation options here.
Implementation 1 would be much simpler server-wise. It would also ensure that signups are fair for everyone. However, it requires a bit more thought in how we ensure everyone's frontends work well.
Federated administration
We also need to choose if federated admins can edit events or view signups. This also affects which APIs the federation key should be valid for.
In order to preserve audit loggability, federated administration might require servers to explicitly trust and authenticate each other (signed JWTs?), instead of just allowing access with a shared per-event key.
The text was updated successfully, but these errors were encountered: