on master help sign in
snapshot link
commita3c6cc9d25b81a1dabcaeb8160cf01f8b4d6e19f authorGordon <gordon@hey.com> dateWed 5 Oct 2022, 15:12 (4 years ago) parent76c2ef3
1 file changed+1−1
content/blog/urbit-creator-daos.md+1−1
content/blog/urbit-creator-daos.md+1−1
@@ -35,7 +35,7 @@ Straw opens up a whole new way to decide what—and who—creators publish next.
3535
3636# Decentralized Kicking and Adding
3737
38−Urbit also offers a novel solution with regards to vetting group members and weeding out bad ones. As Murphy points out, the Holium’s Urbit app Ballot—which works like a decentralized Snapshot for Urbit Groups—allows creators to decentralize the expulsion process which many creators who run creator networks would much prefer.
38+Urbit also offers a novel solution with regards to vetting group members and weeding out bad ones. As Murphy points out, the Holium’s Urbit app Ballot—which works like a decentralized [Snapshot](https://snapshot.org/#/) for Urbit Groups—allows creators to decentralize the expulsion process which many creators who run creator networks would much prefer.
3939
4040> If someone makes a proposal in [Ballot](https://urbit.org/applications/~lomder-librun/ballot), and maybe the owner gets to decide the threshold where if a certain amount of people want to kick someone out, they're kicked. It's actually a really annoying burden, in some ways, to know who to kick out. How bad does someone have to bet? You can have all the rules and regulations you want and try to be as objective as possible, but ultimately the owners and the admins have to use their judgment to decide. I would frankly much rather not have that responsibility. I would love for it to be hardwired such that only a super majority, or something like that, could do it. You can imagine that as a custom action on Ballot.
4141