> Kirsten: All of this, to me, illustrates how quickly things are moving. I mean, when you really think about it, the whole tokenmaxxxing thing has become a thing, peaked, and now is seen disfavorably, within six months
Pretty sure from inception the phrase “tokenmaxxing” was never seen in a positive light…
Article and this post seems to be AI generated… but this is a good quote
> AI coding assistants hallucinate package names. They confidently suggest npm install some-plausible-sounding-package for packages that do not exist. Attackers monitor those hallucinations and register the names - a technique now called slopsquatting
I started believing at 4 years old when going to a christian school, then stopped believing a few years later when I realised I couldn’t see any proof of any god watching, planning or influencing the world in any way at all…
> I’m a new solo dev with almost no audience. If a large org or a well-known developer sees the idea and ships a similar implementation, they can get more attention immediately than I can get in months. And in the end I get nothing for open-sourcing my project.
This has always been a fear of open source development… but in reality it’s over exaggerated, thousands of FOSS ideas are posted every day…
My advice would be to treat posting your project like a launch, and get all the readme’s, docs etc ready before posting, so it has the best chance of growing an audience, which seems to be your goal.
But if you really don’t want other people to recycle your idea, then open source is not for you…
I don’t think they “got lucky”. nextjs is an old project now, and for a long time it was the simplest framework to run a React website.
This is why most open source landing pages used nextjs, and if most FOSS landing pages use it, then most LLM’s have been trained on it, which means LLM’s are more familiar with that framework and choose it
There must be a term for this kind of LLM driven adoption flywheel…
> For instance it does not make sense to have an MCP to use git.
What if you don’t want the AI to have any write access for a tool? I think the ability to choose what parts of the tool you expose is the biggest benefit of MCP.
As opposed to a READ_ONLY_TOOL_SKILL.md that states “it’s important that you must not use any edit API’s…”
Well yeah, business has literally always extracted value from open source software, that’s one of the main benefits of it… (although license violations have been unprecedented with AI)
“Creating value” in open source has never been about capturing value at all, it’s always been about volunteering and giving back, and recognising the unfathomable amount of open-source software that runs the modern world we live in
“Capturing value” is the opposite of this, wall-gardens, proprietary API’s, vendor lock-in, closed-source code… it’s almost antithetical to the idea of open source
https://github.com/benwinding
https://benwinding.com
[ my public key: https://keybase.io/benwinding; my proof: https://keybase.io/benwinding/sigs/bVV_JyagfOPTVOiqOf50YZB4rhM0EIDgUvumlGAA6mY ]