on master help sign in
massaging copy in last section
commit1879e7cc95122d1ad0690d41ef431dcb7dbe09a7 authorGordon <gordon@hey.com> dateWed 5 Oct 2022, 17:58 (4 years ago) parenta16f27c
1 file changed+1−1
content/blog/urbit-creator-daos.md+1−1
content/blog/urbit-creator-daos.md+1−1
@@ -37,7 +37,7 @@ Straw opens up a whole new way to decide what—and who—creators publish next.
3737
3838# Decentralized Kicking and Adding
3939
40−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.
40+Urbit also offers a novel solution with regards to vetting group members and weeding out bad ones. As Murphy points out, Holium’s Urbit app Ballot—which works like a decentralized [Snapshot](https://snapshot.org/#/) for Urbit Groups—allows creators to decentralize the expulsion process. A shift which many who run creator networks would much prefer.
4141
4242> 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.
4343