Fix federation payload for activities without proper metadata #48

Merged

McPringle merged 6 commits from fix/remote-activity-unknown into main

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

McPringle commented

2026-05-04 18:12:57 +02:00

(Migrated from github.com)

This PR fixes how activities are federated to remote instances.

Previously, federated activities could appear as an unknown activity with no proper name, while activity metadata ended up in the content body instead of being attached as structured activity data. As a result, remote instances were missing important activity information such as metadata and route preview.

This change ensures that activities are federated with the expected structure so remote instances can recognize them correctly and render them with their associated metadata.

What changed

fixed the federation payload for activities
ensured the activity name is federated correctly
moved activity metadata out of the plain content body into the proper activity fields
ensured activity-specific metadata is attached to the activity itself
restored support for route/track preview on remote instances

Result

Federated activities are now recognized correctly by remote servers, show a proper name instead of an unknown activity, keep their metadata in the right place, and expose route preview data as expected.

Testing

verified federated activities are no longer shown as unknown activities
verified activity names are present on remote instances
verified metadata is attached to the activity instead of embedded only in content
verified route preview is available again on remote instances

Important

When this PR is merged, #42 is obsolete. If #42 was merged before, this PR can be merged on top smoothly.

This PR fixes how activities are federated to remote instances. Previously, federated activities could appear as an unknown activity with no proper name, while activity metadata ended up in the content body instead of being attached as structured activity data. As a result, remote instances were missing important activity information such as metadata and route preview. This change ensures that activities are federated with the expected structure so remote instances can recognize them correctly and render them with their associated metadata. **What changed** - fixed the federation payload for activities - ensured the activity name is federated correctly - moved activity metadata out of the plain content body into the proper activity fields - ensured activity-specific metadata is attached to the activity itself - restored support for route/track preview on remote instances **Result** Federated activities are now recognized correctly by remote servers, show a proper name instead of an unknown activity, keep their metadata in the right place, and expose route preview data as expected. **Testing** - verified federated activities are no longer shown as unknown activities - verified activity names are present on remote instances - verified metadata is attached to the activity instead of embedded only in content - verified route preview is available again on remote instances **Important** When this PR is merged, #42 is obsolete. If #42 was merged before, this PR can be merged on top smoothly.