Can I trust this software?

Do NOT. This is amateur project with a history of dangerous mistakes.
It is yet not even version 1.
I take absolutely no responsibility if some data get lost.

Why another photo organizer?

Most solutions are bloated and packed with too many features.
They offer complex databases, own image viewer and often editor.
I think I can use another GUI viewer on top of standard directory structure.
I only offer image files management and image preservation tips.

It seems to do nothing

No flags are enabled by default. You must add -r or --recursive flag
to actually index directory recursively.

Long names / Phone cameras

Most digital cameras are standardized to use 8 characters+extension file names
and I will truncate anything longer! I don't care phone cameras do not respect conventions.
If you wish long file names without truncation, apply this patch:

patch api.py < patches/fullnames.patch

However phone cameras rather produce images but not photos, judgment based
on a fact that phones optimize for screens not for paper print.

Errors with external disk

Most (possibly all) disks come formatted FAT/ExFat or NTFS.
These file systems do not support symbolic links and file attributes,
which features are required. Use another file system.
See tips for details.

RAW photos

Changed from not recommended to always save.
RAW files include most complete metadata saved by camera and can be used to
recover and improve images, given raw itself was not lost or corrupt.

Note: raw is basically not open and not reliable format.

* do not hope it will survive decades and still be readable.
* most raw files are silently compressed, so even one bit flip can destroy it.

It is not a good idea to mix RAW with image files, so it is NOT
enabled by default. Use a separate clone with a patch to enable them.
See tips for details.

More formats

It is potentially possible to index any immutable files.
This is not standard and is not enabled by simply adding formats.
It will be necessary to enable long file names also (see patches).

Video

Same as more formats: I struggle to find pattern for video file naming.

Any kind of AI is beyond the scope?

See these threads:

https://github.com/pytorch/pytorch/issues/17621
https://discuss.pytorch.org/t/libtorch-cuda-so-is-too-large-2gb/103155

Looks portable?

Website is too simple

It is deliberately made to look as simple as possible to simplify rendering by simple browsers
including lynx and netsurf. Additionally Web-3.0 glue interface is not something that aligns with project philosophy.