You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Entries should be formatted and sorted/paginated using the naive time, as that ostensibly reflects the author's time of day when the post was authored.
Current Behavior
Entries are having their dates formatted/sorted/paginated based on the Publ app's configured timezone instead.
Context
Dates are hard. But this appears to be a regression.
Using the local time was a conscious decision because it's the least-bad approach; if an author changes primary time zones, that should not affect the pagination or display of entries in retrospect, and if an author is visiting another country and writing an entry about being up at 3 AM, the entry had better show the authoring time as being 3 AM!
The text was updated successfully, but these errors were encountered:
Okay it wasn't a regression so much as an artifact of how dates work in Postgres rather than SQLite - in Postgres they are stored as timezone-aware and retrieved with a specific timezone specified, which is not what we want. Whereas SQLite just stores them as strings.
Since display_date is never used for queries and is only used for display, we now just save it as the isoformat string and let arrow re-parse it into the correct native time.
Expected Behavior
Entries should be formatted and sorted/paginated using the naive time, as that ostensibly reflects the author's time of day when the post was authored.
Current Behavior
Entries are having their dates formatted/sorted/paginated based on the Publ app's configured timezone instead.
Context
Dates are hard. But this appears to be a regression.
Using the local time was a conscious decision because it's the least-bad approach; if an author changes primary time zones, that should not affect the pagination or display of entries in retrospect, and if an author is visiting another country and writing an entry about being up at 3 AM, the entry had better show the authoring time as being 3 AM!
The text was updated successfully, but these errors were encountered: