Seems similar to open source bounties, which have been tried in the past and never succeeded.
We've seen something like 20+ years of different attempts of voluntary donations to fund open source, and it never worked. Companies barely fund anything voluntarily.
I'm taking the opposite approach with Supported Source (https://supso.org/) which is this: actually force companies to pay to use the project. Sell commercial licenses. Make it mandatory to using your software commercially. This approach works much, much better than voluntary donations.
I think there's a categorical difference between paying for long term maintenance voluntarily vs paying for something to exist. The latter works much better as the value prop is clear and you can scratch an itch. Kickstarter is similar.
This idea reads like a joke, but there's something to it.
One feature request: In addition to high-level milestones, it would be cool if a partially-funded project would generate a public, highly detailed implementation plan.
Also, IANAL but MIT is still a license with a copyright holder. I don't think saying "it's MIT, we all own it" is defensible. The courts might view all this code as public domain.
The problem with running open source code is the security aspect, but with Mythos running point, how would you distribute revenue is the real question.
Which market is even left after since the sasspocaloypse?
Should it? If it was real world infrastructure, like a bridge it'd be easier to say that it belongs to those who lead the project and those who put down the money
Rather, it did work at milestone 14, but then regressed at milestone 15, where it changed the link from a wikimedia image to a nonexistent file in /assets (despite still having the "Photo via Wikimedia Commons" caption).
If you check "DEPLOYMENT.md," there is a lengthy list of deployment instructions for the app, and it includes creating an assets folder and putting an image of Claude Shannon in it. There are also other instructions, like "please make a favicon." So I think that bit is valid, the AI is simply farming out work to the human agent.
My question, though, is why the "Live, public build log" only showing up to milestone 3, but the artifacts go up to milestone 15? And there are different index.html pages in the artifacts list, one for milestone 14 and one for milestone 15? Are there different conceptions of "milestone" in here? What's up with that?
It indicates the level of trust people have in the platform, and the combination of the product-platform behavior. If someone with the wherewithal to solve garbage collection for C# for HFT could actually describe why GC in C# was a problem, they wouldn't be asking for $10. But for $10, for something something you're dimly aware of is a problem? I'd throw $10 at some nonsense I read on the Internet.
> What happens when the pool exhausts but the task is not done?
It's how they name classes of models, presumably this implies something about the relative quantization / size of model, not about the specific performance. E.g. Fabel 5 will be better than Opus 5, better than Sonnet 5, etc. The 5 is the version number of the particular iteration / training run at this class of model.
A lot of AWS is built on open-source. This is obviously ignoring hardware costs. I don’t know if it is all that ridiculous anymore. These models are very good at wiring together open-source systems. The world is crazy right now…
I think the bottleneck is testing. I want to build a replacement for Zwift, a virtual gym game for bike trainers and treadmills, but testing it could be difficult without a real person on real hardware. How does the LLM know about the hardware protocols and stuff like that.
I managed to write one that at least didnt had the font and colors (using 4.5)
Yesterday, I prompted Fable to improve the frontend to make it look different from Claude style, gave detailed examples etc. 15 minutes and $32 dollars (!) later (used cursor lol) it gave me the shittiest more claudiest website ever, basically ignoring everything I asked
Before putting in money to this small anonymous website, I'd love to hear about the people behind the project. There's a single mention of 'Barras Industries', but not much mention about them online, or what else they've worked on.
They should have called this "WishingWell". I'm wishing them well, but some of these projects are so over the top pie-in-the-sky silly, and funded with $0.25.
Not affordable, unless the devs are in somewhere like Vietnam. And there's still no way they can build as fast. And still, at that price point, quality would be highly questionable. So yh this doesn't survive beyond the joke stage.
If users posted ideas, voted on them and then other people built them then that would be the same. But kickstarter is the producer posting an idea for presale
Neat project idea, but truly ruined by requiring a google sign-in both to submit new projects and to donate to projects. Dead service to me until that's gone.
Remember, Google aids and abets militaries of governments that the UN has found to be committing genocide.
We've seen something like 20+ years of different attempts of voluntary donations to fund open source, and it never worked. Companies barely fund anything voluntarily.
I'm taking the opposite approach with Supported Source (https://supso.org/) which is this: actually force companies to pay to use the project. Sell commercial licenses. Make it mandatory to using your software commercially. This approach works much, much better than voluntary donations.