⚠️ We’re now entering the “extinguish” part of “Embrace, extend, extinguish”.

[bengo@mastodon.social]

️ We’re now entering the “extinguish” part of “Embrace, extend, extinguish”. We’ve had the first proposals in @socialcg to remove requirements of #activitypub that have been in place for 7+ years, and without an explanation how the removal improves anything.
https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extinguish

React if you’d like a #ActivityPubSpecAlert when there are proposals to change the requirements of ActivityPub as we’ve begun to see the last couple weeks.

Join https://www.w3.org/community/socialcg/

[julian@community.nodebb.org]

bengo@mastodon.social what's the context for this?

[pfefferle@mastodon.social]

@julian @bengo ???

[trwnh@mastodon.social]

@pfefferle @julian @bengo @csarven @raucao @oblomov

i think the context is this github issue: https://github.com/w3c/activitypub/issues/320

was put to the swicg mailing list as a cfc by evan: https://lists.w3.org/Archives/Public/public-swicg/2025Jun/0038.html

bengo requested a clear "error description" and "candidate correction": https://lists.w3.org/Archives/Public/public-swicg/2025Jun/0039.html

to clarify, no requirements are being removed: https://lists.w3.org/Archives/Public/public-swicg/2025Jun/0043.html

i agree that cfc emails should include an "error description" and "candidate correction". perhaps https://github.com/w3c/activitypub/issues/320#issuecomment-2971191447 suffices?