#socialcg — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #socialcg, aggregated by home.social.
-
Anyone who is interested in the #Fediverse and #ActivityPub is welcome to join the Social Web Community Group #SocialCG at the #w3c.
It's the group that develops and advances the social standards that make this network go. It's open to anyone. If you have specific interests, we have task forces that work on specific topics. Or you can start one!
It's easy to join.
-
Anyone who is interested in the #Fediverse and #ActivityPub is welcome to join the Social Web Community Group #SocialCG at the #w3c.
It's the group that develops and advances the social standards that make this network go. It's open to anyone. If you have specific interests, we have task forces that work on specific topics. Or you can start one!
It's easy to join.
-
Anyone who is interested in the #Fediverse and #ActivityPub is welcome to join the Social Web Community Group #SocialCG at the #w3c.
It's the group that develops and advances the social standards that make this network go. It's open to anyone. If you have specific interests, we have task forces that work on specific topics. Or you can start one!
It's easy to join.
-
Anyone who is interested in the #Fediverse and #ActivityPub is welcome to join the Social Web Community Group #SocialCG at the #w3c.
It's the group that develops and advances the social standards that make this network go. It's open to anyone. If you have specific interests, we have task forces that work on specific topics. Or you can start one!
It's easy to join.
-
Anyone who is interested in the #Fediverse and #ActivityPub is welcome to join the Social Web Community Group #SocialCG at the #w3c.
It's the group that develops and advances the social standards that make this network go. It's open to anyone. If you have specific interests, we have task forces that work on specific topics. Or you can start one!
It's easy to join.
-
@hongminhee how can we get more East Asian #ActivityPub developers involved in the #W3C #SocialCG and #SocialWG?
-
@hongminhee how can we get more East Asian #ActivityPub developers involved in the #W3C #SocialCG and #SocialWG?
-
@hongminhee how can we get more East Asian #ActivityPub developers involved in the #W3C #SocialCG and #SocialWG?
-
@hongminhee how can we get more East Asian #ActivityPub developers involved in the #W3C #SocialCG and #SocialWG?
-
@hongminhee how can we get more East Asian #ActivityPub developers involved in the #W3C #SocialCG and #SocialWG?
-
I think I just figured out why the SocialCG prioritised work on encrypted private messaging for ActivityPub.
Decentralised DMs already give the fediverse an edge over the ATmosphere (eg BlueSky DMs are BS-only). If they're all E2EE as well, that puts us head and shoulders above anything the ATProtocol can currently handle.
(1/?)
-
I think I just figured out why the SocialCG prioritised work on encrypted private messaging for ActivityPub.
Decentralised DMs already give the fediverse an edge over the ATmosphere (eg BlueSky DMs are BS-only). If they're all E2EE as well, that puts us head and shoulders above anything the ATProtocol can currently handle.
(1/?)
-
I think I just figured out why the SocialCG prioritised work on encrypted private messaging for ActivityPub.
Decentralised DMs already give the fediverse an edge over the ATmosphere (eg BlueSky DMs are BS-only). If they're all E2EE as well, that puts us head and shoulders above anything the ATProtocol can currently handle.
(1/?)
-
I think I just figured out why the SocialCG prioritised work on encrypted private messaging for ActivityPub.
Decentralised DMs already give the fediverse an edge over the ATmosphere (eg BlueSky DMs are BS-only). If they're all E2EE as well, that puts us head and shoulders above anything the ATProtocol can currently handle.
(1/?)
-
The #Miscellany context for #ActivityPub, which documents a few widely-used terms, is now a Draft report of the #SocialCG:
https://swicg.github.io/miscellany/
/cc @socialcg
-
The #Miscellany context for #ActivityPub, which documents a few widely-used terms, is now a Draft report of the #SocialCG:
https://swicg.github.io/miscellany/
/cc @socialcg
-
The #Miscellany context for #ActivityPub, which documents a few widely-used terms, is now a Draft report of the #SocialCG:
https://swicg.github.io/miscellany/
/cc @socialcg
-
The #Miscellany context for #ActivityPub, which documents a few widely-used terms, is now a Draft report of the #SocialCG:
https://swicg.github.io/miscellany/
/cc @socialcg
-
The #Miscellany context for #ActivityPub, which documents a few widely-used terms, is now a Draft report of the #SocialCG:
https://swicg.github.io/miscellany/
/cc @socialcg
-
> Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly).
As it happned, while cleaning up a gazillion browser tabs I had open, I bumped into the SocialCG document that defines HashTag:
-
> Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly).
As it happned, while cleaning up a gazillion browser tabs I had open, I bumped into the SocialCG document that defines HashTag:
-
> Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly).
As it happned, while cleaning up a gazillion browser tabs I had open, I bumped into the SocialCG document that defines HashTag:
-
> Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly).
As it happned, while cleaning up a gazillion browser tabs I had open, I bumped into the SocialCG document that defines HashTag:
-
> Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly).
As it happned, while cleaning up a gazillion browser tabs I had open, I bumped into the SocialCG document that defines HashTag:
-
I have heard people say "In #ActivityPub there's a timeline and a notification feed". No, there isn't. But perhaps in ones solution, there is. "There are Mentions and Hashtags". No, there aren't. Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly). "There are special hashtags to put in a summary field that machines understand". Nope!
https://social.coop/@smallcircles/116394824802521441
There are #FEP documents. These are just guidance that allow people to align on common ways to achieve things, and are currently the best way to avoid an even larger sprawl of protocol decay. They are non-normative wrt to the AP protocol itself.
I think a large part of the quick rise in attractiveness, popularity and adoption of #ATProto stems from how it offered devs a clear and well-documented introduction and a path to doing solution development on top of a robust protocol, where a dev could say "this is my app, and this is protocol".
-
I have heard people say "In #ActivityPub there's a timeline and a notification feed". No, there isn't. But perhaps in ones solution, there is. "There are Mentions and Hashtags". No, there aren't. Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly). "There are special hashtags to put in a summary field that machines understand". Nope!
https://social.coop/@smallcircles/116394824802521441
There are #FEP documents. These are just guidance that allow people to align on common ways to achieve things, and are currently the best way to avoid an even larger sprawl of protocol decay. They are non-normative wrt to the AP protocol itself.
I think a large part of the quick rise in attractiveness, popularity and adoption of #ATProto stems from how it offered devs a clear and well-documented introduction and a path to doing solution development on top of a robust protocol, where a dev could say "this is my app, and this is protocol".
-
I have heard people say "In #ActivityPub there's a timeline and a notification feed". No, there isn't. But perhaps in ones solution, there is. "There are Mentions and Hashtags". No, there aren't. Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly). "There are special hashtags to put in a summary field that machines understand". Nope!
https://social.coop/@smallcircles/116394824802521441
There are #FEP documents. These are just guidance that allow people to align on common ways to achieve things, and are currently the best way to avoid an even larger sprawl of protocol decay. They are non-normative wrt to the AP protocol itself.
I think a large part of the quick rise in attractiveness, popularity and adoption of #ATProto stems from how it offered devs a clear and well-documented introduction and a path to doing solution development on top of a robust protocol, where a dev could say "this is my app, and this is protocol".
-
I have heard people say "In #ActivityPub there's a timeline and a notification feed". No, there isn't. But perhaps in ones solution, there is. "There are Mentions and Hashtags". No, there aren't. Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly). "There are special hashtags to put in a summary field that machines understand". Nope!
https://social.coop/@smallcircles/116394824802521441
There are #FEP documents. These are just guidance that allow people to align on common ways to achieve things, and are currently the best way to avoid an even larger sprawl of protocol decay. They are non-normative wrt to the AP protocol itself.
I think a large part of the quick rise in attractiveness, popularity and adoption of #ATProto stems from how it offered devs a clear and well-documented introduction and a path to doing solution development on top of a robust protocol, where a dev could say "this is my app, and this is protocol".
-
I have heard people say "In #ActivityPub there's a timeline and a notification feed". No, there isn't. But perhaps in ones solution, there is. "There are Mentions and Hashtags". No, there aren't. Though there may be #SocialCG recommendations on how to deal with those (I have eternal trouble finding these documents quickly). "There are special hashtags to put in a summary field that machines understand". Nope!
https://social.coop/@smallcircles/116394824802521441
There are #FEP documents. These are just guidance that allow people to align on common ways to achieve things, and are currently the best way to avoid an even larger sprawl of protocol decay. They are non-normative wrt to the AP protocol itself.
I think a large part of the quick rise in attractiveness, popularity and adoption of #ATProto stems from how it offered devs a clear and well-documented introduction and a path to doing solution development on top of a robust protocol, where a dev could say "this is my app, and this is protocol".
-
Not sure if there's an existing framework that can be designed to work with #ActivityPub. But I do think that thinking about consent in a more general/generic sense would be a worthwhile effort. This should be something that is picked up at the #SocialCG level, or perhaps in #FEP documents first. A lot of the mechanisms that proliferate now are also app-centric and almost *assume* that #fediverse is a glorified #microblogging environment. The more that trend continues, the more that will indeed be the case. This is what my long blog post was about, that I wrote recently:
-
Not sure if there's an existing framework that can be designed to work with #ActivityPub. But I do think that thinking about consent in a more general/generic sense would be a worthwhile effort. This should be something that is picked up at the #SocialCG level, or perhaps in #FEP documents first. A lot of the mechanisms that proliferate now are also app-centric and almost *assume* that #fediverse is a glorified #microblogging environment. The more that trend continues, the more that will indeed be the case. This is what my long blog post was about, that I wrote recently:
-
Not sure if there's an existing framework that can be designed to work with #ActivityPub. But I do think that thinking about consent in a more general/generic sense would be a worthwhile effort. This should be something that is picked up at the #SocialCG level, or perhaps in #FEP documents first. A lot of the mechanisms that proliferate now are also app-centric and almost *assume* that #fediverse is a glorified #microblogging environment. The more that trend continues, the more that will indeed be the case. This is what my long blog post was about, that I wrote recently:
-
Not sure if there's an existing framework that can be designed to work with #ActivityPub. But I do think that thinking about consent in a more general/generic sense would be a worthwhile effort. This should be something that is picked up at the #SocialCG level, or perhaps in #FEP documents first. A lot of the mechanisms that proliferate now are also app-centric and almost *assume* that #fediverse is a glorified #microblogging environment. The more that trend continues, the more that will indeed be the case. This is what my long blog post was about, that I wrote recently:
-
Not sure if there's an existing framework that can be designed to work with #ActivityPub. But I do think that thinking about consent in a more general/generic sense would be a worthwhile effort. This should be something that is picked up at the #SocialCG level, or perhaps in #FEP documents first. A lot of the mechanisms that proliferate now are also app-centric and almost *assume* that #fediverse is a glorified #microblogging environment. The more that trend continues, the more that will indeed be the case. This is what my long blog post was about, that I wrote recently:
-
@snarfed.org @quillmatiq @bnewbold.net @trwnh @darius @dmitri @thisismissem and others.
Bluesky is working on a new Communities feature for ATProto. At the same time, the #SocialCG at the W3C is working on Groups features for #ActivityPub.
It would be a missed opportunity if we used wildly different architectural patterns that made bridging the two models impossible.
I opened up an issue on our GitHub repo to discuss how we can minimise that:
-
@snarfed.org @quillmatiq @bnewbold.net @trwnh @darius @dmitri @thisismissem and others.
Bluesky is working on a new Communities feature for ATProto. At the same time, the #SocialCG at the W3C is working on Groups features for #ActivityPub.
It would be a missed opportunity if we used wildly different architectural patterns that made bridging the two models impossible.
I opened up an issue on our GitHub repo to discuss how we can minimise that:
-
@snarfed.org @quillmatiq @bnewbold.net @trwnh @darius @dmitri @thisismissem and others.
Bluesky is working on a new Communities feature for ATProto. At the same time, the #SocialCG at the W3C is working on Groups features for #ActivityPub.
It would be a missed opportunity if we used wildly different architectural patterns that made bridging the two models impossible.
I opened up an issue on our GitHub repo to discuss how we can minimise that:
-
@snarfed.org @quillmatiq @bnewbold.net @trwnh @darius @dmitri @thisismissem and others.
Bluesky is working on a new Communities feature for ATProto. At the same time, the #SocialCG at the W3C is working on Groups features for #ActivityPub.
It would be a missed opportunity if we used wildly different architectural patterns that made bridging the two models impossible.
I opened up an issue on our GitHub repo to discuss how we can minimise that:
-
@snarfed.org @quillmatiq @bnewbold.net @trwnh @darius @dmitri @thisismissem and others.
Bluesky is working on a new Communities feature for ATProto. At the same time, the #SocialCG at the W3C is working on Groups features for #ActivityPub.
It would be a missed opportunity if we used wildly different architectural patterns that made bridging the two models impossible.
I opened up an issue on our GitHub repo to discuss how we can minimise that:
-
There are certainly issues. I wrote a long thought piece on social experience and travels in #ActivityPub space and with a call-for-reflection to anyone to ponder #fediverse's Future of #SocialNetworking..
The blog post (which is an hour-long read) also stipulates re-centralization risks, and how a #fedi-native protocol implementation of #GrassrootsStandards and #GrassrootsStandardization processes like the #FEP and #SocialCG can help mitigate the #centralization risks.
https://social.coop/@smallcircles/116379158584600016
PS. See also my call-to-participate as #CommonsCustodian in the #standardization of our networking protocols..
https://social.coop/@smallcircles/116402592862958767
Together we can :boosts_appreciated: #BoostFediForwards and #cocreate a better #future.
-
There are certainly issues. I wrote a long thought piece on social experience and travels in #ActivityPub space and with a call-for-reflection to anyone to ponder #fediverse's Future of #SocialNetworking..
The blog post (which is an hour-long read) also stipulates re-centralization risks, and how a #fedi-native protocol implementation of #GrassrootsStandards and #GrassrootsStandardization processes like the #FEP and #SocialCG can help mitigate the #centralization risks.
https://social.coop/@smallcircles/116379158584600016
PS. See also my call-to-participate as #CommonsCustodian in the #standardization of our networking protocols..
https://social.coop/@smallcircles/116402592862958767
Together we can :boosts_appreciated: #BoostFediForwards and #cocreate a better #future.
-
There are certainly issues. I wrote a long thought piece on social experience and travels in #ActivityPub space and with a call-for-reflection to anyone to ponder #fediverse's Future of #SocialNetworking..
The blog post (which is an hour-long read) also stipulates re-centralization risks, and how a #fedi-native protocol implementation of #GrassrootsStandards and #GrassrootsStandardization processes like the #FEP and #SocialCG can help mitigate the #centralization risks.
https://social.coop/@smallcircles/116379158584600016
PS. See also my call-to-participate as #CommonsCustodian in the #standardization of our networking protocols..
https://social.coop/@smallcircles/116402592862958767
Together we can :boosts_appreciated: #BoostFediForwards and #cocreate a better #future.
-
There are certainly issues. I wrote a long thought piece on social experience and travels in #ActivityPub space and with a call-for-reflection to anyone to ponder #fediverse's Future of #SocialNetworking..
The blog post (which is an hour-long read) also stipulates re-centralization risks, and how a #fedi-native protocol implementation of #GrassrootsStandards and #GrassrootsStandardization processes like the #FEP and #SocialCG can help mitigate the #centralization risks.
https://social.coop/@smallcircles/116379158584600016
PS. See also my call-to-participate as #CommonsCustodian in the #standardization of our networking protocols..
https://social.coop/@smallcircles/116402592862958767
Together we can :boosts_appreciated: #BoostFediForwards and #cocreate a better #future.
-
There are certainly issues. I wrote a long thought piece on social experience and travels in #ActivityPub space and with a call-for-reflection to anyone to ponder #fediverse's Future of #SocialNetworking..
The blog post (which is an hour-long read) also stipulates re-centralization risks, and how a #fedi-native protocol implementation of #GrassrootsStandards and #GrassrootsStandardization processes like the #FEP and #SocialCG can help mitigate the #centralization risks.
https://social.coop/@smallcircles/116379158584600016
PS. See also my call-to-participate as #CommonsCustodian in the #standardization of our networking protocols..
https://social.coop/@smallcircles/116402592862958767
Together we can :boosts_appreciated: #BoostFediForwards and #cocreate a better #future.
-
#BoostFediForwards :boosts_appreciated:
In this rushed world of ours, do you still have #time on your hands here and there? And love spending it on building and nurturing our sustainable and safe #fedi gardens?
Do you want be more deeply involved in weaving delightful #SocialFabric? Play a part in #SocialWeb future?
Then #SocialHub, the discussion forum for #ActivityPub developers, has #vacancies for you!
The #FEP Process as well as the #W3C #SocialCG, the two major standardization bodies that drive #fediverse future, are inclusive and open to anyone to contribute their 2 cents.
Become a #CommonsCustodian now..
Help cocreate a 💃🕺 #peopleverse.https://delightful.coding.social/delightful-fediverse-experience/
#UrgentPlatitude: Our #future is created today, not #tomorrow.
See also the broader discussion on ecosystem #sustainability and my personal story and #brainstorm invitation about fedi's #evolution.
https://discuss.coding.social/t/sx-sustainable-ecosystem-evolution-see/836
-
#BoostFediForwards :boosts_appreciated:
In this rushed world of ours, do you still have #time on your hands here and there? And love spending it on building and nurturing our sustainable and safe #fedi gardens?
Do you want be more deeply involved in weaving delightful #SocialFabric? Play a part in #SocialWeb future?
Then #SocialHub, the discussion forum for #ActivityPub developers, has #vacancies for you!
The #FEP Process as well as the #W3C #SocialCG, the two major standardization bodies that drive #fediverse future, are inclusive and open to anyone to contribute their 2 cents.
Become a #CommonsCustodian now..
Help cocreate a 💃🕺 #peopleverse.https://delightful.coding.social/delightful-fediverse-experience/
#UrgentPlatitude: Our #future is created today, not #tomorrow.
See also the broader discussion on ecosystem #sustainability and my personal story and #brainstorm invitation about fedi's #evolution.
https://discuss.coding.social/t/sx-sustainable-ecosystem-evolution-see/836
-
#BoostFediForwards :boosts_appreciated:
In this rushed world of ours, do you still have #time on your hands here and there? And love spending it on building and nurturing our sustainable and safe #fedi gardens?
Do you want be more deeply involved in weaving delightful #SocialFabric? Play a part in #SocialWeb future?
Then #SocialHub, the discussion forum for #ActivityPub developers, has #vacancies for you!
The #FEP Process as well as the #W3C #SocialCG, the two major standardization bodies that drive #fediverse future, are inclusive and open to anyone to contribute their 2 cents.
Become a #CommonsCustodian now..
Help cocreate a 💃🕺 #peopleverse.https://delightful.coding.social/delightful-fediverse-experience/
#UrgentPlatitude: Our #future is created today, not #tomorrow.
See also the broader discussion on ecosystem #sustainability and my personal story and #brainstorm invitation about fedi's #evolution.
https://discuss.coding.social/t/sx-sustainable-ecosystem-evolution-see/836
-
#BoostFediForwards :boosts_appreciated:
In this rushed world of ours, do you still have #time on your hands here and there? And love spending it on building and nurturing our sustainable and safe #fedi gardens?
Do you want be more deeply involved in weaving delightful #SocialFabric? Play a part in #SocialWeb future?
Then #SocialHub, the discussion forum for #ActivityPub developers, has #vacancies for you!
The #FEP Process as well as the #W3C #SocialCG, the two major standardization bodies that drive #fediverse future, are inclusive and open to anyone to contribute their 2 cents.
Become a #CommonsCustodian now..
Help cocreate a 💃🕺 #peopleverse.https://delightful.coding.social/delightful-fediverse-experience/
#UrgentPlatitude: Our #future is created today, not #tomorrow.
See also the broader discussion on ecosystem #sustainability and my personal story and #brainstorm invitation about fedi's #evolution.
https://discuss.coding.social/t/sx-sustainable-ecosystem-evolution-see/836
-
#BoostFediForwards :boosts_appreciated:
In this rushed world of ours, do you still have #time on your hands here and there? And love spending it on building and nurturing our sustainable and safe #fedi gardens?
Do you want be more deeply involved in weaving delightful #SocialFabric? Play a part in #SocialWeb future?
Then #SocialHub, the discussion forum for #ActivityPub developers, has #vacancies for you!
The #FEP Process as well as the #W3C #SocialCG, the two major standardization bodies that drive #fediverse future, are inclusive and open to anyone to contribute their 2 cents.
Become a #CommonsCustodian now..
Help cocreate a 💃🕺 #peopleverse.https://delightful.coding.social/delightful-fediverse-experience/
#UrgentPlatitude: Our #future is created today, not #tomorrow.
See also the broader discussion on ecosystem #sustainability and my personal story and #brainstorm invitation about fedi's #evolution.
https://discuss.coding.social/t/sx-sustainable-ecosystem-evolution-see/836
-
#ThoughtProvoker :blobhyperthink:
App-centrism is a re-centralization force in the #ActivityPub fediverse.
For the #fediverse the accepted app-centric #SocialNetwork work method is a decentralized NPM-like dependency hell waiting to happen.
Apps that introduce extensions become owners of parts of the specs when they become de-facto standards. We can only hope for responsible #ownership, and that the project stays around to keep their #design docs and code in the air.
The #FEP and the #SocialCG are two points of #centralization we find acceptable to help mitigate protocol decay and tech debt. It is not ideal, but a bandaid to keep an utterly fragmented developer ecosystem together.
The people who do most of this holding together are volunteers that can be counted on one hand. They may burnout and leave any day, in typical #FOSS fashion.
#SX investigates the concept of #GrassrootsOpenStandards, where the standardization process matches social dynamics that exist in our #commons.
-
#ThoughtProvoker :blobhyperthink:
App-centrism is a re-centralization force in the #ActivityPub fediverse.
For the #fediverse the accepted app-centric #SocialNetwork work method is a decentralized NPM-like dependency hell waiting to happen.
Apps that introduce extensions become owners of parts of the specs when they become de-facto standards. We can only hope for responsible #ownership, and that the project stays around to keep their #design docs and code in the air.
The #FEP and the #SocialCG are two points of #centralization we find acceptable to help mitigate protocol decay and tech debt. It is not ideal, but a bandaid to keep an utterly fragmented developer ecosystem together.
The people who do most of this holding together are volunteers that can be counted on one hand. They may burnout and leave any day, in typical #FOSS fashion.
#SX investigates the concept of #GrassrootsOpenStandards, where the standardization process matches social dynamics that exist in our #commons.
-
#ThoughtProvoker :blobhyperthink:
App-centrism is a re-centralization force in the #ActivityPub fediverse.
For the #fediverse the accepted app-centric #SocialNetwork work method is a decentralized NPM-like dependency hell waiting to happen.
Apps that introduce extensions become owners of parts of the specs when they become de-facto standards. We can only hope for responsible #ownership, and that the project stays around to keep their #design docs and code in the air.
The #FEP and the #SocialCG are two points of #centralization we find acceptable to help mitigate protocol decay and tech debt. It is not ideal, but a bandaid to keep an utterly fragmented developer ecosystem together.
The people who do most of this holding together are volunteers that can be counted on one hand. They may burnout and leave any day, in typical #FOSS fashion.
#SX investigates the concept of #GrassrootsOpenStandards, where the standardization process matches social dynamics that exist in our #commons.
-
#ThoughtProvoker :blobhyperthink:
App-centrism is a re-centralization force in the #ActivityPub fediverse.
For the #fediverse the accepted app-centric #SocialNetwork work method is a decentralized NPM-like dependency hell waiting to happen.
Apps that introduce extensions become owners of parts of the specs when they become de-facto standards. We can only hope for responsible #ownership, and that the project stays around to keep their #design docs and code in the air.
The #FEP and the #SocialCG are two points of #centralization we find acceptable to help mitigate protocol decay and tech debt. It is not ideal, but a bandaid to keep an utterly fragmented developer ecosystem together.
The people who do most of this holding together are volunteers that can be counted on one hand. They may burnout and leave any day, in typical #FOSS fashion.
#SX investigates the concept of #GrassrootsOpenStandards, where the standardization process matches social dynamics that exist in our #commons.
-
#ThoughtProvoker :blobhyperthink:
App-centrism is a re-centralization force in the #ActivityPub fediverse.
For the #fediverse the accepted app-centric #SocialNetwork work method is a decentralized NPM-like dependency hell waiting to happen.
Apps that introduce extensions become owners of parts of the specs when they become de-facto standards. We can only hope for responsible #ownership, and that the project stays around to keep their #design docs and code in the air.
The #FEP and the #SocialCG are two points of #centralization we find acceptable to help mitigate protocol decay and tech debt. It is not ideal, but a bandaid to keep an utterly fragmented developer ecosystem together.
The people who do most of this holding together are volunteers that can be counted on one hand. They may burnout and leave any day, in typical #FOSS fashion.
#SX investigates the concept of #GrassrootsOpenStandards, where the standardization process matches social dynamics that exist in our #commons.
-
@evan some time ago you queried about what would be a good comms channel for #ActivityPub API.
I have some ideas / recommendations on the #Github repo that the #W3C TF uses.
- Structure the repo to hold the work of the full task force, not just for the creation of a single specification document.
- Use GH Discussions for all the general elaboration, feedback collection, etc. The repo forms a self-contained body of work. Move most current Issues in the tracker to become Discussions.
- Issues are created by task force members, and always represent actionable items. They are tracked on a Project kanban board where the swimlanes represent a simple protocol development #Process with a number of stages.
Then:
- Primary comms channel is Discussions.
- Issues + kanban represent work tracks.
- Secondary comms channel can be #fedi.I'd reserve #SocialCG mailing list to #governance and organizational matters concerning the CG itself, and point mails on other subject to appropriate channel.