Welcome to 1.3.2, another checkpoint rather than a full update. This blog post summarizes the features added over the last month and a half.
This version brings some long-awaited features, such as sign-in with Google, a public API, reports and rejection appeals, and database improvements, which lay the groundwork for upcoming features.
Signing in
You can now sign in with Google. If you already have an account, connect Google in your account settings first. Accounts are never linked automatically by e-mail address, so signing in with a Google account that isn't connected starts a new sign-up instead.
Accounts can also be protected with multi-factor authentication using passkeys. After your password or Google sign-in, you confirm with a passkey on your device. When you add your first passkey you get a set of recovery codes. Keep them somewhere safe, as they are the way back in if you lose your passkey.
We also send an e-mail when someone signs in to your account, so you notice if it wasn't you. This is on by default and can be changed under notification settings.
A public API
SimPictures now has a public, read-only API, documented at /docs/api . It returns the latest pictures of an aircraft by its registration, or of an airport by its ICAO code, and comes with an OpenAPI document for tools that read one.
Every picture returned by the API carries a link to its picture page and an attribution line, and both must be shown with the image. Pictures licensed All Rights Reserved are included as well, and may only be displayed as delivered by the API, linked and attributed. The Terms of Service were updated to cover this.
Reports, requests and appeals
You can now report a picture, member or comment that breaks the guidelines. You can also request a change to a picture, addon or airline, for example a wrong registration or a missing developer, and ask for one of your own accepted pictures to be deleted.
If a submission of yours is rejected and you think the decision was wrong, you can appeal it once per picture. Rejections also got new reasons, "Inaccurate livery" and a custom reason, and several existing reasons were reworded to be clearer.



