[bug] Mobilizon Federated Events cause error when using PropertyValue in an Attachment as part of the Event payload #465
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#465
Loading…
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?
Your setup
OTP
Extra details
No response
Version
3.6.0
PostgreSQL version
15.2
What were you trying to do?
When a Mobilizon group federates an Event to Akkoma, if the request contains an attachment with PropertyValue data in it, it throws an error and Akkoma cannot process it correctly.
I have an anonymized payload so you can look at what I mean in terms of data.
As for how to reproduce it, you can do it from a Mobilizon instance.
Steps:
Reference: https://docs.joinmobilizon.org/use/users/follow-federation/
Note: In Mobilizon, you don't follow a user account. User accounts can create and manage Groups and Events. From Akkoma you follow the group account which then pushes new Events and Event updates to the group's followers to Akkoma.
Create a new event in the group making sure that at a minimum the following fields filled in:
Title
Avatar (not sure if needed, but listing anyways)
It can be an online event (toggle)
Description
Website / URL
Under Event Metadata, try adding a Twitch user url
- Click the text box for "Find or add an element"
- Start typing in "twitch"
- Fill in a full twitch url (can be a fake user) like https://twitch.tv/test
Click Create Event
Watch Akkoma error on trying to process the federated event. It is unable to process the event.
I have a sample payload (anomymized) attached. It is not the exact payload that generated the pasted log errors, but it was created using the same steps and same important pieces.
What did you expect to happen?
I expect the event to be processed and pushed to the Akkoma user's timeline without issue.
What actually happened?
Akkoma errors out with errors.
Logs
Severity
I cannot use it as easily as I'd like
Have you searched for this issue?
Here is the source in the Mobilizon code that explains all of the "types" of PropertyValues that it will use in the attachment fields.
https://framagit.org/framasoft/mobilizon/-/blob/main/js/src/services/EventMetadata.ts
Ex from attached sample above:
This comes from this part in the Mobilizon code:
The full list of possible types might make it a little easier to know how to interpret Mobilizon's event data and different types.