there's a page on this in the primer:

w3.org/wiki/Activity_Streams/P…

But it's not always clear.

One thing that might distinguish is presentation.

I expect an Article to appear on its own page. References to an Article in a stream or tree layout might just include title and summary, with a link to a UI to show the full text.

But lots of Note objects can fit in a stream or tree presentation.

@thisismissem

@reiver 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: social.coop/@smallcircles/1161…

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.

🫧 socialcoding..

2026-02-21 15:59:23

#ThoughtProvoker

The current fediverse is an evolutionary dead-end for 2 reasons:

1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay.

2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out.

Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep #ActivityPub experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with.

To avoid fedi to become less and less attractive to newcomers, we must now consider:

“Why do we want to grow the open social web, and for whom?” -- @ben

coding.social/blog/shared-owne…

Shared responsible social web ownership

We strive for an inclusive social web that is by the people and for the people. But how do we guarantee equity and shared ownership?

^{Social coding commons}

Btw, I am sorry as I should've added "tangential" to the above, but was out of chars. I borrowed your post to continue my argument made elsewhere.

Adding an analogy that popped up as a showerthought just now, to clarify further what I refer to..

In a different context someone who creates a Webshop webapp might ask:

> When is something a "Product" or "Invoice" in HTTP / HTML?

It is not fully equivalent, but demonstrative of how the concepts clash, mixing solution space with protocol vocabulary in language use.

Yet this is what happens continuously in all fediverse developer talk, sowing endless confusion, but also leads to complete different, incompatible views and expectations on what fediverse is, and where it is headed.

We have a laissez-faire fediverse. Handy, as you can just hack things in. But also directionless and random.

@thisismissem