Fixes an ActivityPub timestamp issue in federation. #42

Closed

McPringle wants to merge 5 commits from fix/inbox-timestamp-exception into main

McPringle commented

2026-05-02 20:29:22 +02:00

(Migrated from github.com)

Federated activities could fail because the published timestamp was sent without timezone information. I added regression tests for that case, made the inbox more tolerant, and fixed the sender so new activities are emitted with a timezone-aware timestamp.

What changed

added a regression test for incoming remote activities with a published timestamp that has no timezone
made InboxProcessor accept that timestamp format as a fallback
added regression tests for outgoing ActivityPub serialization
fixed outgoing published timestamps so they are sent as UTC instants

Result

After this change:

incoming activities with that timestamp format no longer fail
newly sent activities include timezone information
the regression tests are green

Federated activities could fail because the `published` timestamp was sent without timezone information. I added regression tests for that case, made the inbox more tolerant, and fixed the sender so new activities are emitted with a timezone-aware timestamp. ## What changed - added a regression test for incoming remote activities with a `published` timestamp that has no timezone - made `InboxProcessor` accept that timestamp format as a fallback - added regression tests for outgoing ActivityPub serialization - fixed outgoing `published` timestamps so they are sent as UTC instants ## Result After this change: - incoming activities with that timestamp format no longer fail - newly sent activities include timezone information - the regression tests are green

javahippie commented

2026-05-05 10:39:24 +02:00

(Migrated from github.com)

Superseded by #48