[bug] Custom emoji objects aren't valid JSON-LD #848

New issue

Open

opened 2024-11-01 18:27:08 +00:00 by zotan · 2 comments

zotan commented

2024-11-01 18:27:08 +00:00

What were you trying to do?

with #815 being merged, payloads containing custom emoji objects are no longer JSON-LD compliant. See #815 (comment) for details.

What did you expect to happen?

Payloads can be passed through JSON-LD expansion

What actually happened?

An error is thrown due to an invalid @id object

Severity

I cannot use the software

### What were you trying to do? with #815 being merged, payloads containing custom emoji objects are no longer JSON-LD compliant. See https://akkoma.dev/AkkomaGang/akkoma/pulls/815#issuecomment-13167 for details. ### What did you expect to happen? Payloads can be passed through JSON-LD expansion ### What actually happened? An error is thrown due to an invalid `@id` object ### Severity I cannot use the software

👀 1

zotan added the

bug

label 2024-11-01 18:27:08 +00:00

zotan commented

2024-11-01 20:24:52 +00:00

Author

Since this is a spec conflict and likely a mistake in the AP specification, I've opened an issue with the W3C: https://github.com/w3c/activitypub/issues/476

zotan commented

2024-11-02 15:23:20 +00:00

Author

From the discussion in the GH thread, the best way to solve this issue on the akkoma side would be to send out Emoji objects without an id property, instead of setting them to null.

From the discussion in the GH thread, the best way to solve this issue on the akkoma side would be to send out `Emoji` objects without an `id` property, instead of setting them to null.