Re: SWICG CG Charter

Oh sorry, missed the subject line.  Comments inline:

I would like us to pave the way for the standards to go far far beyond the
>>> microblogging Twitter level of Social Media and for The Charter to reflect,
>>> allow, and prepare the way for this.
>>>
>>> To do this I think we need to bring a server "capabilities" model into
>>> ActivityPub/ActivityStreams where webfinger can get both supported
>>> ActivityStreams extensions, and also a set of supported media types, this
>>> can default to the existing ActivityStreams 2 context, and be an array of
>>> supported contexts and terms.
>>>
>> I don't think a CG can make changes this structural to the protocol? Or
at least, this extended usage of Webfinger could be written up as an
extension (start with FEP, go through the stages) as CG work items, and the
protocol changing to _assume_ this capability discovery would be a vNext of
the core protocol, which definitely has to be a WG thing.


> There is a tension between the usage of just JSON based packets and
>>> JSON-LD based, this reflects levels of complexity for implementers and in
>>> implementations and needs to be resolved by the CG and WG and not swept
>>> under the carpet and for us to shy away from this or hide intentions for
>>> the sake of one camp or another.
>>>
>> Agreed! IMHO the "polyglot" nature of the protocol's _implementation_ and
interop responsibilities is more like a social contract ever in need of
renewing that a simple technical fact that can be definitively resolved or
decided, even if the fact of the wire format itself being is JSON-LD is cut
and dry!

> Server management on a technical, social, and political level is not part
>>> of the standard(s) and really needs examining properly, the existing
>>> implementations and solutions. How well can this be documented, formalized,
>>> and standardized will be an interesting problem, but I think we need to
>>> bring this whole area into the fold and reflect this in the charter.
>>>
>> Can you make a concrete PR that would add them into the charter? We
already have task forces like Trust and Safety working on this stuff, so I
never really considered them _out_ of scope, but it couldn't hurt to be
explicit if I'm overinterpreting what's in there textually.


> This may all be opening a can of worms, and hope this is not ignored, but
>>> I really think we need a wider remit and scope, and this will be necessary
>>> in order for the standards and future standard to keep up with and in fact
>>> lead the field. paving the way for creating and nurturing Social Media,
>>> Networking, and Collaboration Systems, which will emergently become a
>>> continuum.
>>>
>> Here too I'm not sure this charter's scope excludes that?


> From looking at the charter most of what I am presenting here would end up
>>> in the Out of Scope section.
>>>
>>> The reasoning behind me bringing all this up, is having seen a wider
>>> view and longer term context to both the web and social media's
>>> development. We are still stuck in an infancy of 20 years of FaceBook's
>>> user interface, and 18 years of Twitter/X'es user interface and
>>> functionality not really changing to any degree, and in fact with the case
>>> of FaceBook's even being retrograde.
>>>
>> I see this as a layering problem. The past work items and deliverables
have been very low-level, and the user interface and economics/separation
of concerns/architecture of platforms and products is way above what W3C
works on. It might be best to keep this work in the FEP-zone/community
until 2 or more implementations want to negotiate interoperability at a
low-enough level to justify "going normative", as the Forum/Threads folks
are doing (as we speak, in fact) with their Task Force.


> Kind regards,
>>>
>>> Aaron
>>>
>>> --
>>> Aaron Gray - @AaronNGray@fosstodon.org | @aaronngray@threads.net
>>>
>>> Independent Open Source Software Engineer, Computer Language Researcher
>>> and Designer, Amateur Type Theorist, Amatuer Computer Scientist,
>>> Environmentalist and Climate Science Researcher and Disseminator.
>>>
>>>
>
> --
> Aaron Gray - @AaronNGray@fosstodon.org | @aaronngray@threads.net
>
> Independent Open Source Software Engineer, Computer Language Researcher
> and Designer, Amateur Type Theorist, Amatuer Computer Scientist,
> Environmentalist and Climate Science Researcher and Disseminator.
>
>