If anyone is interested, I have a simulator for pool-based funding as I'm working on a side project that uses the same approach: http://syd.jjcm.org/soci/ http:

If anyone is interested, I have a simulator for pool-based funding as I'm working on a side project that uses the same approach: http://syd.jjcm.org/soci/ http://syd.jjcm.org/soci/ My project is essentially a reddit-esque site that hosts images/blogs/video/audio content. Each vote on a piece of content gives it one share of your funding pool for that month. The pool based approach is definitely the best for simple usability, but there's another aspect to it as well: it means you weigh your vote more. In the case of a social sharing/news site, low-effort content will get upvoted less, as you have to consider that every vote will dilute the pool. I'm really bought in on this as an overall concept and I think it's something that will be extremely healthy for the web overall. Previously this was a model that was used by Flattr, but they had a major issue that not everyone was on their platform, so often times creators wouldn't get money out of a donation (because they didn't know the donation existed). I definitely agree with the author here that if this were to be done, Github themselves would have to implement it. As soon as a third party who isn't hosting the content implements it, an enormous percentage of creators wont know they have funding waiting for them and things fall apart.