I'm very proud that we implemented democratic features directly into https://karrot.world/ - currently there is a network of trust to gain editing rights, and discussion then score voting for group removal.
I'm not aware of other bits of software that use democratic processes to actually perform actions within the software. I'm sure there must be some others though...
Standalone democratic process tools kind of miss the point for me. I want to see democracy deeply embedded into our tools.
@nicksellen sounds really interesting! What's Karrot for exactly? There's no description on the site and I'd like to read something before signing up
@michel_slm hey, thanks for the interest. You're right that page doesn't explain much. We chat with groups first in person or via email rather than random people arriving on that page, but it would be nice to support that too.
The focus is on grassroots community food saving - collecting excess food from being wasted. Similar to foodsharing.de in German-speaking countries.
But the features are general purpose so can be used for other things.
A bit more info is on https://foodsaving.world/karrot
@Matt_Noyes @michel_slm @appleseed we (as a project) exchanged emails before, differences from what we can remember is that robot:
- is for bringing food to centralized food bank
- has multi-level user roles
- is available in English only
- no messaging/app
Could be misremembered/wrong/outdated though!
Important principle is that communities can input into the software - to support plurality of approaches.
Software should follow the community not the reverse. Not one tool for all people.
@nicksellen wow I'd love to learn more. Any docs on the Democratic structures? I'd love to learn more. Working on this now: https://osf.io/gxu3a/?view_only=11c9e93011df4865951f2056a64f5938
@ntnsndr sure! You can read https://community.foodsaving.world/t/info-how-does-the-conflict-resolution-feature-work/254 and https://community.foodsaving.world/t/info-karrot-trust-system-and-user-levels/108 which explain the system. It took a lot of discussion to get to this point. We always resisted adding normal admin features.
@nicksellen thanks for this—really interesting. Seems to have resemblances with reputation-based decentralized networks. But since this is a self-hosted system, what special powers does the hoster have other than pulling the plug?
@ntnsndr the hoster has no special powers within the application. Currently all groups use our hosted instance as they tend to be small low tech volunteer groups.
We don't attempt to solve the problem that people with server access can do anything. That's a tough one to solve and have usable software.
We're trying to get some sort of co-op model to oversee the project and server/data ownership/management. Stalled a bit recently though.
@nicksellen really interesting. I just ask because the disproportionate role and cost of the hosting role tends to correlate with governance powers. Cooperative hosting seems like an important prerequisite.
@douginamug @maxlath @jums there are some user-level docs at https://community.foodsaving.world/t/info-how-does-the-conflict-resolution-feature-work/254/2 and https://community.foodsaving.world/t/info-karrot-trust-system-and-user-levels/108.
As for code, it's spread between frontend/backend, the score voting bit is part of an "issue" (e.g. https://github.com/yunity/karrot-backend/blob/master/karrot/issues/models.py#L44) - Tilmann could tell you more, whichever room he is hiding in ;)
It took a long time to get that far, we did a collaborative "storyboarding" session to think how the feature should work, well before any coding. Highly recommend doing those.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!