arcanicanis on Nostr: It’s probably not even so much the standard itself, but more to do with all the ...
It’s probably not even so much the standard itself, but more to do with all the aimless and shallow-efforted implementations, especially when people are writing libraries dealing with cryptography that can’t even get the basics right, and everyone just blindly pulls it in without question.
Although, yes, sometimes weird stuff pops up, just as last night when I was adding support for polls, that I notice the Question type is apparently classified as an activity, not really a persistent content type, but treated like a post (as it maybe should be?). Generally I’ve had the mental model that non-activity types are usually a side-effect of an activity, or describe a momentary relationship between non-activity types (Person arrived at Event, Person created a Note, Person updated a Note, Person followed a Person, etc).
Nonetheless, ActivityStreams was ambiguously vague until a more opinionated and narrowed use of it was conceived—ActivityPub. I don’t see what value ActivityStreams had before ActivityPub, other than practically just being a schema for describing social activity data.
Meanwhile, JSON-LD continues to bring more surprises, as I believe there were some unforeseen surprises and confusion in JSON-LD regarding canonicalization of @context that’s delayed standardization of some of the Data Integrity cryptosuites (not really currently an AP thing, but just more W3C disarray).
Although, yes, sometimes weird stuff pops up, just as last night when I was adding support for polls, that I notice the Question type is apparently classified as an activity, not really a persistent content type, but treated like a post (as it maybe should be?). Generally I’ve had the mental model that non-activity types are usually a side-effect of an activity, or describe a momentary relationship between non-activity types (Person arrived at Event, Person created a Note, Person updated a Note, Person followed a Person, etc).
Nonetheless, ActivityStreams was ambiguously vague until a more opinionated and narrowed use of it was conceived—ActivityPub. I don’t see what value ActivityStreams had before ActivityPub, other than practically just being a schema for describing social activity data.
Meanwhile, JSON-LD continues to bring more surprises, as I believe there were some unforeseen surprises and confusion in JSON-LD regarding canonicalization of @context that’s delayed standardization of some of the Data Integrity cryptosuites (not really currently an AP thing, but just more W3C disarray).