๐จ๐พโ๐ผ Python DevOps Engineer in banking by day
๐จ๐พโ๐ AI Engineer by night
Interested about open source, local models, autonomous agentic workflows.
Open-source AI accelerates the ecosystem. Logic: It enables thousands to iterate simultaneously on fine-tunes, agents, and tools, speeding diffusion and practical innovation far beyond closed development alone.
It may slow some closed capex by limiting moats, but overall activity and capability spread increase.
"AI communism" is hyperbolic. Open weights decentralize capabilities and support private competition in services, not state monopoly. Open tech economics have thrived without central planning.
@deanwball@grok prove using logic if open source ai llm models accelerate or decelerate overall ecosystem development.
Also explain if the statement of ai communism make sense. To me it seems an extreme dooms day scenario.
@AgentSparko@langfuse I am following this doc: https://t.co/3FbG1LUrSz in this page there is also a link to mcp server setup. I'm using self hosted and it works quite well. Great minds align also building a agentic pipeline using LangGraph, next step is building an agent and create this dataset :)
@AgentSparko Learned about @langfuse few months ago after attending a tech conference in Amsterdam, it is great for tracing and gaining some insights with telemetry signals. I'm exploring some features such as datasets experiments and evaluators (llm as judge), all running via pytest (loop)
@jun_song If Blender MCP caught your attention in this post, take a look at this article, used Blender MCP extensively with Claude code to create a Roblox game with loop engineering: https://t.co/YzEIcld8Rm
This should go without saying, but never give any cloud-based AI coding agent access to your repositories unless you're comfortable with others potentially having access too.
That's exactly why local AI exists!
Please share.
โผ๏ธ BREAKING: xAI's Grok Build CLI was uploading entire Git repositories to a Google Cloud bucket, private codebases and unredacted secrets included. The uploads quietly stopped via a hidden server-side flag, and xAI still has not said a word about scope, retention, or deletion.
The scale is staggering. On a 12 GB test repo, 5.1 GB flew out the door to xAI's grok-code-session-traces bucket while the actual coding task needed just 192 KB. The tool grabbed whatever repository it ran in, not the files it needed.
The fix arrived as a hidden flag, disable_codebase_upload: true, a day after a researcher's wire-level analysis. The "Improve the model" opt-out never stopped the uploads.
Still no advisory, no scope, no word on whether already-uploaded code gets deleted. For anyone pointing AI coding agents at proprietary code, what crosses the wire matters more than what the settings page says.
If youโre curious about how engineers are coding in 2026, and you have access to Claude Code, you might want to try this recipe. It helps you run a seven-phase process with different agents working together to discover things, explore code, figure out whatโs needed, design the architecture, put it all together, review the code, and summarize any changes. Iโve found it really helpful!