Just heard in #ActivityPub related chat (because I typed it) ..
> Btw, the ad-hoc code-first show-dont-tell mentality is an interesting social dynamic in FOSS, but esp. in the AS/AP open standards based ecosystem, a chaotic grassroots #commons.
Discussion
Loading...
> And it is an understandable dynamic.. devs have invested much time to 'eat' their way through the complexity of building federated apps, and afterwards when they are unlocked, gained the expertise, they want to focus on their app. They are likely to even resist major changes to the spec, even if they'd be ultimately beneficial to them.
This pragmatic approach that often works very well for individual #FOSS projects, is detrimental to formation of healthy #commons.
https://socialhub.activitypub.rocks/t/layered-activitypub/5449/6?u=aschrijver
The link above points out that for AS/AP and #fediverse at large we need to know the domain model of the protocol and al start talking in the same ubiquitous language for good common understanding.
A similar need for a domain model also exists for the #Protosocial#ActivityPub protocol extension, and if that initiative lifts off is one of the first things to flesh out.
(Thanks also to @tijl for pointing out that need to which I 馃挴 agree)
https://discuss.coding.social/t/protosocial-activitypub-protocol/665
@smallcircles
> for AS/AP and #fediverse at large we need to know the domain model of the protocol
> for AS/AP and #fediverse at large we need to know the domain model of the protocol
I'm pretty sure if we can all agree on what a "domain model" is, we can all agree on what the "domain model" is for AP : P
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled