Slideshow: Google Photos albums as a source (low priority, possible future plugin)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- google-cloud, python
Línea de trabajo
Start by building the local-folder slideshow, which this issue says is a prerequisite. Then run a quick test script from the Pi over SSH to try desktop-app sign-in, pick a few photos, and download them; decide who owns the Google Cloud project before building the integration. Done means picked photos can be imported to local storage and shown in the slideshow, with the sign-in and project ownership approach settled.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Low priority. Possible plugin for the future. Not part of any milestone.
Idea: a slideshow source that shows photos from a user's private Google Photos albums. Looked into on 2026-10-24; Google's rules make it hard, so it is parked.
What Google allows now
- Since 31 March 2025 the Library API scopes that let an app read a user's library and albums (
photoslibrary.readonly,photoslibrary.sharing,photoslibrary) are removed. Apps can only read photos they uploaded themselves. - The only way left is the Photos Picker API (scope
photospicker.mediaitems.readonly): the app opens a Google Photos page, the user ticks photos (or all photos in an album), and the app gets that list. - The app gets the picked list, not a link to the album. Photos added to the album later do not appear; the user must pick again.
- Access is short: each picking session has an end time (
expireTime), each download link (baseUrl) works 60 minutes, max 2000 photos per session. - => PaperPi would have to download the picked photos to the Pi right away and show them from local storage. Google Photos would be an "import into the local slideshow folder" step in the web interface, not a live source.
Sign-in problems on a Pi with no browser
- The TV-style "type a code on another device" sign-in does not allow any Photos scope.
- A normal web sign-in needs an
httpsorlocalhostreturn address; the PaperPi web interface (http://<IP>:8080) is not accepted. - Left over: "desktop app" sign-in with a
http://127.0.0.1/...return address that fails on the user's phone; the user copies that address into the PaperPi web page (the way rclone does it). Works, but clumsy. Not tested yet. - Who owns the Google Cloud project:
- each user makes their own (~15 steps; in "testing" mode the sign-in stops after 7 days), or
- one shared PaperPi project (easiest for users, but needs Google's app review: privacy policy, weeks of waiting, long-term upkeep).
If picked up later
- Build the local-folder slideshow first (needed anyway).
- Quick test script: desktop-app sign-in from the Pi over SSH, pick a few photos, download them.
- Decide who owns the Cloud project.
Sources: Photos API updates · Picker: get started · Picker: media items · Picker: sessions · Configure your app · TV / limited-input sign-in
🤖 Generated with Claude Code
- Lenguaje dominante
- Python
- Estrellas
- 205
- Forks
- 17
- Merge medio
- 3 h 55 min
- PR fusionados (30 d)
- 77
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de txoof/PaperPi
-
Plugins whose default refresh equals the display time (word_clock, system_info, nl_openbaar_vervoer)Posiblemente ocupada @txoof-bot la tomó hace 1 día. Abiertoarea:plugins in-progress
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
txoof/PaperPi#335 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
area:web enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 56/100
Los mantenedores suelen responder en 1 día
-
area:core area:web enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 45/100
Los mantenedores suelen responder en 1 día
Todos los issues de txoof/PaperPi
Issues similares
-
bug P1
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Toloka/tolokaforge#1947 ·
Los mantenedores suelen responder en 1 día
-
SageMaker provider: streaming fails with NoStreamDataError on DJL Serving (LMI) endpointsPosiblemente ocupada @balajiaru la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
UKGovernmentBEIS/inspect_ai#6127 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
pydot/pydot#601 · 4 comentarios ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
letsencrypt/cp-cps#361 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100