@philip @activitypubtestsuite how would you define “supported”?
3 comments
@blake @philip @activitypubtestsuite so you’d have a 3-valued range of support: yes, no, and falling back. @J12t @activitypubtestsuite At the protocol level, I guess I’m thinking: If I send a message of type X, do I get a response that suggests the server accepted it, or not. |
@J12t@social.coop @philip@mastodon.mallegolhansen.com @activitypubtestsuite@venera.social I think I'd do it in first class, second class, and no support. First class is, well, first class treatment, like a Note is in Mastodon or an Article for WordPress or WriteFreely. Second class is probably going to be when it's converted into a first class type, like Articles are in Mastodon (afaik) or how Firefish/Akkoma reactions fall back to generic favorites in Mastodon, or when it uses a fallback representation (was it
content
orsummary
that's on every object?). No support could be defined as any case where the above doesn't apply, and it crashes (god forbid) or drops/ignores the activity or object entirely.@J12t@social.coop @philip@mastodon.mallegolhansen.com @activitypubtestsuite@venera.social I think I'd do it in first class, second class, and no support. First class is, well, first class treatment, like a Note is in Mastodon or an Article for WordPress or WriteFreely. Second class is probably going to be when it's converted into a first class type, like Articles are in Mastodon (afaik) or how Firefish/Akkoma reactions fall back to generic favorites in Mastodon, or when it uses a fallback representation (was it