# The "You can ..." - language aka "Language of Empowerment" **URL:** \ **Category:** Commons based social stack\ **Tags:** fediverse, vision, sx\ **Created:** [January 11, 2025, 11:47am UTC](https://discuss.coding.social/t/the-you-can-language-aka-language-of-empowerment/593 "2025-01-11T11:47:41Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![helge](https://discuss.coding.social/user_avatar/discuss.coding.social/helge/32/252_2.png) [@helge](https://discuss.coding.social/u/helge)\ **Post date:** [January 11, 2025, 11:47am UTC](https://discuss.coding.social/t/the-you-can-language-aka-language-of-empowerment/593/1 "2025-01-11T11:47:41Z")
This is a distillation of a language thing, I’ve been talking about in the matrix room: [https://matrix.to/#/#groundwork-matters:matrix.org](https://matrix.to/#/#groundwork-matters:matrix.org) Second a goal is to achieve what is pointed out in [Wiki: Vision for a Fedi Specification](https://discuss.coding.social/t/wiki-vision-for-a-fedi-specification/563/6): > [@Wiki: Vision for a Fedi Specification](https://discuss.coding.social/t/wiki-vision-for-a-fedi-specification/563/6): > > Most important that we start speaking a common language, a Ubiquitous language (UL), right from the start. ## The goal - Develop a language that can let us clearly communicate our vision for the Fediverse - This language should state verifiable goals → **Testability** ## The main idea My main claim is that by specifying our **Vision for the Fediverse** as statements starting with “You can …”, we can ensure that our statements are meaningful and the chance of people understand them differently is lowered. In order to explain what a “you can”-statement is, I will do an example: > You can change service without losing your data. Here the word **you** is the person using your eventual new social network / evolved Fediverse. This is work towards turning our evolved Fediverse into a Peopleverse, as we emphasize what the person using it can do. Second, with **you can** , we describe an action that the person can take. For me, this is an obvious advantage. I encourage everybody to use BDD anyway. So it’s cool. However, I also believe that it is good for a less technical audience, as it tells them what they can do. ### Relationship to BDD From a BDD perspective, one could rewrite the above “You can”-Statement as: ```gherkin When you change service Then you don't lose your data ``` This is not a complete feature yet, as the setup is missing. However, I hope it is clear how often rewriting will be possible. **Note** : It is not necessary for a “You can”-Statement to be valid, that one can rewrite it as a Gherkin feature. ## Evolution of the idea The idea of formulating the thing as “You can”-Statements did not arise in a vacuum, but comes from trying to specify a language so one can make better statements about a Fediverse visioin. I will now take you through my journey (as I remember it), to the “you-can”-statement. This will be by looking at statements, I consider bad. > The network is decentralized. Thinking about this statement was the first time, I realized, a lot of people talk about this, but I don’t care. It’s something that doesn’t matter in my world. From the perspective of the people, it also doesn’t matter. It doesn’t look at what happens to a person. It treats people as a big entity to describe. Instead, I prefer the statement > You can self-host. This is something that a person can do. It is also very simple to disprove. Can somebody set up an instance for your network while waiting for the train? In an afternoon? With 2 weeks of work? Here, I was thinking about the you statement. Then, I encountered the you statement: > You have data ownership. It’s a “You”-Statement, unfortunately I also dislike it. It sounds like something lawyers will have to litigate in order to assign meaning. So it’s nothing for me. Also it is not really behavior. The alternative was > You can change service without losing your data. from above. ## Another example: E2EE Adding E2EE to the Fediverse is interesting from a technical standpoint. It would force one to clean up what an actor is comparred to what the user’s device is. This is due to the encryption keys being generated on the device and never leaving it. Anything else is not **end to end** encryption, just encryption. However, if you formulate this as a “You can”-Statement, you realize that what you can achieve with E2EE is probably weaker than is worth the investment: > You can communicate without admins knowing your message content. Why is this weak? You admins will still know you send a message. If you want E2EE with some anonymity properties, you should probably look outside the Fediverse. # A proposed list of “you can …” statements ## Structure of the network - You can self-host. - You can change service without losing your data. ## Structure of the process - You can participate in the protocol process without gate keepers. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [January 11, 2025, 1:00pm UTC](https://discuss.coding.social/t/the-you-can-language-aka-language-of-empowerment/593/2 "2025-01-11T13:00:18Z")
This is a great subject, and promising way forward. At this point, and with an uncertain planning for 2025, I can add that I intend to do something with the wordplay that exists in “social coding”, and it relates to this slogan: > ### Social coding movement: " We social code the social code " There’s a ‘sauce’ that makes a communication network a social network in true sense of the word “social”. Where social coding is the holistic method and “the social code” not just the tech but encompassing the entire social experience. “Social code” then indicates a kind of domain to be modeled and evolved, giving common language, concepts and terminology against which the field of SX might emerge. (PS. The project will be named SocialCode) ---
**Author:** ![helge](https://discuss.coding.social/user_avatar/discuss.coding.social/helge/32/252_2.png) [@helge](https://discuss.coding.social/u/helge)\ **Post date:** [January 14, 2025, 11:37am UTC](https://discuss.coding.social/t/the-you-can-language-aka-language-of-empowerment/593/3 "2025-01-14T11:37:50Z")
> [@helge](#): > > The network is decentralized. On a side note. If you want views on decentralization, look at > **[Interpeer Project (@interpeer@chaos.social)](https://chaos.social/@interpeer/113685467599117325)** > > In response to a number of recent discussions on the (de-)centralization of networks, here's a somewhat grandiosely titled first part in a short series of blog posts that re-examine this... by @jfinkhaeuser. In particular, pointing out [On (De-)Centralized Communications: Part 3](https://interpeer.org/blog/2025/01/on-de-centralized-communications-part-3/#fediverse-centralization) (the fediverse link), where he correctly makes the case that the Fediverse is non resilient, e.g. you lose a host, you loose its data. To continue my “You can …” exercise: > If a server dies, you can host its data somewhere new. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [January 14, 2025, 11:49am UTC](https://discuss.coding.social/t/the-you-can-language-aka-language-of-empowerment/593/4 "2025-01-14T11:49:31Z")
Indeed. Jens was among a small circle of people with whom I reflected my thoughts on new forms of organization within grassroots movements, among others to address the sustainable evolution of a humane technology base on which a thriving ecosystem can emerge. Validation of that concept has ended, as I move to a different aspect of grassroots collaboration at scale: cocreation. It would be fabulous if @jfinkhaeuser might provide insights from Interpeer as input to our current efforts now and then, in moments when there is time and opportunity.