Rethink caching policy #1459
Description
(Feel free to reject this one without further justification. I'm sure the current Implementation exists for good reasons.)
In the past days and weeks, I encountered quite a few situations where we had to ask attendees, volunteers, sponsors and speakers to hard-reload a page to see the changes we discussed with them, or the changes they made themselves.
The current caching policy is probably very good for static content (as in "content that does not change"), but I don't think it serves our use case well, especially in the weeks before and during the event.
This is not urgent, but might be worth reconsidering before EP 2026 :)
Here are a few references to such issues, you will find more if you search for "cache" and "caching" in the EPS and EP2025 discord servers:
- https://discord.com/channels/899729921381912576/1356550840219074601/1395179412776943819
- https://discord.com/channels/1331995051093528636/1363473726003482704/1394951307584081932
- https://discord.com/channels/1331995051093528636/1393843533974339725/1394933365274181793
- https://discord.com/channels/1331995051093528636/1394066477635600574/1394255629731762238
- https://discord.com/channels/899729921381912576/1350454595679424653/1391515256374689832