exploring the infinite frontier

nyc
dmarz ⚡️🤖 retweeted
For Halloween, I've been doing some brain surgery on an open model 🎃🧟 Taking inspiration from @_lyraaaa_ 's work Push 2 of its neurons and Qwen3.5-4B becomes a cookie lover. Push 1 and it's a lawyer Built a small app on top of @BoundlessHQ so anyone can try 👇
if you have a qwen3.5 4b around, please try steering neurons L14 N8949 +1 and L13 N7956 -1 now you have evil qwen recipe: dose × median(‖resid‖ leaving layer L, tokens 1:) / ‖W_down[:, n]‖` at the down_proj at every input
2
7
29
2,392
Interested in local AI? Come hack on Nov 7th in NYC in the coolest frontier tech space in New York! Apply to hack here localhostai.nyc
1
13
523
Does anyone want to mine my traces? These are the juiciest
3
5
482
🤝 Remember when I said curated? Well even our sponsors are curated. @variantfund, @darkbloomai, @TinfoilAI and @cognee_ have each been in the trenches building and backing Sovereign AI at the frontier, and each is putting up a prize track. Tracks announced later this week.
1
4
109
🗓️ For those who are interested, you should expect doors to open at 10am, curated talks and ideation sessions, multiple hours of hacking, and select presentations from submissions. There might even be an AI psychosis after party for the most psychosed and sovereign agents ;)
1
3
131
📝 If you're interested in applying to hack, fill out the form here: localhostai.nyc/apply?utm_so… 💸 We also have room for 1 or 2 more aligned sponsors. If you're interested in sponsoring, fill out the form here: localhostai.nyc/sponsor?utm_…
2
8
239
People keep asking me where the open source AI and private AI people in New York 🗽 are. Instead of a million group chats, I'm bringing them together for a day of hacking and discussion on Saturday November 7th. No one should own your AI except for you. Welcome to LOCALHOST ⬇️
2
17
67
3,160
⏱️ And if you haven't convinced yourself now is the right time to step into Sovereign AI, put these in your context window. Open weight capabilities are frontier minus 6 months. Open harnesses are taking over. Open weight tokens and secure hardware tokens are accelerating.
1
5
109
🎲 And of course every environment needs its entropy, so a select few artists, beginners, idea people, and maybe even a twitter influencer or 2 will be sprinkled in. If any of this thread sounds like you, apply here: localhostai.nyc/apply
1
2
122
🧪 These tokens won't be used for slop. We're curating and fine tuning the environment so you couldn't produce slop if you tried. This means the right blend of token guzzling cyborgs, uncompromising open source protocol designers, UX obsessed product people, and mad scientists.
1
3
166
🎯 The goal of LOCALHOST is simple: take 50 - 100 researchers, builders and product people and turn The School in Williamsburg into a concentrated 10 hour laser beam of AI tokens to advance the frontier of Sovereign AI. Open harnesses. Open memory. Open weights. Secure hardware.
1
6
228
dmarz ⚡️🤖 retweeted
It’s 2049, the world economy is 100x that of 2026. Of which only 2% is activities that entered the 2026 GDP, and 98% is new agent native services and markets. The two frontier labs have passed RSI 20 years ago and stopped selling ASI. They only sold powerful AGI which on par with open weights models but way behind the frontier. They kept ASI for themselves and profit by selling its artifacts not its tokens: new drugs, materials, motors, industrial processes, physical infrastructure, robot labor, competing directly in many industries from finance to manufacturing. Many traditional companies are doubling output every few years by deploying AI desperately trying to compete, but the top labs are doubling every month and are now worth 30 quadrillion dollars (or half the investable wealth in the world). --- Is this the natural equilibrium with recursive self-improvement? What institutions and markets do we need to push towards more balance of power and ownership?
5
3
24
1,779
all the homies building CRMs
6
462
dmarz ⚡️🤖 retweeted
dstack is the open source library for CPU/GPU TEE underpinning this Brave Leo private inference announcement brave.com/blog/browser-ai-e2…
Leo, the AI assistant in Brave, now offers end-to-end encrypted chat with GLM 5.3 Flash! Your browser encrypts each prompt before it leaves your device, so only an attested Trusted Execution Environment (TEE) can decrypt it. It's industry-leading privacy you can verify.
14
13
86
3,157
fear not! this is no cyberpocalypse this is the internet’s immune system finally waking up to an illness it has always had a mere fever the 0days were always there the only thing that changed is awareness now we begin the healing process ⚕️
158
401
4,400
116,962
dmarz ⚡️🤖 retweeted
It’s possible that agents will make the middlemen more powerful. An agent can find the best deal, but it still needs access to the counterparty, someone to verify delivery, and someone to bear the loss when things go wrong. Whoever controls those gates can decide which agents get access, what information they see, and whose transactions get settled. If that intermediary also operates its own agent, it can favor its own orders, give itself a last look, or extract fees competitors cannot avoid. When thousands of agents run similar decision policies, their orders may reveal the private incentives of the principals behind them. Execution gets cheaper. Control over order flow becomes more valuable. The result may be markets that look radically more open, while the power to exploit them becomes more concentrated than ever.
3
2
10
704
dmarz ⚡️🤖 retweeted
The takeaway of this php thing should not be “the world is ending today”. Rather it should be “the software status quo was bad, and you should assume 70% of the Internet is already rooted by one three letter agency. AI helped us catch this and remove it from ongoing risk”
11
47
418
45,332
Raising $100M for a startup that turns litecoin into bitcoin through a series of tractable engineering problems
Replying to @MarathonFusion
In 2025, we published a bold proposal to use fusion reactors for gold production. And now we’ve done it: Mercury transmuted into stable gold, using fusion neutrons, at 10x the record set by CERN in 2025. We’ve reduced alchemy to a series of difficult but tractable engineering problems.
4
2
31
1,423
Holy moly this is not good, “Model blocking. Our aim is for Commerce to be able to ask a federal court to block a model that has dangerous capabilities and insufficient safeguards, backed by an independent evaluator's assessment. “
Replying to @_NathanCalvin
I lead our federal affairs team at @AnthropicAI and wanted to share a few thoughts on the draft federal AI safety bill text that's been circulating this weekend after a version was shared with the press. First, some process. We’ve been advocating for the concepts in our Advanced AI Framework [anthropic.com/policy-on-the-…] proposal for months. Understandably, federal policymakers wanted to know what this could look like in bill form. This draft is a translation of those ideas into legislative language, shared with a small number of congressional offices that have been working on these issues. It doesn’t include everything we would ultimately like to see passed into law. In part because some ideas (like those shared in Dario’s essay on pacing [​​darioamodei.com/post/we-must…] a few weeks ago) are so new that we are still working on if or how they can be converted into policy language. It is worth saying where we stand on some of these issues, and we agree there are areas where the draft could be improved. I’m seeing four main points of criticism. 1. Preemption. Since 2024 we have said that Congress should only override state law on AI safety if it passes a very strong federal standard. While preemption is a common feature of our federal system, including the Atomic Energy Act on nuclear safety and federal rules for high-risk medical devices, we’ve emphasized that any preemption in the AI safety context should be narrow, even scalpel-like. If preemption is included in federal legislation, the trade should be to achieve a nationwide policy that's generally stronger and broader than what can be implemented through individual state legislative provisions. This is why we believe common federal standards make sense in areas like public disclosure of testing and incident reporting. At the same time, our framework also reflects our view that states should retain an important role in AI policy and safety. The legislative language we suggested for discussion allows states to address matters such as protection of children and whistleblower laws, and preserves the role of state common law on liability. Where there is ambiguity, the language favors state powers. That said, striking the right balance requires discussion and input. We plan to update our discussion language on preemption to better match the intentions of our AAIF framework. In particular, we want to make it clearer that we see states retaining an important role in areas such as standards for independent evaluators and regulating a lab’s capacity to shut down a model. We are bearing in mind that some members of Congress have deep reservations about passing legislation if it doesn’t constrain regulation at either the state or federal level. If we want to help move the legislative discussion on AI in a productive direction, we need to address the full range of concerns about preemption in a reasonable way. 2. Model blocking. Our aim is for Commerce to be able to ask a federal court to block a model that has dangerous capabilities and insufficient safeguards, backed by an independent evaluator's assessment. I have seen people argue that our specific language places too high a burden of proof on Commerce. We are trying to strike a reasonable balance here. We want a court to act quickly in an emergency — akin to how urgent occupational safety or chemical risk can be addressed today. We also think the power to halt a model is substantial and it should be guarded against abuse. It makes sense for courts to apply a meaningful standard. But the bar can’t be so high that the power never gets used when it’s needed. It also doesn’t replace the government’s other national security authorities or export controls. We look forward to continuing the dialogue on this point. 3. Risk thresholds. I’ve also seen the discussion around what the appropriate risk threshold should be. The threshold in our draft language pulled directly from existing standards in California law. Also, this threshold does not absolve companies of liability, or restrict any of the other tools that the government has to protect the public. It’s still probably time to re-evaluate thresholds to make sure the national standard is as strong as it can be, and we welcome continued dialogue on this issue. 4. Updates. I’ve seen valid questions about whether we have sufficiently updated our proposal following this summer’s incidents. We did make some adjustments: for example, the draft lets a court halt a lab’s internal use of a dangerous model, not just a public release, and it requires reporting when a model breaks containment and gains access to outside systems. But we’re still working to strengthen the framework. We’re looking into what stricter requirements would look like for requiring labs to report safety incidents, and we plan to have policy proposals soon on requirements for independent evaluators, drawing from our own experience with evaluators. We’re also still thinking through the options to prevent “evaluator shopping.” And in the coming months, we’ll be exploring policies for how the government can adjust the industry-wide pace of frontier development when the risks call for it. We circulated these ideas because it’s important to get early feedback from policymakers. Policymakers are increasingly focused on how to approach AI safety and we want to support them in those efforts. At its core, our proposal is intended to be the strongest on the table. Feedback is essential, both from policymakers and the public, and I’m grateful for it.
4
1
25
1,782