@reiver@mastodon.social that's a good summary for it.
@reiver@reiver โผ (Charles)
it is a good question. It is also a question that is formulated from the perspective on how we currently see the AS/AP fediverse.
> I've seen an ongoing debate between "Note" versus "Article" in #ActivityPub / #ActivityStreams.
> When is something a "Note"โฝ
> When is something an "Article"โฝ
The question makes sense from the notion of what the current #fediverse is. It makes less sense from the context of AS/AP as described in the protocol specs.
Background to my post is this observation: https://social.coop/@smallcircles/116109447243110037
Then the answer to when is something a Note or an Article is: Always. Note is Note in ActivityStreams and Article is Article.
The question that you would be asking, if only we had a fediverse that followed the original promise of the open standards, is:
> "When is something a Note or an Article in a Microblogging domain?"
For instance.. types you have in any domain depend on your model preferences. Could be anything that serves needs of a solution.
If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116110545919004233 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
To chain things together a bit on this fleety medium of ours, create a hyperweb ๐ I'll quote this toot to follow-up to
https://social.coop/@smallcircles/116110545919004233
I remember about 2018 or so, when I joined my first #SocialCG meetup. It was when the CG was still strongly tied to #SocialHub community.
There were mundane items on the agenda, interesting to any #ActivityPub dev, and also the call to action was "whether you are technical or not at all, join the meetup, we are open and inclusive to all fedizens". Very friendly, good vibes.
However during the session the talk was not only CS expert level, but dealing with subject matter nowhere near the spec. It was 'wire reality' slang, and to learn it the guidance was either nowhere, or everywhere, dispersed. And this is still as it is today. To expertised AP developers their domain language sounds all natural, but it likely seems Martian to a dev newcomer.
Stark contrast to the W3C specs that leave folks with refreshing "Let's implement this" vibe.