100% agreed.
I have contributed quite a bit to the PieFed codebase, but the ActivityPub parts of the code are the main area where I dare not wander unless absolutely needed. Trying to make sense of what AP json should look like for specific actions is basically impossible and each software tends to have slightly different dialects anyway because of the a la carte nature of the FEPs.
To that end, I just saw that you (mbin) just published what all of your AP json schema. It is so incredibly helpful to have complete schema in one place for each type of activity. So, thank you a lot! I am sure I will make use of it.
melroy@kbin.melroy.org 2 weeks ago
I fully agree. And you nailed it. This was exactly what I try to explain what is wrong with ActivityPub FEPs.
Thank you, we do indeed publish those schemas, these are coming from the code. So our documentation build is also relying on our code to expose these schemas, and that's also why I can guarantee it's always up to date.
melroy@kbin.melroy.org 2 weeks ago
For example we have ap issues with lemmy, lemmy doesn't support multiple attachments. We use attachments for both links (url, other than image links) as well as images themselves can be an attachment.
But again AP fails, and lemmy only shows the picture.