A multiplayer geography game where players compete to locate cities and flags on a map in real-time.
Posio is an open-source multiplayer geography game where players compete in real-time to locate cities and identify country flags on an interactive map. It uses WebSockets for live gameplay synchronization and provides an engaging way to learn world geography through competitive challenges.
Educators, developers creating educational games, and geography enthusiasts looking for an interactive, self-hostable multiplayer experience.
It offers a fully open-source alternative to commercial geography games, with real-time multiplayer capabilities, easy self-hosting via Docker, and a modern tech stack that eliminates complex JavaScript frameworks.
A multiplayer geography game using Websockets
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses Django Channels with WebSockets for live score updates and player synchronization, enabling competitive gameplay as highlighted in the key features.
Leverages HTMX for dynamic UI updates without full page reloads, reducing client-side complexity compared to heavy JavaScript frameworks.
Includes Docker Compose configuration for simplified setup and running, making self-hosting straightforward as shown in the quick start guide.
Offers two specific geography challenges—city identification and flag recognition—tailored for interactive learning, detailed in the README.
Built with GeoDjango for accurate location-based queries, ensuring reliable gameplay mechanics for map interactions.
Requires manual installation of GeoDjango with Spatialite and Redis, which can be error-prone and time-consuming outside containerized environments.
Only includes two pre-defined game modes; adding new geography challenges would require significant backend and frontend development effort.
The README provides basic setup but lacks detailed guides on customization, API usage, or scaling, hindering advanced modifications.
Relies on Redis for real-time functionality, adding operational overhead and potential points of failure for self-hosted deployments.