|
Top-level
Sebastian Lasse, redaktor.me
The “extensions” was not what we were talking about, that was Grishkas answer related to NodeInfo. An “extension” does not help here at all. 13 comments
Gregory replied to Gregory
@sl007 @humanetech So, for example, there's the Follow activity. Everyone knows what that does, right? Wrong. You can Follow people in a social media service. But you can't in a forum. There you could, for example, follow a topic or a subforum to get notified about new posts. It's two vastly different domains that use the exact same vocabulary in logically incompatible ways. 
smallcircles (Humane Tech Now) replied to Gregory
@grishka yes, it is the same problem as the semantic web had. I saw @sl007 mention DELETE. If you look at Rest it is also vaguely defined, everyone doing it differently. You might only support GET and POST, have different API designs. It is not ideal at all, but it has proven to be practical. In @activitypub et al there should be accepted ways and best-practices and standardization-as-much-as-possible. Closed vocabulary extensions. I am less worried about big players doing things differently.
Sebastian Lasse, redaktor.me replied to Gregory
Sorry, every ActivityPub actor can be followed. “interpret everything in the context of their domain.”
Gregory replied to Sebastian Lasse, redaktor.me
@sl007 @humanetech So how could we then have any diversity in the feature sets of the fediverse software?
Gregory replied to Gregory
@sl007 @humanetech my point being, following people in a forum is a rare and rarely used feature. Not all forum engines have it. PhpBB, one of the most popular ones, certainly doesn't.
Sebastian Lasse, redaktor.me replied to Gregory
My first and most simple idea: Better would either be simply concat (the multiple values problem) and bridging to supported types.
Gregory replied to Sebastian Lasse, redaktor.me
@sl007 @humanetech You keep saying that as if it's possible to have someone send you an activity your software doesn't support. The whole point of having capability negotiation is to solve this very problem before it has a chance to happen.
smallcircles (Humane Tech Now) replied to Gregory
I agree with @grishka Every activity has different interpretations depending on the domain it is used in. In a webshop you might have as:Offer literally meaning something that is for sale. But Offer is already being used in other contexts. In #forgefed an as:Note is a comment to a Ticket or Merge Request. etc.
Gregory replied to smallcircles (Humane Tech Now)
@humanetech @sl007 Yeah. I use Offer{Follow} as a friend request. But I only send it to actors that have supportsFriendRequests=true. I change my UI accordingly.
Sebastian Lasse, redaktor.me replied to Gregory
Citing the spec. again please note that MUST is written in capital letters for a purpose.
smallcircles (Humane Tech Now) replied to Sebastian Lasse, redaktor.me
But does it say what Followers / Following means? What if I have completely different custom actor types.. Tim Berners-Lee's Semantic Web failed because there was they idea to have universal semantics that applied globally. It is very important to have closed vocabularies, imho, where the terminology only have well-defined meaning in a specific domain. This matches the idea of domain-driven design (DDD) where you have bounded contexts.
Gregory replied to smallcircles (Humane Tech Now)
@humanetech @sl007 You would technically follow the spec if you have these collections, return them as always empty, and send Reject{Follow} for any Follow you receive. |
Gregory's Server
@sl007 @humanetech Problem is, the AP spec is deliberately very vague and domain-unspecific. But its real-world implementations are concrete and interpret everything in the context of their domain.
Core properties can be, and often are, also interpreted differently depending on the domain. So in that sense they aren't very much different from extensions many projects declare in their own namespaces, except that they have somewhat similar meanings across implementations.