"If you are living with other humans, getting along is essential. You need human discussion and consent. For example, ragequit is not a good mechanism for co-living. Deeper understanding and willingness to find compromise isn't part of DAO tooling."

"Better frameworks for living together are group rituals, culture, storytelling, sharing protocols, and even religion or spirituality. There's rich history in ecovillages and intentional communities about what works and what doesn't."

"they still need to manage money"

"They still need to manage assets."

Ragequit: this feature embodies the very spirit of Moloch. It's an action designed for individual self-preservation by removing oneself from the process of collective governance. Anyone who ragequits needs to pack their bags and leave the commune. As identified above, ragequit should be wholly excluded from many community coordination strategies; depending on what the specific governable asset(s) are and the context around the community managing them.

Discussion and Consent: I would reframe these two participatory activities as being 100% essential components in a "healthy" DAO. They can also be embedded as conditions that gate access to proposing and/or voting in various ways. A more nuanced approach is to apply granular permissions on which members & groups in a DAO can create different types of proposals (e.g. @AstroDao policies) - and by using some sort of "reputation modifiers" to adjust vote weight depending on whether a member participated in a contributing activity.

Co-living Frameworks: as with discussion & consent, we can systematically apply conditions and weights to members' proposal & voting rights based on specific actions performed in any of the co-living strategies mentioned above (e.g. group rituals, storytelling, etc). Defining these conditions along with appropriate input and output metrics can be done fairly easily using flexible documentation & referencing systems like @eas_eth and @HyperfilesOrg.

Ragequit has proven to be a valuable tool in reimagining exit strategies for IRL projects. It does happen a lot, causing dreams to be buried and land sold. Life changes are a part of life, you have to go in prepared to go out even if you think you never will.

This article is composed of excerpts from one of Dr. Nick's post on X.

"If you are living with other humans, getting along is essential. You need human discussion and consent. For example, ragequit is not a good mechanism for co-living. Deeper understanding and willingness to find compromise isn't part of DAO tooling."

"Better frameworks for living together are group rituals, culture, storytelling, sharing protocols, and even religion or spirituality. There's rich history in ecovillages and intentional communities about what works and what doesn't."

"they still need to manage money"

"They still need to manage assets."

Ragequit: this feature embodies the very spirit of Moloch. It's an action designed for individual self-preservation by removing oneself from the process of collective governance. Anyone who ragequits needs to pack their bags and leave the commune. As identified above, ragequit should be wholly excluded from many community coordination strategies; depending on what the specific governable asset(s) are and the context around the community managing them.

Discussion and Consent: I would reframe these two participatory activities as being 100% essential components in a "healthy" DAO. They can also be embedded as conditions that gate access to proposing and/or voting in various ways. A more nuanced approach is to apply granular permissions on which members & groups in a DAO can create different types of proposals (e.g. @AstroDao policies) - and by using some sort of "reputation modifiers" to adjust vote weight depending on whether a member participated in a contributing activity.

Co-living Frameworks: as with discussion & consent, we can systematically apply conditions and weights to members' proposal & voting rights based on specific actions performed in any of the co-living strategies mentioned above (e.g. group rituals, storytelling, etc). Defining these conditions along with appropriate input and output metrics can be done fairly easily using flexible documentation & referencing systems like @eas_eth and @HyperfilesOrg.

Ragequit has proven to be a valuable tool in reimagining exit strategies for IRL projects. It does happen a lot, causing dreams to be buried and land sold. Life changes are a part of life, you have to go in prepared to go out even if you think you never will.

This article is composed of excerpts from one of Dr. Nick's post on X.