Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

How do you ensure "one user, one vote?"

This seems impossible without intrusive government ID verification, and not immune to government meddling in any case.



To be determined. It's not a problem we have yet, since we're going to ease into the cooperative governance.

Right now it's an LLC. If we can hit basic financial stability, then we'll convert the LLC to a nonprofit and start with an appointed board with a two year term who's job is to draft the permanent bylaws and define the electoral system. Basically, I'm bootstrapping it and we need to raise the money to pay the legal fees and fund the legal research needed to get the cooperative structure right. And part of that is going to be designing the electoral systems.

It's definitely going to be hard and it may end up coming down to "ID verification required to vote". Not to use the platform, just to vote in board elections. I'd love to find a way to avoid that, but we can always do it if we have to.

The plan is to moderate the platform pretty heavily using a two layered moderation system: community moderation as the first layer and official moderation as a second layer that moderates the community moderation. That moderation will be very much aimed at keeping the platform as free of bots, spammers, and propagandists as possible.

So if we're successful in that, we may be able to avoid the intrusive verification by saying "It's an honor system and all active users in good standing are trusted to be honorable." But it remains to be seen whether we're successful enough in the moderation to even attempt that.

Or we may be able to come up with some other system to ensure it.

The other piece is that it's a multi-stakeholder cooperative. Users elect half the board, but the workers elect the other half. And with workers, it will be easy to restrict it to one worker one vote. So the workers can and will provide a safety backstop against user elections that go off the rails in one way or another.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: