Questions and Answers
FrontierNav is currently maintained and developed by me: Jahed. It's a wiki platform so the game data is maintained by the community.
Usually, yes if it fits with FrontierNav's vision. Just let me know. But there is a queue. I am only one person and FrontierNav does not pay enough for me to work on it a lot. This means new features will be added depending on how complicated it is, how often it is requested and how interested I am in it. Time is really the key constraint here.
Typically, the amount of game data is based on games I'm interested in. Some games are maintained by other contributors. It does not mean there is a commitment to add any more information, though specific requests are welcome.
FrontierNav's data is community-driven so if you would like to contribute data to help others, you can. See "Making Changes". This will be expanded in the future to let anyone add games and take ownership of data maintenance much like a wiki.
FrontierNav is made to be a companion while playing video games, so ideally it should be out of focus with the main focus being on the game. The easiest way to do this is to use a dark theme which reduces the amount of light emitted by displays which in turn prevents grabbing your attention when you are not focusing on it.
A Light Theme may be added in the future, but it is not a priority. Supporting both Light and Dark Themes is a lot of work when adding and re-designing features as it doubles the manual testing surface since there is no automated way to ensure colours look correct to the human eye.
FrontierNav is a very dynamic application. So to reduce server-side burden (as I am running on a limited budget), your browser downloads the entire latest database for the game. This is typically a few hundred kilobytes at most. After the initial download, your browser will not need to download it again until the database is changed. If you're experiencing consistent slow page loads, make sure your browser's cache is enabled.
FrontierNav uses Firebase to store user credentials. So the sign-in link will be sent by them. To avoid spam, Firebase does not allow this email to be customised at all so it will not have FrontierNav's branding. But do not worry, it is safe. It contains a single link which will automatically sign you in.
To avoid dealing with account hijacking, weak passwords, phishing and general malicious intent, FrontierNav avoids using passwords. You can only login through other social media platforms or a sign-in link sent through email.
If your social media or email account is hijacked, please resolve it with those providers as it is pretty much impossible for FrontierNav to validate your identity without them. FrontierNav takes monthly backups so if an account is hijacked, once you regain access, you can request any lost data to be restored.
- Access logs are stored for 5 weeks for monthly audits of malicious activity.
- Error logs are stored for 1 month for troubleshooting and fixing issues.
- Authentication data (such as emails, names and avatars) are stored indefinitely.
- Application data (such as game libraries and forum posts) is stored indefinitely.
- Data backups are stored for 1 month in case of data loss.
- Application data may be visible to other users.
- All data is visible to admins for auditing and admin-related tasks such as account recovery and backups.
- You can request to remove any of your data, including your account. Contact support.
FrontierNav uses continuous deployment so it is updated constantly as I work on it. You can get weekly news of what has changed on the home page.
Some parts of FrontierNav are open source; the parts that can be used in other projects. FrontierNav's data is open and available under "Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)" which is common for wikis. You can save the data and use it in your own applications within the terms of the license.
FrontierNav's codebase is not open source as it is experimental and there is an overhead in providing enough documentation for others to contribute code. It is also a personal long-term project and there is a personal cost to exposing my private activity to the public. FrontierNav was open source in the past, but due to a lack of contributions, these costs were not paying off.
FrontierNav may become open source again in the future if it can generate enough donations to sustain such an endeavour. If you wish to see the source code for any part of FrontierNav, feel free to contact support. I will try doing a useful write up of it for everyone to benefit.