Incorrect timestamps when returning latest items #1

New Issue

Jef Roosens · 2025-03-04T20:20:49+01:00

Jef Roosens commented

2025-03-04 20:20:49 +01:00

The Gpodder API returns a timestamp value for certain routes indicating the value that should be used as the since parameter for the next request to the endpoint.

The current implementation always returns the timestamp of the latest element incremented by 1. This isn't correct if the latest returned element is in the past. The timestamp should reflect that no more elements are present between the last element's timestamp and the current UNIX timestamp.

To fix this, the API should instead return the current UNIX timestamp if it's returning the latest elements.

The Gpodder API returns a timestamp value for certain routes indicating the value that should be used as the `since` parameter for the next request to the endpoint. The current implementation always returns the timestamp of the latest element incremented by 1. This isn't correct if the latest returned element is in the past. The timestamp should reflect that no more elements are present between the last element's timestamp and the current UNIX timestamp. To fix this, the API should instead return the current UNIX timestamp if it's returning the latest elements.

Jef Roosens added the

bug

label 2025-03-04 20:20:49 +01:00

Jef Roosens self-assigned this 2025-03-04 20:20:50 +01:00

Jef Roosens removed their assignment 2026-02-22 19:58:39 +01:00

Sign in to join this conversation.