hrefna, 6 months ago

So far in my evaluation no one, of any size service, handles all of this correctly.

I don't seem to be alone in this analysis, either: https://www.stevebate.net/nothin-implements-activitypub/

Serious question: are there any projects out there that:

1. implement all of this—including things like handling multiple actors or multiple inReplyTo links/objects/lists/etc
2. correctly
3. with tests

Ideally would be one that also does this without needing to parse it "in #JsonLD"

?

jenniferplusplus, 6 months ago

@hrefna not to my knowledge. I'm also working on it. Coauthorship is a big wishlist item for me.

joelving, 6 months ago

@hrefna
How do you understand it when the AS2-spec says a thing can be "Link or Object"? Object is an object (duh), but so is Link (with href properties and such). And then there's URIs. And often optional multiplicity (single value vs collection). Do we really have four (!) potential target types for deserialization?

hrefna, 6 months ago

@joelving It gets worse. There's an Object type Collection.

Which can contain a list of items, but it could also contain a CollectionPage. https://www.w3.org/TR/activitystreams-core/#collections

hrefna, 6 months ago

@joelving Basically, to represent one object, I think these are all valid:

{
type: Obj etc
}

2. [{ type: Obj etc}]

3. {href etc}

4. [{href etc}]

5. <uri>

6. [<uri>]

7. {Collection, items: [{type: Obj etc]}]}

8. {Collection, items: [{href etc}]}

9. {Collection, items: [<uri>]}

10. {Collection, CollectionPage, first: [{type: Obj etc}]

11. {OrderedCollection, items: [{type: Obj etc]}]}

etc etc etc, not getting into additional nesting that you could do as well.