@nik it's not what *i'm* doing; this is what most of fedi does.
-
@nik it's not what *i'm* doing; this is what most of fedi does. AS2 has the dubious "advantage" of letting you "ignore the LD", but you can easily make mistakes in your ignorance.
i can be smart and do a proper RDF graph merge, but i was formulating a way for "plain JSON" people to effectively do a graph merge while being graph-unaware, through the equivalent JSON operations (without triggering errors due to redefining protected terms)
-
@nik it's not what *i'm* doing; this is what most of fedi does. AS2 has the dubious "advantage" of letting you "ignore the LD", but you can easily make mistakes in your ignorance.
i can be smart and do a proper RDF graph merge, but i was formulating a way for "plain JSON" people to effectively do a graph merge while being graph-unaware, through the equivalent JSON operations (without triggering errors due to redefining protected terms)
@trwnh I know. And my point is: If you can't handle RDF, stop developing for ActivityPub.
(Yes, the spec should clearly state that RDF is obligatory, and we should make better tools and libraries to support people who can't wrap their heada around RDF.)
-
@trwnh I know. And my point is: If you can't handle RDF, stop developing for ActivityPub.
(Yes, the spec should clearly state that RDF is obligatory, and we should make better tools and libraries to support people who can't wrap their heada around RDF.)
@nik it's not obligatory at all, though? taking a hardline RDF stance and asking anyone who disagrees to "stop developing for ActivityPub" is asking basically all of fedi to stop. they're not going to listen to this, and they're not going to oblige in the slightest.