Live and recent posts from across the Fediverse tagged #photoprism, aggregated by home.social.
PhotoPrism kapta az októberi nagy frissítést: új ONNX alapú képosztályozó és NSFW-detektor, valamint NVIDIA GPU-támogatás az MI-modelleknek. Jobban kezeli a 360°-os felvételeket és automatikus arcnév-azonosítást is hoz — érdekel, hogyan gyorsítja ez a fotókezelésed? Próbálnád a saját NAS-odon?
#PhotoPrism #ONNX #NVIDIA #AI #fotókezelés #NAS #arcfelismerés #Insta360
PhotoPrism’s October 2026 update redesigns its image-classification system around a new ONNX model.
The change improves recognition accuracy, especially in wide photos where important objects may sit away from the centre.
The update also replaces the previous NSFW detection system with a new ONNX-based model.
Users with supported NVIDIA GPUs can now run all of PhotoPrism’s built-in AI models on the GPU rather than relying…
PhotoPrism aduce recunoaștere facială îmbunătățită și procesare bazată pe AI
https://linuxforeducation.blogspot.com/2026/09/photoprism-aduce-recunoastere-faciala.html
#PhotoPrism #ArtificialIntelligence #SelfHosted #Linuxiac #OpenSource #Docker #Privacy
A PhotoPrism frissítése sokkal pontosabb arcfelismerést hoz, még a csoportképeken is több arcot talál — szeretnéd, hogy a gyűjteményed is javuljon, vagy inkább megvárod a migrációt? Új CLI-eszközök és Private/Hidden adatvédelmi opciók is érkeztek. Továbbá jön a natív Insta360 támogatás.
https://linuxmint.hu/hir/2026/09/a-photoprism-az-mi-alapu-fotoapp-meg-pontosabb-arcfelismerest-kap
#PhotoPrism #arcfelismerés #ONNXRuntime #Insta360 #360fotó #privacy #Docker #NAS #MapLibre #libheif
PhotoPrism 260919-28c46a116
Upgraded libheif from v1.23.1 to v1.23.4 including 8 CVE fixes
https://whatsnew.fyi/product/photoprism/releases/260919-28c46a116
Gerade steht noch das Kunststück aus aus #photoprism und #applefotos eine gemeinsame Library zu machen - also konkret - raus aus Apple Fotos und ab nach Photoprism. Was für ein Spaß! Schauen wir mal was der Metadaten Abgleich da so zu Tage fördert was wo drin ist. Mit Darktable geht es danach weiter. Irgendwie bröckelt meine Toolchain. Bei Film war das irgendwie entspannter, schlimmstenfalls scannt man die Negative noch einmal. Ich glaube ich brauche doch eine Pentax 17 :) #pentax #fotografie
Episode 2 de la série DEGAFAM.
Ce matin on s'est attaqué aux Photos.
Je rappelle que le but est de proposer des alternatives par niveau.
Afin que la réilience numérique de soit pas réservé aux technophiles.
1. Mode facile : Le SaaS
Ente parait etre une très bonne alternative accessible.
2. Mode normal : P2P
Ça a fait débat en live, car certaines personnes trouvent que Syncthing est plus rugueux qu'un self host managé avec YunoHost.
Perso je ne trouve pas, donc j'ai mis Syncthing en mode "normal"
3. Mode avancé : Auto-hébergement
-- Immich : C'est le projet le plus prometteur pour un équivalent de Google Photos ou iCloud.
Equivalent à tel point que j'ai ressenti un petit enfermement en coulisses (beaucoup de choses gérées en base et organisation "destructrive" de l'organisation des médias sur le disque (pardon pour le terme, mais en gros Immich refait une orga à sa sauce).
-- PhotoPrism : Plus léger et beaucoup moins de choses gérées en base (plutot en sidecar pour le coup)
-- Nextcloud Photo : Meme si je ne suis pas un grand fan, il faut l'inclure dans la logique d'avoir une suite globale qui répond à plein de choses
4. Mode Hardcore
Comme la semaine dernière avec les fichiers, on a parlé de copyparty.
Et je suis désolé, mais à part l'UI/UX, c'est un super soft...
La vidéo est disponible :
Peertube : https://videos.stackgui.de/w/7hCHZLXLodcZjLNwJD8bM1
YouTube : https://youtu.be/eSKO7VCJQeY
Blog : https://sansdependances.fr/posts/alternatives-gafam-photos-par-niveau-de-complexite/
Replay Twitch : https://www.twitch.tv/videos/2854982629
#degafam #immich #ente #photoprism #synchting #copyparty
Comment quitter les GAFAM : Les photos (ep 2)
The Backup Shell Script for Photoprism and Immich
Reading Time: < 1 minuteWhen I go out to cycle, run, and do other things I take photos and when I come home I sync them to photoprism on one laptop and immich on a separate Raspberry Pi. I use photosync to sync to Photoprism.
Once images are ingested I usually run a script almost daily. Rather than give you the lines of shell script I’ll explain what it does. It checks that the photos SD card is mounted, as well as the backup drive before using rsync to synchronise between the primary and backup locations and then from the laptop running photoprism to the Pi running a second instance of Immich.
You might have noticed that I wrote “second instance”. The reason for having two of them is so that if one work flow has a problem I have the second as a backup. If photoprism and immich in one workflow fail then I have the backup immich instance. The final backup is via kDrive, from Infomaniak. That’s the offsite backup.
I check that the drives are mounted, and I ensure that rsync never deletes because if a drive isn’t mounted, if you’re not careful, then rsync will wipe a drive of its contents. That’s why I have the safety checks.
I also have the safety checks because sometimes the laptop reboots and mounts everything correctly, but other times it does not. Rebooting solves the problem.
The Shell script says that it can’t find the required mount points, and that’s when it is time to trouble shoot. It is usually quick to resolve, and resilient to data loss, so far.
The shell script works well, and I tweaked it once or twice, but this version is stable.
#backup #immich #photoprism #script
🖼 Radiokot/photoprism-android-client
📸 A convenient Android gallery for your PhotoPrism library with plenty of useful features
A mobile photo gallery app for PhotoPrism that enables browsing media through timelines, search configurations, and media sharing features
⭐ Stars: 599
📅 Last Update: Jul 24, 2026
https://github.com/Radiokot/photoprism-android-client
#selfhosted #homelab #selfhost #selfhosting #opensource #android #photoprism
On Resolute Raccoon and Photoprism
Reading Time: < 1 minuteYesterday when I was looking at Photoprism, and synching from one drive to two other drives, and a second instance I noticed that for some reason I only had the last two months of photos. I eventually noticed that the photos are now living in run/media/… rather than /media/… and it is for this reason that Photoprism could see recent photos but not the entire library.
media/username/library still mounts, but the proper mount point is run/media/username/library moving forward. That’s why I could see recent photos but not photos from before the OS update.
I then need to take two further steps, which I have not taken.
The first is: sudo mkdir -p /mnt/medialibrary and then:
# /etc/fstab – clean and reliable
UUID=your-drive-uuid /mnt/medialibrary ext4 defaults,nofail 0 2
disclaimer: This is just an example, not for tutorial purposes.
## Reconciliation
The next step is to reconcile the “media” library that was created with the correct new source at run/media/username/drive and to update the docker yaml file. Once that is done, things are back to the new normal.
I am glad the issue was easy to resolve.
#photoprism #resolute #ubuntu
🧹 Grand ménage sur mes clusters #Proxmox !
On continue d'optimiser l'infrastructure pour garder un environnement propre et performant. Aujourd'hui, c'est un nettoyage ciblé sur les conteneurs #LXC.
LXC supprimés : #HomeTube, #GoMFT, #TubeSync, #Palmr, #Blinko, #MySpeed, #PhotoPrism, #WatchYourLAN, #CalibreWeb, #Termix, #Netvisor.
ИИ-агент двойного назначения
В наши дни каждый разработчик, наверняка, пробовал вайбкодить, а некоторые идут дальше и заводят себе целых ИИ агентов. Однако отовсюду доносятся новости о том, как какой-то AI агент удалил базу данных со всеми бэкапами. Поэтому давайте посмотрим исходных код проектов, которые так или иначе связаны с агентной разработкой.
Sprecht mir nach: Wir 👏 verschicken 👏 keine 👏 Bilder 👏 über 👏 WhatsApp 👏 auch 👏 nicht 👏 per 👏 HD-Upload 👏
(Wir teilen unsere Bilder in bester Qualität via Immich, PhotoPrism oder weiß der Geier. Aber verschandelt wenigstens nicht euere Bilder!!) #immich #photoprism #homelab #homelabbing #selfhosting
Tornare da un viaggio significa quasi sempre ritrovarsi con una quantità ingestibile di foto. Nel caso di Lisbona, il problema non era tanto archiviare gli scatti, quanto riuscire a estrarne una ventina davvero condivisibile: belle, sì, ma anche varie e capaci di raccontare l’esperienza nel suo insieme. PhotoPrism offriva già un’ottima base grazie a geolocalizzazione, riconoscimento facciale, label e strumenti di organizzazione, ma non aveva ancora un modo per comporre automaticamente un album con “le foto più belle” e soprattutto con sufficiente varietà.
Da qui è nata l’idea di un selezionatore AI: una piccola applicazione Java che usa PhotoPrism per recuperare le miniature delle immagini e Ollama per far lavorare due modelli AI, uno multimodale per assegnare un punteggio estetico e produrre una descrizione oggettiva, e un secondo modello testuale per raggruppare semanticamente le foto e selezionarle con più equilibrio.
Il problema vero non era la qualità
Il primo prototipo faceva una cosa molto semplice: prendere le foto da PhotoPrism, inviarle a un modello multimodale su Ollama e chiedere un voto estetico da 1 a 100 insieme a una breve descrizione. Sulla carta sembrava sufficiente, ma in pratica produceva una selezione monotona: immagini molto belle singolarmente, ma spesso troppo simili tra loro.
Era il classico caso in cui un ranking puro ottimizza la qualità locale ma non la copertura narrativa. Se cinque foto dello stesso scorcio o dello stesso momento ricevono voti alti, un algoritmo ingenuo tende a sceglierle tutte. Per costruire un album da condividere, invece, non basta premiare le immagini migliori: bisogna anche evitare la ripetizione.
[…]
#ai #albumFotografici #clusteringSemantico #computerVision #fotografia #java #Maven #multimodalAI #ollama #organizzazioneFoto #photoprism #PhotoPrismAPI #selezioneFoto #selfHosted https://www.b0sh.net/2026/05/ho-costruito-un-selezionatore-ai-per-scegliere-le-foto-migliori-da-photoprism/
@electric pravda, pravda. Ale pořád lepší (dmn) než #photoprism kde se vývoj vleče skutečně šnečím tempem anebo #ente , které postupuje taky rychle, ale nemá fokus a míří všemi směry. Zůstávám u Immichu
Using Photoprism and Immich in Tandem Across Three Machines
Reading Time: 3 minutesTable of ContentsI have an HP laptop running Photoprism, and two Raspberry Pi 5 running Immich. One of the Pi devices is running Immich, solo, and is made accessible via Tailscale when I am on the move. Photoprism runs on the HP laptop and is not available at all times. When the laptop sleeps, Photoprism is not available. This means that I have to consciously decide to ingest the photos to photoprism.
Propagating from Photoprism to Immich
I setup Photosync on my phone to upload the most recent photos and organise them by year and month. This is easy to forget, so I consciously set that up. The reason for this decision is two-fold. The first reason is that by organising photos in this manner it is easy to mirror them to multiple drives, as well as to make them accessible to Immich, and Photoprism on the second Pi I mentioned earlier.
At the time when I set this up I was using the Ubuntu machine daily so every morning I could upload the photos with photosync.
Woupsie Daisies
Recently I allowed the HP laptop to run out of battery, and when it rebooted everything seemed fine, so I went to sync between devices and that’s when the “woopsie daisisies” incident occured. The “Woopsie Daisies Moment” was both catastrophic, but luckily recoverable. The SD card that I use within the laptop didn’t mount properly but I didn’t notice. When I told rsync to sync from the HP SD card to the external hard drive locally, and to Immich on the Pi it deleted all the files on the Mac spare drive. I suddenly noticed that Nextcloud had no more photos so I killed the sync within seconds. When a delete command is sent it goes for a while before the kill command was received.
The impact was that my secondary backup was wiped, and that my cloud backup, as a result was also in danger. When I realised I unplugged drives, safely, to isolate them, until I understood what happened.
Drive not Mounted
When I looked at the mounted drives on the HP machine I checked to see if the external hard drive was mounted. It was, but the photos were gone. It occured a few weeks ago so I don’t remember if the Pi5 was also wiped, but I don’t think it was. I then realised that the primary drive that I was using had not mounted after the dead battery incident. I mounted the drive, and the photos were intact.
A Sync Shell Script
To avoid this mistake from occuring again I made two key changes. The first is that I removed –delete from the rsync commands. If a file is not present rsync will not delete anything. Accidental deletion is almost instanteneous. The second change was to make sure that the shell script checked that the drives are mounted before doing anything. If the drive is not mounted it aborts the transfer.
Now I sync from the local SD card to the local external hard drive. When that’s done I sync the external hard drive to the Pi5 currently running Immich before then syncing from Linux to MacOS and my kDrive cloud instance. Within two or three minutes I have things backed up across the HP machine, the MacOS machine, a Pi5, and Infomaniak.
The Standalone Immich Backup
I have an entirely seperate workflow for my second Pi5. I synchronise to this Pi5 via the Immich app directly. In theory, within seconds of taking a photo it can be synced and indexed by this Pi5. If the Photoprism and Immich suffers an issue such as a describe above, this one is entirely seperate and isolated. A mistake with one worfkflow only affects one workflow.
The Tertiary Backup
The primary worflow goes from Photosync to Photoprism, and then Immich across multple machines and drives. The secondary worflow is from the Immich iPhone app to the Immich instance on a seperate Pi. The tertiary backup is kDrive. All of the photos are automatically backed up by kDrive in the year/month folder structure, so if the primary and secondary workflow fail, I can still revert to the tertiary solution.
Each library uses the same structure therefore migration data from one library to the other should be seamless. This gives me the opportunity to continue learning, and if I make a mistake I have several recovery solutions.
And Finally
The key mistake was not to check that the volume was available. If I had done that, then I would not have run rsync. I have removed that risk by replacing manual operation with a shell script. The second mistake was to have a delete flat in an rsync workflow by default. I removed it. The third mistake was to allow the battery on the laptop to run flat. That’s why when the machine was rebooted it did not mount correctly.
If you see that files are missing, the first thing to do is check that the volume is mounted. If I had done that, then I would have seen it wasn’t and I could have mounted it, and the issue would have been resolved within seconds.
The current workflow is now more resilient, and automated.
#immich #photoprism #rrsync
The "convenience" of Google Photos often comes at the cost of your privacy. If you're tired of big tech scanning your family memories to build a data profile, it's time to switch.
PhotoPrism uses AI to tag your photos and recognize faces locally on your own instance. Same smart features, zero data mining.
Host it on PikaPods from $6.20/mo (sponsor features included): https://pikapods.com/pods?run=photoprism
Sooo #google. Nimm das. #Nextcloud und #photoprism auf einem raspi5 mit 4GB RAM und ein bisschen Unterstützung und gute Ideen von Claude sind wie Google mit Nostalgiefaktor. So Long s****rs!
Aber läuft. #didit #dutgemacht
The latest PhotoPrism update introduces enhanced Ollama configuration options, improved security, and multiple bug fixes related to indexing, folders, and metadata.
https://linuxiac.com/photoprism-ai-powered-photos-app-brings-better-ollama-integration/
Migrating Photoprism From One Machine to Another
Reading Time: 4 minutesDue to the Raspberry Pi 5, and older, having issues with heat throttling and more it makes sense to build a Photoprism on a "normal" laptop before migrating towards the Pi. The process is an interesting one.
Photo Consolidation
The First step is to consolidate your photos from Google Photos, Apple Photos, Flick and any other source you might have. The simplest method is to organise them chronologically, and then to spend time removing as many duplicates as possible. There are tools for that. They will help you add exif data back into the photo exif fields, as well as look for duplicates.
Photo Ingestion
If your library is organised and ready there are three folders that are interesting to us.
Originals
The originals folder is where you put your chronological library. Photoprism will automatically index all the files in this folder. If you have decades of photos this takes time. It applies machine learning to catalogue dates, locations, people, objects and more.
Storage
The storage folder is critical because this is where json, yaml and other metadata files. This is also where the thumbnails are stored and this is key for migrating from a high spec laptop to a limited spec Pi. When I migrated this folder I had 1.8 million files for 110,000 photos.
Import
The import folder works as a stepping stone. It allows you to import photos and videos at a later date. If you select "move" then it will import photos, and then move them out of the folder leaving it empty.
Phone Ingestion via Photosync
Photosync is a partially free app. If you pay once you can unlock more functionality. With Photosync you can setup photoprism syncing. You add a configuration title, for example "laptop" and then you select the destination folder, and make sure to use "create sub-directories yyyy/mm/dd to preserve the hierarchy you spent hours preparing earlier.
Be careful, because usually the default is Device Name + Album Name. There are other options but they are out of scope for now.
The advantage of Photosync is that once it is set up correctly, it will keep uploading photos according to the hierarchy you want, eliminating the need to do things manually.
Moving to the Pi 5
Once all the heavy lifting has been done, and the logs say that tasks are completed you can move everything to an NVMe card or external hard drive depending on budget, and convenience. With an NVMe card and a 400 gb library you still have head room. With a 2-6TB hard drive you have plenty of head room.
It's worth keeping in mind that the docker-compose file for an intel machine and a Pi are different so you will need to find a template for the Pi and ARM architecture.
I like to have a folder /apps/photoprism/ for the docker compose file on the SD card. I also have /apps/photoprism/database on the HD, that was prepared on the laptop, as well as /photoprism/photos, photoprism/storage and photoprism/import on the external hard drive. I prefer to keep the photos and DB separated.
The Thumbnail Mistake
When I migrated from the laptop to the Pi I didn't bother to copy the storage folder because I thought "the thumbnails won't take too long to generate". I quickly realised the error of my ways, shut down the Pi, rsynced the files, and then plugged the drive back in before rebooting the file. Within seconds Photoprism was happy.
If I had let the Pi regenerate all of the thumbnails and video files it would take hours, if not days and weeks.
The Vanished HEIC Files
According to the laptop library I have 119,000 photos but according to the Pi5 I only have 110,000. That's a huge difference. I noticed that the photos that were missing were those taken with a phone, specifically HEIC files. I tried uploading them as jpeg and they appeared almost instantly.
The quick solution is to upload the photos as jpeg rather than HEIC via Photosync. The slow solution, and this isn't a solution, since it makes the Pi unusable for hours is to reindex the library. I am attempting this now.
The Thumbnails Exist
the paradox, in this situation, is that Photoprism, on the intel based laptop already did all of the heavy lifting so Photoprism should just have seen that each photo had a thumbnail and reflected that in the index, instead of re-inventing the wheel.
And Finally
The Good
I was able to migrate my library from one computer to the other and it worked almost flawlessly except for the HEIC issue. If I had transferred jpeg images I would have had a flawless migration.
The Mistake
The mistake is to re-index the entire library, especially in light of the limitations of rRaspberry Pi devices.
The elegant Solution
The elegant solution is to revive an old phone with all these photos, make sure Photosync is installed and setup, and tell it to upload to the Pi5 as JPEG rather than HEIC. It takes more than five minutes, but it worked instantly with a few test photos.
Silver Lining
The Proof of Concept migration was a success. If I had moved between two intel devices it would have been flawless. It's because I migrated from one architecture to another that I hit a little snag. I simply noticed it while writing the blog post.
#laptop #photoprism #photos #pi #Raspberry #selfHosting
Frustrated by Google Photos' privacy trade-offs? 📸
PhotoPrism brings AI-powered organization—like face recognition and world maps—to your collection without the Big Tech tracking.
On PikaPods, you get the full experience with all Sponsor features included, starting at $6.20/mo. Keep your memories, lose the surveillance.
https://pikapods.com/pods?run=photoprism #PhotoPrism #Privacy #OpenSource
PhotoPrism troubleshooting tip:
If PhotoPrism crashes during photo import/indexing, it's almost certainly an out-of-memory kill.
PhotoPrism requires minimum 4GB of swap space. Without it, the Linux OOM killer terminates the process during TensorFlow face detection.
Fix:
sudo fallocate -l 4G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
Add to /etc/fstab for persistence.
#selfhosted #photoprism #docker #linux #homelab #troubleshooting #foss
On Familiar Faces and Forgotten Names
Reading Time: 2 minutesIt's amusing. I look through Immich and Photoprism and I am struck by how many names I have forgotten, but how easily I remember certain faces. I'm also curious to see how I remember certain names after scrolling through faces yet to be identified.
Decades ago when I was playing with iPhoto and Picasa I knew all these people well, and I saw them daily. It was easy to match faces to names. Now it's a challenge, because I haven't seen these people in years, if not decades.
For a while iPhoto and Picasa were happy to encourage us to add names to faces, until people worried about privacy, and the need to deactivate this functionality. It's about privacy.
Now that we are moving back to to an era of locally installed apps, or self-hosting, if we want to use a trendy term, we can allow facial recognition to know which face belongs with which name. The challenge is to remember the name.
If Facebook was still the network of uni friends and their friends, and our families, and friends of theirs, then it would be easy to remember who A, B and C are.
Instead I rely on patience, and triggers. I might not recognise a face for days or weeks, and eventually I remember because by remembering name A and Context C I find the name from that memory subset.
On Immich I have identified plenty of people, but I have 11,000 faces in total, so remembering all those names is highly unlikely. On Photoprism I have recognised 80 faces out of 999+ faces. Each time I recognise a dozen I end up with 999 more faces to recognise.
In some cases I met the people two or three times, so to forget their name is normal. In other cases I spent years seeing these people daily so I should remember their names with ease.
The forgotten names don't really matter. The value of Photoprism, and Immich facial recognition is consolidating my name recollection for people that are part of my current life, whether it is people I cycle, hike, discuss books with or more. It would be nice to recognise people by their names, as well as their faces.
Photoprism V Immich
Immich is head and shoulders above Photoprism when it comes to browsing and naming faces. With Immich you can regonise a face, name it, double check, and return to naming other people within a second or two. With Photoprism it's slow and sluggish. For context Photoprism is slow and suggish on an HP455(need to double check) whereas immich on a Raspberry Pi 5 with 8 gigs of ram is fluid.
And Finally
When Immich and Photoprism instances crash and I need to repopulate a library most of the work is quick and automatic. I remember the name of via ferrata, and places. It's adding a name to a face that I find difficult. That's the part that takes time.
And finally, I do get a sense of accomplishment with recognising a face after days or weeks of trying to remember. Why do we forget names of familiar faces?
#facialRecognition #immich #machineLearning #photoprism
On PhotoSync and Photo Uploader for Photoprism
Reading Time: 2 minutesPhotosync is a photo uploading app that allows you to upload to various devices and cloud solutions with ease. Photo Uploader for Photoprism is a specialist app for Photoprism. The reason for which I bring up both of these apps is that they allow you to sync to photoprism.
When I was testing uploads with Photosync I noticed that I can upload to the Photoprism library directly but that it creates a "current_phone" folder, and adds photos within this folder. Since my originals folder is meant to be clean and chronological this breaks the flow I want.
That's why I tested Photo Uploader for Photoprism. This is a specialist app. It's designed to upload to Photoprism and nothing else. I configured it correctly, went out for a walk and uploaded a few pictures and they appeared right where I expected and wanted them to appear.
Tidy with Photo Uploader
If I use a Fairphone 4, and an iPhone Se, and an Iphone 14 I'd end up with three or four camera folders, each filed with photos. It would require manual maintenance to ensure that the library remains organised chronologically.
With a chronological library photos appear by year, month, day, so whether you upload from camera A or B, or C, they all get organised into the same hierarchy reducing the risk of duplicates, triplicates or worse. It also makes it possible to share your library between apps.
Imagine that you have a photos directory that Photoprism can feed and Immich and Nextcloud can see. If Immich and Nextcloud can see the same directory as Photoprism, then photoprism is the primary interface and Immich and Nextcloud mirror it.
In this way you have a single library to backup and maintain and the others mirror. With rsync you can mirror this drive to a secondary drive for a backup, and you can also get a service like kdrive, iCloud, Google Drive or other to watch and mirror changes either automatically or via cron jobs.
Versatile with PhotoSync
Photosync offeers WebDav, Google Drive, Google Photos, Flickr, Photoprism and more. If you want to you can set it up to sync automatically to the service of choice, and you can tell it to delete photos once they're backed up. I never use the delete after backup option. I prefer to have files mirrored in at least one other place before deleting files.
Date Based Folders
While looking through I noticed that we have the Date Based Formats option, and the option of choosing recording date (year + month + day). I took a test photo this morning and it was automatically sorted into 2026/02/18/filename. By keeping the desired folder hierarchy I have little to no tidying up to do.
And Finally
Photosync and Photo Uploader for Photoprism do almost the same thing. Photosync feels more polished and stable. By allowing me to keep the folder hierarchy I want I can then feed Immich and Nextcloud with the shared folder without worrying about duplicates and triplicates.
If there is a breaking change for Photoprism, or Immich, and I need to start from scratch, my folder hierarchy will simplify the task, thanks in part to how Photosync or Photo Uploader for Photoprism, helped me keep my photos organised.
#apps #iOS #mobile #photoprism #photosync #upload
Sorting Photoprism Photos With the Mistral Cat
Reading Time: 3 minutesI chose to experiment with Le Chat by Mistral, the French AI alternative to Gemini, Claude and CatIFARTED (ChatGPT). For the experiment I copied my Photoprism photos from the drive I use that is connected a Raspberry pi to a laptop before running scripts to sort and remove duplicates. It worked well, with a nice little bonus which I'll expand on later.
Goal: Clean Up Duplicate Photos
My objective was to Remove duplicate photos from a large collection while keeping the best version of each file. I Used jdupes to identify duplicates and a custom script to decide which files to keep.
The sources of duplication were that I imported photos from Google Takeout on one side, as well as from two or three iphones and an android phone. I suspect that Photosync might also contribute by encouraging the creation of a folder per device that we import from.
Custom Rules for Keeping Files
After running jdupe I set up custom rules that looked at file Naming: I told it to Prefer IMG_ or VIRB over hash-named files. iPhones, Android phones and photo cameras never, or rarely, use names that are hashes. These are usually created by Whatsapp and similar apps.
I chose to apply directory priority to Keep files in human-readable directories (e.g., "Spain bike ride") over generic ones (e.g., "Photos from 2018"). Google Takeout creates two or more folders. It creates a primary year folder with all photos from that year, as well as secondary event specific folders based either on the name we chose, for example 'spain bike ride' or date based, if we did not give a specific name.
In the final step I noticed that it seemed to be choosing to delete HEIC files, rather than .JPG/.JPEG files. As HEIC are usually the original I want to keep the original. Eventually I saw that we had duplicate HEIC files, in which case I allowed it to remove duplicates of this file type. Finally I noticed that video files were either kept as mov files or converted. I accepted to have a rule to choose.MOV over .MP4. I used Le Chat (The cat) to help me understand the output from jdupe runs.
Script Development and Testing
As we progressed through the project The Chat offered three types of automation. It suggested Digikam, Pillow, a bespoke python script or using exiftool. In several cases it Wrote a Python script to apply the rules and generate a list of files to delete based on the output from jdupe being run.
Testing and Iteration
Part of collaborating with AI tools is experimentation and iteration. It's about running a command, seeing the output, understand what you see, and then perfecting the command until you get what you want. It's also about seeing opportunities.
One of the scripts I got The Cat to run was to check the "to delete" list and check if they had exif data for the creation date. i.e. the date when photos were taken. When a script confirmed that this was the case, that's when the process of fine tuning the deletion script advanced. These are the rules we mentioned above.
Verification and Safety Checks
We ran a lot of dry runs. When you run dry-run jdupe it checks for duplicates and outputs to the terminal. When you have thousands of duplicates the terminal window forgets plenty of results. that's where writing to a text file helps. It's persistent.
The beauty of these text files is that they're light, and you can share them with The Cat and the cat, in some situations, will actually run the script you discussed with it, rather than outputting the python script. This differs from Gemini in two ways. First it runs the script, so you don't have to, but secondly if it reaches the token limit for script execution then it gives you the python script to run locally.
What is especially nice is that you can still keep "chatting" even if you reach that limit. It just won't run scripts internally.
Backup: Emphasized
Along the way The Cat constantly encourages you to make sure you have a backup before running a command. As I was working from a copy, rather than the primary library I felt safe to experiment. Eventually I did execute the command to delete the duplicates and ran jdupe one last time to ensure the duplicates were gone.
And Finally
While experimenting I hit the limitations of the free plan, first for code execution, and then for chat. I didn't intend for it to run scripts on files I uploaded. I think running scripts locally makes more sense. I uploaded the data for The Cat to get a better understanding of the data.
Hitting the data limit is a feature. It encourages us to take a break and work on something else.
What surprised me, yesterday, but again today, is that I get fatigued from playing with AI, because although large language models do some of the thinking, you still need to babysit them, and understand and supervise what they're doing.
#AI #cat #jdupe #machineLearning #mistral #photoprism
@pixeldorf
Schön, dass Du's wieder am Laufen hast... ja, NC kann schon a bissl rumzicken.
Vor allem vor nem Update gibts immer nen Snapshot. 😜
Hab hier gelesen, dass ihr alle #Immich nutzt... sehr cool!
Da trau ich mich als #Photoprism User ja garnix mehr sagen. 😆
@sindum I started my #Photoprism server in the #Proxmox Homelab Project last week. After some experiments with the configuration in the first round, I indexed about 200,000 images. Currently more than 200,000 images are running. Many of them are RAW files. Grouping by location, faces, and calendar works just fine. The web app runs pleasantly stable on Linux, Windows, Andoid and iOS. The files and thumbnails are stored on a NAS; the database runs on an internal SSD. #DiDay
Mẹo nhỏ: Dùng Nextcloud làm cầu nối để đồng bộ ảnh từ điện thoại vào PhotoPrism hoàn toàn miễn phí, không cần mua app trả phí. Cài đặt: Dùng app Nextcloud để tự động tải ảnh lên, sau đó mount thư mục ảnh vào PhotoPrism qua Docker. Ảnh sẽ tự động được đồng bộ và index. Mình cũng dùng Nextcloud để đồng bộ Joplin (WebDAV) và Floccus (WebDAV). #Nextcloud #PhotoPrism #SelfHosting #Docker #Sync #NextcloudSync #Joplin #WebDAV #Tự_động_hóa #Dữ_liệu_riêng #Lưu_trữ_tự_chủ
Dùng Nextcloud làm cầu nối để đồng bộ ảnh từ điện thoại vào PhotoPrism hoàn toàn miễn phí, không cần app trả phí. Dùng app Nextcloud để tự động tải ảnh lên, sau đó mount thư mục ảnh vào PhotoPrism để tự động index. Nextcloud cũng có thể dùng để đồng bộ Joplin, bookmark (Floccus) qua WebDAV. Cấu hình Docker kèm hướng dẫn đầy đủ.
#Nextcloud #PhotoPrism #SelfHosting #Sync #Mobile #Joplin #WebDAV #NextcloudVietnamese #TựLưuTrữ #ĐồngBộẢnh
Built two NAS-es on older hardware laying around. Used TrueNAS for the first time. One NAS is syncing its data to the other one. The Asus router is just used as a switch. The services (Photoprism and Jellyfin for now) on the main NAS are exposed via a Pangolin instance using a cool (undisclosed) new domain name. Am bidding now on a small server rack, which I hope to acquire in two days. Then it will all be shipped to my sister as a mini-datacenter. Then she can migrate her data from an old USB drive to the main NAS and will she have one sexy setup.
Had fun and learned a few things. Jellyfin is nice and I might consider migrating from Kodi to Jellyfin for my own setup.
Finally got my iCloud subscription cancelled thanks to #GrapheneOS, #Syncthing, and #Photoprism. My photo library is now stored 100% locally and is properly backed up. Entering 2026 with paying zero to Apple or Google.
Poddaję się.
Dawarich + PhotoPrism/Immich mnie przerosło.
Za Chiny Ludowe nie chcą mi się wyświetlać zdjęcia.
Nu har jeg lavet lidt tests og umiddelbart vinder #immich på ansigts genkendelse og på brugerinterface. Plus det er ret sejt at det har support for flere konti. Men jeg mangler en metode at synkronisere billeder fra en PC. #Photoprism har WebDAV, hvilket er ret smart, men også lidt manuelt. Men man kunne godt lave et workflow hvor man altid importerer billeder fra sit kamera i "import" mappen. Så sørger den automatisk for at placere dem korrekt. Alternativt må jeg have #nextcloud i gang også...
PhotoPrism, l'app open per la gestione di foto con AI, si aggiorna e porta la modifica in blocco per metadata e label, integrazione diretta con i modelli AI Ollama e OpenAI per generare didascalie, e miglioramenti nella gestione del riconoscimento facciale #PhotoPrism #Linux #Docker #SelfHosted
People with self-hosted photo storage: I'm considering moving from #Photoprism to #Immich. Any experiences with that (or with either of these)?
For context: I know that you can run both in parallel, but that feels like more bother than it’s worth, and getting trivial non-hacky upload in itself is enough reason to move (and that's without mentioning that Immich just seems on a much better trajectory as a project).
Addendum: experiences with using internal vs external libraries with Immich?
Chào mọi người! Mình cho một script giúp bạn bè không chuyên chạy Nextcloud + Jellyfin + PhotoPrism hoàn chỉnh một lệnh Ubuntu. Được Docker + Tailscale Serve bảo mật các URL (/cloud, /media, /photos). Hỗ trợ 8GB RAM. Bạn cần thêm gì? Hзд Pessoa script nhé!
#Selfhosting #Nextcloud #Jellyfin #PhotoPrism #Ubuntu #TailscaleServe #Docker #Automation
https://www.reddit.com/r/selfhosted/comments/1o6m6ie/building_an_automated_selfhosting_stack_for/
#photobackup #share
Nevím, asi jsem stará struktura
Nenadchnul mne #photoprism ani #immich prostě místo #googlephoto budu zálohovat z mobilu fotky na NAS pomocí jednoduché APP stylem ROK/MESIC/DEN/fotka.jpg a následně si je ručně (jak to dělám s fotkami ze zrcadlovky rovnat do #jAlbum
A je to ...
PS: tak po domluvě jsme dali šanci Immich, ač je opravdu náročný na HW.
Asi nejvíce, včetně APP připomíná Google Photo.
Necháme to zatím běžet jen lokálně doma, bez VPN, holt se zálohy provedou jen když budeme doma. I tak posílám příspěvek vývojářům a zkoumám nastavení, abych HW odlehčil, nový NAS jsem spočítal na 50k a to prostě nedám, takže příští rok nové disky - to se vejdu do 10k.
2 dni temu walczyłem z restartem dcokerowego środowiska #IMMICH na #RPI4B spowodowane generowaniem miniaturek, dziś społeczność dostarcza rozwiązanie. i działa.
bardzo mnie to cieszy, bo mimo iż #photoprism jest wciąż backendem dla zdjęć, to jednak immich ma przyjaźniejszy UI
edit: jakby ktoś był ciekawy problemu, to
-> temat restartów dockera https://github.com/immich-app/immich/issues/21189
-> https://github.com/immich-app/immich/issues/21237 <- probelm i rozwiazanie
I'm looking for self-hosted alternatives for my Google Photos backups. I have some old photos on an external drive and I'd like to make them searchable, ideally within an android app. But I'd like to keep them within my local network. I could either simply share a folder via samba, e.g. Solid Explorer handles the network folders quite well, but I'm sure there must be better solutions. Recently, I found #immich, which looks very promising. #photoprism seems interesting. Any other ideas?
#Blinko passe en version 1.2.0 (https://github.com/blinkospace/blinko/releases/tag/1.2.0), #OpenWebUI passe en version 0.6.17 (https://github.com/open-webui/open-webui/releases/tag/v0.6.17), et #PhotoPrism en version 250707-d28b3101e (https://github.com/photoprism/photoprism/releases/tag/250707-d28b3101e) 😎
PhotoPrism’s July 2025 release introduces Ollama AI support, enhanced search capabilities, and a new map-based location tool.
https://linuxiac.com/photoprism-ai-powered-photos-app-adds-map-based-location-editor/
🖼️ Private Fotos gehören nicht in die Hände von Google, Apple & Co. Wer Kontrolle über seine Bilder behalten will, sollte auf quelloffene und datenschutzfreundliche Alternativen setzen. Die Empfehlungsecke zeigt, wie sich Bilder datenschutzfreundlich verwalten lassen – ohne gläserne Nutzerprofile, zentralisierte Auswertung oder Abhängigkeit von Tech-Konzernen. 👇
Also managed to setup #photoprism in a Docker container to self host all of my photos and videos, finally #degoogle ing myself in that regard. That also feels good, but still working out the kinks with this workflow. Any tips appreciated.
I am running #PhotoPrism on a Raspberry Pi 5 with 8GB of RAM, using a 1TB SSD as the main and only drive, using the Pimoroni NVMe Base.
So far, I could not properly measure the performance, because I don’t know how to do it, but I am satisfied! Yet, this is definitely not a future-proof solution, since I need way more storage: I still haven’t imported most of my pictures there, and I need to prepare for plenty more to come.
The simplest (yet quite pricey, 261£) option would be to get a Pimoroni NVMe Duo and maximize it with a total of 4TB NVMe SSDs.
I think this is not optimal, though, and probably I could be spending all that money much better… Do you have any advice?
The thing about hosting a personal media gallery is that it requires a lot of resources when indexing the pictures (so only when you add new ones), then it’s super light—correct me if I am wrong, @photoprism. Hence, I’m thinking the best would be an extensible solution where I can add many HDDs and SSDs, without being forced to pump up the other specs too. I would probably be using just one NVMe SSD for the software and the database, and then save everything else in high-performance HDDs, since they are getting cheap and I can get much more storage with less money—of course I am performing a daily backup off-site, as they are more likely to fail, too.
If I am 100% sure that whatever I end up choosing will be solid for many years to come, I am willing to consider spending a bit more on it.
#homeLab #storage #Immich #mediaStorage #HDD #SSD #NVMe #RaspberryPi #RaspberryPi5 #server #homeServer #selfHosting #hosting #help #tips #advice #backup #photo #photoStorage #pictures #selfHost