@devnull The state property is not necessary.
-
@devnull The
stateproperty is not necessary. I send regular Follow and Undo activities, that works.May I ask why this FEP is finalized? There haven’t been any implementors (except for Fedify, above?) who have submitted comments about this.
There were no objections. FEP process doesn't require implementations, a rough consensus is enough for finalization.
-
@devnull The
stateproperty is not necessary. I send regular Follow and Undo activities, that works.May I ask why this FEP is finalized? There haven’t been any implementors (except for Fedify, above?) who have submitted comments about this.
There were no objections. FEP process doesn't require implementations, a rough consensus is enough for finalization.
@silverpill @protocol @devnull if the state property isn't defined in any json-ld context won't that make validation fail if anyone bothers to do it? -
@silverpill @protocol @devnull if the state property isn't defined in any json-ld context won't that make validation fail if anyone bothers to do it?
@sun In the JSON-LD playground, a property that is not defined in @context results in a "blank node". I don't know how bad that is, but at least it doesn't throw an error.
-
@sun In the JSON-LD playground, a property that is not defined in @context results in a "blank node". I don't know how bad that is, but at least it doesn't throw an error.
@silverpill @protocol I read more about it and apparently it's never supposed to throw an error because it will just be assumed to be resolveable against the base vocabulary, so it some kind of problem but not a parsing one and can be ignored
