Show HN: Performative-UI – A react component library of design tropes

Anti-social: It's fads, not friends, which now dominate social media feeds

MiMo-v2.5-Pro-UltraSpeed: 1T model with 1000 tokens per second

Surveillance is not safety: A statement on the UK's latest threat to privacy [pdf]

Siri AI

AI is slowing down

xAI is looking more like a datacentre REIT than a frontier lab

Apple reveals new AI architecture built around Google Gemini models

Confidential submission of draft S-1 to the SEC

Massachusetts bans sale of precise location data in new privacy rights bill

EU-banned pesticides found in rice, tea and spices

Apple Core AI Framework

1worldflag: A blue dot on a transparent background

What works now: user signups, org creations, private&#x2F;public repos, and importing GitHub repositories (both as read-only mirrors and full migrations). So basically, you can create, push and pull to a repo, but we don&#x27;t have many features quite yet (issues, PRs, CI).What is a bit unique is: 1) we built it in Rust and 2) the website is a little odd. Its design is inspired by CLIs (e.g., fzf, broot, vim) instead of web apps, and as such, lacks some affordances that you might typically expect in favor of keyboard-driven instant navigations (we have the very ambitious goal of an FCP of 100ms). In case you&#x27;re curious, here&#x27;s how we we built it: <a href="https:&#x2F;&#x2F;gitdot.io&#x2F;designs">https:&#x2F;&#x2F;gitdot.io&#x2F;designs</a>We recognize that we&#x27;re making some bold claims here and are also well aware that we have much to learn. Building software is still hard, and that&#x27;s a fact we seem to relearn everyday.But we wanted to share what we built so far nonetheless.Cheers, thank y&#x27;all for reading, and till the next
—paul &amp; mikkel.

Show HN: Gitdot – a better GitHub. Open-source, written in Rust

Ask HN: What are tools you have made for yourself since the advent of AI?

OCaml Onboarding: Introduction to the Dune build system

Why are cells small?

FrontierCode

Hey HN, we&#x27;re Faisal and Ahmad from Intuned (<a href="https:&#x2F;&#x2F;intunedhq.com">https:&#x2F;&#x2F;intunedhq.com</a>). We’re building a platform for building, deploying, and maintaining browser automations.Customers primarily use the Intuned AI agent to automate websites that don&#x27;t expose APIs. Common use-cases include scraping data, pulling reports, and submitting forms. As the website changes, our agent also helps automatically heal the automation.On Intuned, browser automations are created by an AI agent and run as code. Our infra captures the context of every run, allowing our agent to debug and maintain the underlying code - to keep the automations working over time. This way, we’re able to offer the predictability, speed, and cost of code, without the painful parts of writing and maintaining it.Here’s a demo of building a scraper on Intuned: <a href="https:&#x2F;&#x2F;youtu.be&#x2F;ruZP73bK4FU" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;ruZP73bK4FU</a>Here’s a demo of using AI to maintain a project: <a href="https:&#x2F;&#x2F;youtu.be&#x2F;e4R4hLdHBro" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;e4R4hLdHBro</a>Backstory: we were accepted into YC for a completely different idea. During the batch, because of Faisal&#x27;s background at UiPath, several batchmates asked us whether RPA tools could fill API gaps in their products by automating websites without APIs. When it was time to pivot, we went back to those founders to dig deeper. (RPA in this context is referring to using UI automation to do complete non-testing tasks)We discovered that the actual hard problem in browser automation is maintenance. Websites change, selectors break, and failures can be painful to reproduce and fix. So in early 2024, we decided to take a crack at this problem with a handful of customers. It needed a fair number of iterations before we landed on our current code-first approach.How it works: Intuned is infra + agent, deeply integrated.On the infrastructure side, Intuned is a managed runtime for browser automation code. Projects are usually Playwright-based TypeScript or Python. Users can write them directly in our online IDE, or hand the work off to the agent. Either way, once deployed, the platform runs each project in its own isolated machine and handles auth&#x2F;session reuse, scheduling, batch execution, concurrency, observability, and the other plumbing around running browser code.On the agent side, it took us a few iterations to get to the current approach. Our initial attempts were rigid pipelines: collect requirements, inspect the site, generate code, then try to patch whatever broke. It looked reasonable on paper, but real websites are too messy for fixed paths. Late last year, we were planning to ship that version when stronger models landed and harnesses like Claude Code and Codex showed what a more open-ended coding agent could do. We built a prototype on the Claude Agent SDK, it felt much better than what we had, and we scrapped the release and decided to rebuild the agent.The rebuild came down to three pieces around the SDK: an execution environment for running long agent sessions reliably, a CLI that exposes the platform to the agent so it operates Intuned the way engineers do, and a custom plugin (skills + MCP) built around what we&#x27;ve learned building browser automations.The infra-agent integration is where the product gets more interesting. The runtime doesn&#x27;t just run the automation; it captures the context needed to debug it when it fails: params, results, traces, logs. That enables features like Fix with AI, where you can open a failed run and have the agent investigate and prepare a fix.The same integration powers a feature called self-healing. For configured projects, the platform detects failures, starts an agent session with the relevant context, and either proposes a fix for review or deploys it automatically. Demo: <a href="https:&#x2F;&#x2F;youtu.be&#x2F;IVHIXw0lYMs" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;IVHIXw0lYMs</a>We recently also packaged the infra and agent as an API called Web Task API, here is a demo: <a href="https:&#x2F;&#x2F;youtu.be&#x2F;1olRn3l95vw" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;1olRn3l95vw</a>We strongly believe that browser automations can and should be faster, cheaper and more predictable. Check us out at <a href="https:&#x2F;&#x2F;app.intuned.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;app.intuned.io&#x2F;</a>, we have a free tier with trial credits for your first few automations. Excited to hear your thoughts, questions, and feedback!

Launch HN: Intuned (YC S22) – Build and run reliable browser automations as code

It feels like every event&#x2F;venue is selling tickets exclusively through Ticketmaster.  Every other ticketing platform seems to only hold resale tickets in their inventory which just transfers the tickets to your Ticketmaster account when bought. With all the hate Ticketmaster has gotten and all the other ticketing platforms out there, I&#x27;m surprised Ticketmaster still has a hold of pretty much the entire market. How are they doing this? Why haven&#x27;t the other platforms been able to compete?

Ask HN: Why hasn't there been a real competitor to Ticketmaster yet?