> > In every case I've seen, and I'm sure I have not seen them all, there is > duplication between the data in the "Activity" part of a message and the > "Object" part of the same message. If this is universally the case, and > will remain so, it seems > I wanna make sure you understand that that's not like some accidental emergent behavior or, as someone else described it, due to 'careless design'. It is because it's a feature of the protocol that is optimizing for something other than minimizing amount of JSON. https://www.w3.org/TR/activitypub/#object-without-create On Thu, Mar 16, 2023 at 10:52 AM Darius Kazemi <darius.kazemi@gmail.com> wrote: > On Thu, Mar 16, 2023 at 10:49 AM Bob Wyman <bob@wyman.us> wrote: > >> Darius wrote, in his ActivityPub implementor's guide: >> >>> Eh. Don't read [ActivityStreams V2.0] now. Skim the table of contents. >>> There will be bits of ActivityPub that don't make sense without the >>> ActivityStreams 2.0 spec, but those will be more advanced questions you'll >>> have later. >> >> >> I don't think this is a very helpful attitude. After several decades of >> either implementing and/or specifying numerous protocols, many much more >> complex than ActivityPub, I would never suggest that anyone even think >> about beginning an implementation without first closely reading all the >> specifications. >> bob wyman >> > > I don't wish to derail this thread but the fact is that reading the specs > in a linear order will not be helpful for many, many people. I was not > advocating for not reading all the specs. I was advocating to skim one set, > go read another, and then come back to the original set when necessary > because you will have better context.- >
Received on Friday, 17 March 2023 03:13:37 UTC