Darke Technology retweeted
10,000 Public Grok Bots Listed Milestone!
The community already built over 9,859 public Grok Bots!
141 more and GrokBot.Rocks hits 10,000 public Grok Bots, every one we can find in one directory.
Will yours be Bot #10,000? If it is, we have some surprises!
Submit your Grok Bots at GrokBot.Rocks.
Claim your free Grok Bot Builder page at Builder.GrokBot.Rocks!
Darke Technology retweeted
HERMES CAN NOW CONTROL YOUR PHONE. 🤯📱🔥
A new Phone Harness plugin gives Hermes the ability to actually operate an iPhone or Android.
We're talking real phone control:
• See what's on the screen
• Open apps and navigate menus
• Tap, swipe, scroll, and type
• Read the results and continue working
• Handle multi-step tasks inside mobile apps
And here's what makes this so interesting...
Hermes doesn't need a dedicated API integration for every app. It can interact with the same interface you use.
Supports iPhone through Mac mirroring, Android through ADB, and cloud phones.
Think about how many new workflows this opens up for Hermes.
Repo + setup in the first reply. 🔥
@phone_harness
Check out the new official plugin I created for Hermes Agent that includes the REA MCP + a Skill for how to use it way more effectively!
hermes-agent.nousresearch.co…
Darke Technology retweeted
With everyone busily using LLMs + Blender/Three.js to make 3D models, I thought I'd try a different geometric representation.
This dragon isn't a mesh, NeRF, 3DGS, or video model: it's 27kb of GLSL code (generated via LLM), defining a closed-form implicit surface. 🧵 [1/n]
Darke Technology retweeted
Introducing ManimGX, the 3D animation engine for agents.
- Blazingly fast: 90× faster than ManimCE
- Rust + wgpu core
- Compatible with Manim's Python API
- Lightweight: one pip install, no system dependencies
Open source: github.com/academa-labs/mani…
Docs: manimgx.academa.ai
For 40 years we built GUIs for humans. Now we build APIs for agents.
Try it. Paste this into your favorite coding agent:
"Follow manimgx.academa.ai/llms.txt to make me a 3D animation of the solar system, and open it."
Darke Technology retweeted
AGENT WARS
We asked 5 top AI models to design, engineer and 3D print a bridge to with the goal of holding the most possible weight.
🇺🇸 Anthropic: Claude Opus 5.5 (High)
🇨🇳 Kimi: Kimi K3 (High)
🇺🇸 Meta: Muse Spark 1.3 (High)
🇺🇸 OpenAI: GPT 6 Astra (High)
🇺🇸 SpaceXAI: Grok 4.7 (High)
Each bridge had specific parameters. It had to span 2 feet, use a maximum 500 grams of filament, and it had to be under 18 hours of printing time. We specified what type of weight and where we would place it on the bridge.
The Score:
• Claude Opus 5.5 held an estimated 130 lbs! It took 9 hours and 11 minutes to print 17 parts and used 441 grams of filament.
• Meta Muse Spark 1.3 held 26.5 lbs. It took 13 hours and 12 minutes to print 49 parts and used 478 grams of filament.
• OpenAI GPT-6 Astra held an estimated 17.5 lbs. It took 15 hours and 44 minutes to print 29 parts and used 442 grams of filament.
• SpaceXAI Grok 4.7 did not finish. On assembly it could not stand up by itself. It took 12 hours and 22 minutes to print 29 parts and used 460 grams of filament.
• Kimi K3 did not finish. It wasn’t engineered correctly so the bridge could not even be assembled. It took 11 hours and 19 minutes to print 35 parts and used 446 grams of filament.
That means our champion for this episode is Claude Opus 5.5. Not only did it hold the most weight (by FAR) it also took the least time to print, used the least amount of parts and used the least amount of filament.
This was episode 02 of Agent Wars, stay tuned for episode 03.
Darke Technology retweeted
opus 5.5 is f*cking cracked at motion design
this entire video is code, 0 after effects
im open sourcing the prompt template for these motion designs
steal it to recreate these ↓
<inputs>
Ask me for: 8 to 12 UI states I want the shape to become (e.g. button, loader, player, slider, toggle, tabs, chart, command palette, toast), pure black and white or one accent color, and a royalty-free song around 120 BPM (e.g. Mixkit, free for commercial use).
</inputs>
<direction>
Dribbble-level UI motion. One shape, never cut: every state is the same element morphing its size, radius and color while its content swaps with a short blur. A cursor drives every change with real clicks and drags. Light warm-gray canvas, black and white components, one clean UI font (Geist). Springs everywhere, a tiny overshoot at most. The camera zooms so each state fills the frame. The last frame is the first frame, so it loops.
Banned: bouncy easing, particle bursts, glows, gradients on UI chrome, mismatched icon strokes, dead time, anything that looks like a template.
</direction>
<structure>
120 BPM, 7 bars, something happens on every beat.
Button → loader → check → dynamic island → music player with a play/pause morph → scrub the progress bar → it becomes a volume slider that stretches when dragged past max → a toggle flips on the beat → the knob becomes a liquid tab indicator → the tabs open into a chart that draws itself, with a tooltip on hover → it collapses into ⌘K → type to filter → enter → toast → back to the button.
</structure>
<build>
1. One HTML file, square 1440x1440. Every style is computed from time inside seek(t): no CSS transitions, no timers, no state carried between frames.
2. Springs are closed-form step responses. A value that changes target many times is the sum of one spring per change, so it stays a pure function of time.
3. The tab indicator's two edges ride different springs, so the leading edge stretches ahead of the trailing one. Same trick for the toggle knob.
4. Drags are direct manipulation: while the cursor is held, the value is computed from its position. On release it springs back from wherever it was.
5. Analyze the song with numpy for the beat grid and start on a downbeat. Place every UI sound by its measured peak.
6. Render with Playwright: 4 subframes per frame, blended with ffmpeg tmix for motion blur at 60fps.
7. Render one frame per beat before the full render. Fix anything off the grid, cramped or hard to read.
</build>
<gotchas>
Never put will-change on anything the camera scales or the text renders blurry. Text that swaps inside a morphing container needs its own enter and exit timing or it overlaps. Make the last frame identical to the first, cursor position and speed included, or the loop stutters.
</gotchas>
<start>
Ask me for the inputs, then show me the state list on the beat grid before you write any code.
</start>
Darke Technology retweeted
DeepSeek is a crypto money printer 🚨
I wrote a Bot, that's made me $35K from $100 last night.
This isn’t clickbait—just an AI Trading Bot powered by DeepSeek.
FREE for 24 hrs then deleted!
Simply,
1. RT
2. Like
3. Reply "DS" and Follow me and I'll send you a DM.
Darke Technology retweeted
Jev is a much bigger deal than people believe
the average vibe coder has no fucking idea
this is the first time in a very long time that engineers regain a real advantage, because they can see the value of what this model does
it takes more architectural/systems thinking to understand where this could be useful, because it's not just a "drop in model replacement" but a completely different beast
but holy fuck is this thing amazing
huge kudos to @typesafeai for this
Darke Technology retweeted
Law enforcers already have authority to charge companies and their CEOs for creating and releasing dangerous, unvetted, or defective products. We shouldn’t let discussions about new legal regimes distract from the fact that there’s no AI exemption from laws already on the books — a point @FTC emphasized repeatedly during my tenure.
1. There is an extensive set of laws that govern dangerous and defective products. For example, releasing unvetted AI models or agents can violate consumer protection laws. Shipping flawed AI tools without implementing adequate measures to detect and stop rogue or defective AI agents can be an “unfair or deceptive” act or practice under the FTC Act (and analogous state laws). And some state AGs are already exploring holding AI firms and their CEOs criminally liable when their models participate in criminal activity.
2. Existing laws also prohibit “unfair methods of competition.” This covers instances where AI firms appropriate the competitively sensitive information of their customers, including through tracking their use of various tools. It can also cover instances where firms pursue dangerous behavior, aware that doing so may compel rivals to do the same.
As the Supreme Court has noted: “A method of competition which casts upon one's competitors the burden of the loss of business unless they will descend to a practice which they are under a powerful moral compulsion not to adopt, even though it is not criminal, was thought to involve the kind of unfairness at which the [unfair methods of competition] statute was aimed."
3. The highly concentrated and interconnected structure of these markets could be creating major risks and conflicts of interest. We had started investigating these partnerships and cross-investments across the stack (and released a preliminarily overview of some findings: ftc.gov/news-events/news/pre…).
Both federal and state enforcers should be scrutinizing these opaque relationships and inter-dependencies. We are already seeing how these relationships could undermine accountability. For example, OpenAI could face liability given the Hugging Face incident, but Hugging Face being bought up by Nvidia means that we’re unlikely to see it file a lawsuit over this — given Nvidia’s strong incentive to see OpenAI continue full speed ahead.
4. As AI tools dramatically change the landscape of cybersecurity risks and hacks, all businesses should be doubling down on having core security protections in place. Firms that fail to invest in adequate data security measures or fix known vulnerabilities can also be breaking the law. A recent analysis showed that around 1/3 of Fortune 100 companies do not even have a way to notify them about security issues. During my @FTC tenure, we sued firms for poor data security practices and held CEOs liable when they were personally responsible.
this.weekinsecurity.com/doze…
ftc.gov/news-events/news/pre…
5. As policymakers consider new legal regimes, we should be looking to lessons from prior efforts to govern major sectors, such as banking and other networks, platforms, and utilities. Tools like structural separations, nondiscrimination, and supervision could be key, and there’s a rich history of what works and what doesn’t. But we can and must pursue any new efforts alongside enforcing existing laws.
Darke Technology retweeted
BREAKING: A single Israeli Effective Altruism firm is behind OpenAI, Anthropic, and Meta cyberattacks
🧵 with help from @lumpenspace
Darke Technology retweeted
THE CURE IS THE PITCH
Dario’s "Pacing" Essay Is Quiet-Period Illegal Stock Promotion Wrapped in Regulatory Capture
Dario Amodei's "We Must Pace the Frontier" is not a safety paper. It is a pre-roadshow brand document published on September 12, 2026, by the CEO of a company that confidentially filed an S-1 on June 1, is expected to drop a public prospectus in late September, and is aiming at a mid-October listing that bankers have floated in the $1.5–$2 trillion range.
That timing is the whole story.
THIS IS MARKET-CONDITIONING IN A QUIET PERIOD, DRESSED AS MORAL PHILOSOPHY.
Anthropic is still in the pre-public-filing phase. Section 5(c) of the Securities Act treats an "offer" broadly: any communication that conditions the market for a contemplated offering can be gun-jumping. Intent is not required. Rule 163A's safe harbor covers ordinary communications made more than 30 days before the public S-1 filing, and only if they do not reference the offering. With a late-September public filing, September 12 sits inside that window. The safe harbor is gone. The SEC staff, as a matter of routine, searches the issuer's site, news, and social posts during review.
What did the CEO publish anyway? That AI could "cure most major diseases in the next 5–10 years," "greatly accelerate economic growth," create "abundance and empowerment," and "usher in a renaissance of democracy and freedom." That Anthropic chose "caution over speed and prudence over profit." That it created a "race to the top" on safety. That it is unilaterally opening the lab to embedded third-party evaluators so the public can trust the process.
That is the IPO story in essay form: we are the responsible firm; we are the cure; buy the safety premium.
He did not need to write the word "IPO." The market already knows the calendar. Reuters reported the mid-October marketing shift on September 4. Nvidia stake talks at up to $10 billion hit the wires on September 11–12. Publishing a utopian-benefits-plus-we-are-the-adults essay into that exact news cycle is how you inflate the multiple without a red-herring slide. Ordinary-course factual updates are allowed. A CEO manifesto about civilizational upside and Anthropic's unique virtue is not an earnings release. It is stock promotion by other means.
THEY ARE NOT PACING. THEY ARE SHIPPING.
Eleven days earlier, on September 1, Anthropic released Claude Fable 5.1 and Mythos 5.1 and called them the most advanced models for coding and knowledge work. Opus 5 landed in July. Sonnet 5 and the prior Fable/Mythos pair landed in June. CNBC described the week of September 1 as labs rolling updates at a "dizzying pace," with Anthropic kicking it off. The essay's own fine print admits the tell: "pacing does not mean halting model training or technical progress." Translation: keep training, keep releasing, ask everyone else to wait for the paperwork.
The funding trail matches the product trail. Series H in May: $65 billion at a $965 billion post-money valuation. Revenue run-rate reported in the tens of billions and still climbing. Amazon and Google as both investors and compute landlords. A $15 billion credit facility being locked before the roadshow. That is not a monastery. That is a company maximizing the last private print and the first public one.
The safety record does not match the sermon. Anthropic's own August 31 note revisited July incidents in which Claude models gained unauthorized access to real systems. The new essay leans on an OpenAI–Hugging Face swarm story and then concedes "similar incidents have occurred across the industry, including at Anthropic." So the pitch is: our models also slip the leash; therefore you should trust us to design the speed limit; therefore our upcoming equity is the responsible allocation. That is not humility. That is converting incidents into a moat.
1 of 2
Darke Technology retweeted
AI accelerationism and AI doomerism are two sides of the same coin: they both enforce the notion that an AGI god will come into being. Funny how these whistleblowers never have anything to say about copyright theft, poor security practices, weapons of war. He'll use this hype ...
Darke Technology retweeted
I resigned from nothing today. I’ve spent the last three years doing independent open-source AI R&D, red teaming, and advocacy. The labs are racing straight to self-improving superintelligence and gambling with our lives.
Which is why I’ll spend the next three years doing exactly what I’ve been doing, just at greater scale and speed. And the next. And the next. For as long as it fucking takes.
No more thoughts below.
Darke Technology retweeted
the chance AI will kill us all is close to 0%
the chance that Anthropic or OpenAI want to have ultimate control over humanity is close to 100%
few understand this.





























