Closed MidnightLightning closed 2 weeks ago
This issue seems to be similar to #2600 , but the file referenced in this comment is no longer at that location, so I cannot submit a patch for it.
Lemmy doesnt support json-ld, it only uses plain json. The context is now defined in this file so please make a pull request.
Edit: expires
is already changed to end_time in the main branch, but it will be a few months before that change gets released.
Requirements
Summary
The JSON-LD context file hosted at https://join-lemmy.org/context.json defines several custom fields, including
sensitive
andexpires
. That context file seems to be trying to add those properties to the ActivityStream vocabulary via the prefixas:
. That prefix is commonly used for ActivityStream, but because the context file doesn't actually define the prefix, it's not doing what is expected.Steps to Reproduce
Take this sample JSON-LD document which is similar to the Actor fragments Lemmy presents via the ActivityPub API endpoints:
put it into the JSON-LD Playground and pick "Expanded". Note that fields like
attributedTo
get expanded tohttps://www.w3.org/ns/activitystreams#attributedTo
(correct), butsensitive
gets expanded toas:sensitive
(incorrect).This incorrect mapping leads to other issues if the receiving application wishes to do other JSON-LD transformations to the object (e.g. Compact it with different aliases).
Technical Details
The contents of https://join-lemmy.org/context.json is currently:
They need to be updated to be:
(one additional alias line added after "litepub")
Version
N/A
Lemmy Instance URL
https://join-lemmy.org/context.json