🌟Federation #998
Description
Is your feature request related to a problem? Please describe.
Currently Hi.Events is deployed as a single instance. If now for some reason various venues from one city decide to use Hi.Events, they would still have to create separate accounts for each venue or organizer. And for smaller theaters or concert halls it means choosing between full self-hosting or giving up control by using a centralized platform.
Describe the solution you'd like
I think it could be usefull, if Hi.Events could be federated. This way each venue/organizer could run their own instance while the user has a single account for various venues/etc. but for example could easy discover new events for other venues.
Additional context
I’m aware this would significantly increase complexity, especially around identity, permissions, payments, refunds, legal responsibility, and UX. This is not meant as a concrete or quick feature request, but simply as starting point to discuss whether federation would even make sense for Hi.Events in the long term. I looked around and found Mobilizon, thats also open source and already does federation and maybe even could help with information about their challenges.
What i could see is that accounts and event-informations themself are federated, ticket-handling and everything else should probably itself remain on the venues "home-instance".
As already mentioned, this is just an idea to start a discussion. Feel free to close this issue if federation is not roadmap or in the vision :)