-
Notifications
You must be signed in to change notification settings - Fork 308
implement a basic income #84
Comments
Closing this in favor of gift bombs (#131). This is pull. That is push. |
I think the algorithm should be: Pay out in pennies, newest participant first. This is how we give everyone a penny (#652). So if there's $50/wk in the community chest, then the newest 5,000 users that week get a penny, and the next week the newest 5,000 users get a penny, etc. So how long you get a penny a week for depends on how fast the site grows. If the site gets 1,000 new users a week then you'd get a penny a week for five weeks. That helps break the ice for you and welcome you to the site. In fact (brainstorming at the retreat), this would be a fantastic teaching tool as part of the sign-up / onboarding workflow. So right after you sign in we say "Welcome to Gittip! Here's your free penny! What would you like to do with it? Options: Give it away. Put it in your bank account. etc." For the normal case where the user signs up to support a specific receiver, we use the penny as the hook at the end of the sign-up flow to draw them further in. We give them the normal one-off payment option, and then at the end we say "Click here for your free penny!" and then that links to the landing page with "Here you go! What you like to do with it?" |
This is interesting again! Gittip retreat! |
I see this as Gittip's answer to a coercive (tax-funded) universal income. |
If we keep escrow in an Ally savings account we could get 0.85% APY risk-free, and we could use that to (partially) fund this community chest. |
+0 from @quinnnorton on Twitter:
|
Verifying identity (#2449) could enable this. |
Reading this, I assume it is blocked because we couldn't verify that every account on Gratipay was owned by a (single) real person. With teams under Gratipay 2.0, it seems that we are doing our identification due diligence ("community curation") before a person gets into the system, so maybe this is now possible? |
Community curation isn't sufficient for KYC (#3289). We need personally identifying information (name, address, SSN). Once we have that, yes: we can revisit here. |
@Sirjazzfeet points to http://groupincome.org/ (yes?) at https://www.loomio.org/d/tNhk36m9/group-income.
|
When thinking of BI a top-down approach comes to mind, as its ideally to everyone. But such top-down design is archaic and is increasingly being made to look very foolish. I'm all for a system that reaches to everyone, but how we reach that point is important, the means influence the ends. I think we need to move away from the totalitarian-like approach of enforcing universal re-distribution through centralised command design of economy and towards greater respect for cultural subjectivity, freedom and democracy. We should seek to maximise individual empowerment and reduce dependence on centralised power (not to say centralised power shouldn't help to resource and develop). The top-down approach will always prone to exploitation and lean towards criminality and greater violence to enforce. Information asymmetry between designers and users makes it inefficient, inflexible, blind, politically abrasive, difficult to scale due to lack of critical distributed control, security and trust. So an incremental bottom-up design, that will perhaps become federated, but certainly more organic, this would be easier to implement politically / culturally (the main obstacle) but also more resilient and dynamic, allowing for greater interoperability.. the potential for integration with social organisation, markets, commons, reputation systems, etc. A self-sustaining platform rather than a handout. Some ideas: |
https://medium.com/@resilience_me/resilience-a-fully-voluntary-wealth-sharing-network-6873c927736a |
"Community curation isn't sufficient for KYC (#3289)" What is KYC, how come team curation doesn't solve the issue? |
KYC stands for "know your customer" and refers to the identity verification requirements of the global financial system. The tl;dr of #3289 is that we've got to collect national identity numbers and other personally identifying information, and cross-check it with screening vendors such as Trulioo. In Team curation we look at whether they provide open work and fit our brand, we don't do any identity verification there currently. |
What I'm saying is: if a team made it transparent that once their basic income quota was full, any further donations for that month would go directly a person or team they have designated, does there still need to be KYC? after all a team wouldn't give money to someone they don't trust or know, and shouldn't the responsibility of distributing their basic income be with the team. ( I must have been tired, could have google'd the definition also, sorry. ) |
Huh. I've been thinking so far that basic income would attach to individuals, not to Teams. There'd be some pool that everyone on Gratipay could voluntarily pay in to, which would redistribute equally to every individual on the platform. Let's say there are 10,000 users on Gratipay, and 1,000 pay in to the basic income pool totaling $1,000 per week. Everyone would get 10¢ of basic income per week, in addition to what they take for themselves from the Teams of which they're a member. Perhaps companies (including many Teams) could pay into the basic income pool as well, though they wouldn't receive basic income since it attaches only to natural persons. How are you thinking basic income would work? |
11 cents per week ($1,000/9,000 users), if you consider the silliness of giving out money for basic income and then receiving less of it right back. |
Sure, though if we're talking silliness 11¢ a week doesn't go much farther than 10¢. 😜 |
Actually, I think this is an important question: who receives the basic income? Everyone? Or only the poor? If it's only the poor then it seems that we are reifying the distinction. Giving is empowering. If I'm poor enough to receive the basic income—what if I want to give 1¢ a week into the basic income pool? "Sorry, you're too poor to give." That doesn't seem right. |
I'm thinking the group basic income would suit Gratipay best. Though you could have both if you like. But 10 cents is neither here nor there. With Group Basic Income, each group decides who their excess income goes to. Thereby creating an incentive to collaborate and focus resources towards commonwealth projects. Such a bottom up approach takes care of such questions, if people want to give to poor only, that's fine, but this way they are not forced to. But since groups set transparent caps on their income, distributing the overflow to form basic income network, it becomes exponentially inclusive. |
Moved to gratipay/inside.gratipay.com#973 for high-level discussion. Will reopen when there's concrete plan and design. |
Make it possible to allocate a portion of one's weekly balance to a community chest, which would algorithmically be distributed amongst the community. What should the algorithm be?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: