You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2024. It is now read-only.
Wanted to further my own musings on the "community comms" thread. I also realise I don't have all the information about TBD, and thus some of my thinking may be off-track. Nevertheless, seems worth some discussion.
In my mind, there are two things going on here.... the first is bringing to life a brand new dweb / web3 tech stack (based on ipfs, did, vc, dweb nodes) and the second is TBD creating useful products based on that stack (starting with TBdex).
My inclination on the first point is that we should be thinking about a "brand" that encapsulates the stack and its future impact on the world, that isn't directly tied to any one entity, and (as much as is possible at such an early stage) is run by a community that includes TBD, but isn't run by it. This would put the focus on building a community around the tech stack and its possibilities, rather than muddling it with the TBD-centric products.
This would lend itself to having a discord, github repo, documentation etc under that community-run brand, as a clear statement of differentiation compared to many other projects in the web3 space that often feel like they aren't being run in the best interests of individual users.
As for the brand itself, terms that jump out at me are things like "self-sovereign stack" or the "dweb stack".
If there was any interest in something like this, more than happy to be a part of helping to bring it to life. That's if I'm not the only one that thinks it has any merit! 😄
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Wanted to further my own musings on the "community comms" thread. I also realise I don't have all the information about TBD, and thus some of my thinking may be off-track. Nevertheless, seems worth some discussion.
In my mind, there are two things going on here.... the first is bringing to life a brand new dweb / web3 tech stack (based on ipfs, did, vc, dweb nodes) and the second is TBD creating useful products based on that stack (starting with TBdex).
My inclination on the first point is that we should be thinking about a "brand" that encapsulates the stack and its future impact on the world, that isn't directly tied to any one entity, and (as much as is possible at such an early stage) is run by a community that includes TBD, but isn't run by it. This would put the focus on building a community around the tech stack and its possibilities, rather than muddling it with the TBD-centric products.
This would lend itself to having a discord, github repo, documentation etc under that community-run brand, as a clear statement of differentiation compared to many other projects in the web3 space that often feel like they aren't being run in the best interests of individual users.
As for the brand itself, terms that jump out at me are things like "self-sovereign stack" or the "dweb stack".
If there was any interest in something like this, more than happy to be a part of helping to bring it to life. That's if I'm not the only one that thinks it has any merit! 😄
Beta Was this translation helpful? Give feedback.
All reactions