Photos shared root returns an empty timeline after opt-in #215

New issue

Closed

opened 2026-09-27 05:36:46 +00:00 by kayg · 3 comments

kayg commented

2026-09-27 05:36:46 +00:00

Owner

A real local adversarial run found that an active shared Photos root can return an empty timeline after the recipient opts in.

Reproduction from tests/adversarial/attack2.py:

User A has a photo in Photos/2024/2024-06-02/ and the owner timeline shows it.
User A shares Photos with User B.
User B adds Shared/<owner-id>/Photos with PUT /api/v1/photos/library-roots (HTTP 200).
Poll GET /api/v1/photos/timeline?before=2024-06-03&days=7&tiles_per_day=10 for 12 seconds.

Observed: every timeline response was HTTP 200 with {"days":[],"next_before":null}. The probe did not mark this finding SLOW. The same host round noted that no thumbnail appeared within 10 seconds and skipped a thumbnail-dependent check, so confirm whether media worker load affected the fixture.

Expected: the recipient sees the shared photo in the timeline after opting in. Revoking the Share must remove it from later reads.

The route updates the setting and starts index::refresh_user in the background. Please check whether the viewer's Photos index is refreshed from the active shared root and whether failures are visible to the caller or logs.

A real local adversarial run found that an active shared Photos root can return an empty timeline after the recipient opts in. Reproduction from `tests/adversarial/attack2.py`: 1. User A has a photo in `Photos/2024/2024-06-02/` and the owner timeline shows it. 2. User A shares `Photos` with User B. 3. User B adds `Shared/<owner-id>/Photos` with `PUT /api/v1/photos/library-roots` (HTTP 200). 4. Poll `GET /api/v1/photos/timeline?before=2024-06-03&days=7&tiles_per_day=10` for 12 seconds. Observed: every timeline response was HTTP 200 with `{"days":[],"next_before":null}`. The probe did not mark this finding SLOW. The same host round noted that no thumbnail appeared within 10 seconds and skipped a thumbnail-dependent check, so confirm whether media worker load affected the fixture. Expected: the recipient sees the shared photo in the timeline after opting in. Revoking the Share must remove it from later reads. The route updates the setting and starts `index::refresh_user` in the background. Please check whether the viewer's Photos index is refreshed from the active shared root and whether failures are visible to the caller or logs.

kayg referenced this issue

2026-09-27 06:13:26 +00:00

Appearance: one Theme card with per-mode theme dropdowns and backgrounds; shared borderless segmented pill everywhere #183

kayg commented

2026-09-27 07:04:33 +00:00

Author

Owner

Post-merge adversarial update from 2026-09-27: the media upload probe again reported thumbnail: none generated in 10 s (media worker busy or missing); header check skipped. This round did not report a shared-root timeline assertion failure, so it does not confirm or clear the original timeline result. The output does not separate worker failure from shared-host load. Hostile-byte checks reported zero findings.

Post-merge adversarial update from 2026-09-27: the media upload probe again reported `thumbnail: none generated in 10 s (media worker busy or missing); header check skipped`. This round did not report a shared-root timeline assertion failure, so it does not confirm or clear the original timeline result. The output does not separate worker failure from shared-host load. Hostile-byte checks reported zero findings.

kayg referenced this issue

2026-09-27 07:11:55 +00:00

Appearance: one Theme card with per-mode theme dropdowns and backgrounds; shared borderless segmented pill everywhere #183

kayg commented

2026-09-27 10:07:31 +00:00

Author

Owner

Follow-up from the #148 adversarial round after merge 61cdb607: the real local server again returned HTTP 200 with days: [] for every recipient Photos timeline poll during the 12-second active-share/opt-in window. This is not a SLOW finding. Several other adversarial runs were active on the shared host, so this still needs a quiet-host reproduction; the empty-timeline result itself repeated.

Follow-up from the #148 adversarial round after merge `61cdb607`: the real local server again returned HTTP 200 with `days: []` for every recipient Photos timeline poll during the 12-second active-share/opt-in window. This is not a SLOW finding. Several other adversarial runs were active on the shared host, so this still needs a quiet-host reproduction; the empty-timeline result itself repeated.

kayg referenced this issue

2026-09-27 10:07:33 +00:00

Files: HTTP 500 'files Index update failed' under heavy load (adversarial, load 50-72) #148

kayg referenced this issue

2026-09-28 18:46:44 +00:00

Shared Photos timeline stays empty after member opt-in #188

kayg referenced this issue

2026-09-28 18:46:58 +00:00

Shared Photos timeline stays empty after member opt-in #188

kayg commented

2026-09-28 23:46:34 +00:00

Author