activitypub activities lack required to/cc/id fields #77
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#77
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
subject covers it.
in the case of new posts being created, the objects have the to/cc fields instead of the activities themselves. this causes pure activitypub message routers like pleroma to discard the activity as invalid, since the activity lacks the to/cc fields.
also, in all cases, an activity must have an id. for example, the accept responses plume sends lack an id field.
other than this, Pleroma presently doesn't detect any major federation protocol violations, but i can't test any further until the to/cc are fixed, I suppose.
Does Pleroma support the
Articletype? (and thanks for the reports btw)my testing instance does have awareness of
Articleitems, but it's not enabled in mainline quite yet because nobody was using it. we treat them the same as notes, since pleroma will autocollapse any data larger than 1KB.All activities should have these fields now. And the demo instance has been updated if you want to check.