That statement feels a litle misleading. The only type of cassettes produced today is Type I.
Everything else is new old stock, where you might end up with a decades-old, chemically degraded cassette.
Immich's current integration solutions (like "External Libraries") treat the archive as a read-only view, which leads to a fragmented user experience:
- Changes, facial recognition, or tagging remain only within Immich’s database, failing to write metadata back to the archival files in their original directory structure (last time I checked, might be better now.
- My established, meaningful directory structure is ignored or flattened in the Immich view, forcing the user to rely entirely on Immich’s internal date/AI-based organization.
My goal (am I the only one?) of having one app view all photos while maintaining the integrity and organizational schema of the archival files on disk is not yet fully met.
Immich needs a robust, bi-directional import/sync layer that respects and enhances existing directory structures, rather than just importing files into its own schema.
Zoho has recently (re)launched Ulaa browser (Chromium fork, alternative to Chrome and Firefox) and Arattai (messenger app, alternative to Whatsapp and Singal), which are getting quite popular (Arattai and Ulaa topped Google Play Store recently in messenger and browser category).
https://www.newsbytesapp.com/news/science/meet-ulaa-zoho-s-a...
[editor]
# No remapping, just use vim instead of mcedit
Given that you can specify the bindings config to use at startup with --keymap you can even configure task specific sets of bindings. This combined with extfs and custom menus makes it a great way to make a personal interface to non-file data sources too.