[bglusman]

This is awesome! My first startup was a kickstarter competitor (enjyn.com) and something like this is one of the big things I wanted to do for code!

My tentative plan was not to just make it for coders though, and to break things down, so one task is to write unit/accceptance tests for a portion of the bounty (maybe configurable, maybe 20 or 30%? dunno) and once the bounty for the tests was accepted, any code that passes those tests automatically gets the remainder of the bounty... if Gun.io can benefit from this idea, my blessings to you!

[Mizza]

Thanks for your kind words!

I've thought a lot about the interesting ways to break projects down into things like that, I really like that test case idea. I'm also looking at integrating tightly with github, so that a commit could flag an action on Gun.io, there could be a post commit hook with .BOUNTY files, things like that. Really I'm just waiting to see how people use this iteration before I work on the next one, though.

Just out of curiosity - what did you learn from Enjyn? Would you consider it a success or a failure? What would you have done differently?

[bglusman]

Sounds like you've got some good ideas, I figured you might :-) I dunno how I'd characterize Enjyn, probably a good experience but basically a failure. I think I allowed myself to be persuaded by my partners (against my instincts, but I probably wanted to agree with them) that kickstarter's ascendence didn't really change things for us that much and that we didn't need to completely rethink our plans and pivot before we'd launched. That's just one key point though, and I don't pretend it's the biggest or most significant mistake, just the earliest point when I think I knew in my gut things had changed and allowed myself to be talked out of it.