🫧 socialcoding.. @smallcircles@social.coop
Public

@evanEvan Prodromou @julian

builds on top of in the sense that it adopted a number of its 'social primitives' defined in its vocabulary, and Collection being among those. These particular uses become 'protocol space', but other than that AS from the perspective of AP solution development is purely a set of social primitives, granular building blocks that one *may* use in a solution. AS is a utility library of sorts then. Or is that a wrong perception?

A 'feed' is something that lives in solution space, and I would only choose Collection to model it, if it offers a perfect fit in functionality. And aboveall.. does not assign some new app-specific use along the way.

I tooted today that I feel the biggest folly of the fedi is that everyone tries to cram their domain into the AS namespace. The AS primitives should not be Swiss army knives and have only singular well-defined meaning and purpose, yet they have become that along the way.

social.coop/@smallcircles/1160

infinite love β΄³ @trwnh@mastodon.social
Public

@smallcircles🫧 socialcoding.. @evanEvan Prodromou @julian if only the application domain of activitystreams was activities and streams... ;)

i do think it causes a lot of confusion to stray away from activities as content, instead using them as vehicles for state changes (which will never be consistent, not even eventually consistent).

back when atompub and atom+as1 were a thing, the "feed entry" was atom semantics and the "activity stream" was as1 semantics. they coexisted in the same xml file. it worked well enough.

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/trwnh/statuses/116099687660616557 on your instance and quote it. (Note that quoting is not supported in Mastodon.)