@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.