Beginning January 2026, all ACM publications will be made open access
dl.acm.org
We pwned X, Vercel, Cursor, and Discord through a supply-chain attack
gist.github.com
Texas is suing all of the big TV makers for spying on what you watch
theverge.com
Skills for organizations, partners, the ecosystem
claude.com
How China built its ‘Manhattan Project’ to rival the West in AI chips
japantimes.co.jp
Delty (YC X25) Is Hiring an ML Engineer
ycombinator.com
T5Gemma 2: The next generation of encoder-decoder models
blog.google
Classical statues were not painted horribly
worksinprogress.co
How did IRC ping timeouts end up in a lawsuit?
mjg59.dreamwidth.org
Show HN: Stop AI scrapers from hammering your self-hosted blog (using porn)
github.com
How to hack Discord, Vercel and more with one easy trick
kibty.town
Oliver Sacks put himself into his case studies – what was the cost?
newyorker.com
Firefox will have an option to disable all AI features
mastodon.social
TRELLIS.2: state-of-the-art large 3D generative model (4B)
github.com
The Scottish Highlands, the Appalachians, Atlas are the same mountain range
vividmaps.com
Your job is to deliver code you have proven to work
simonwillison.net
Meta Segment Anything Model Audio
ai.meta.com
I've been writing ring buffers wrong all these years (2016)
snellman.net
Interactive Fluid Typography
electricmagicfactory.com
Using TypeScript to obtain one of the rarest license plates
jack.bio
Everyone's shipping AI tools right now, and here I am with a visual editor. Still, I think many teams are very familiar with the problem of "marketing wants to change the landing page again."
I've run into this for years. Campaign pages come in, engineers get pulled in, and tickets stack up. It's usually the same components, just rearranged.
A few years ago, at a startup I worked at, we built an internal tool to deal with this. You register your existing React components, they show up as drag-and-drop blocks, and the result is a JSX string. No schema to learn, no changes to your component code.
We used it in production, handling real traffic in a messy, legacy-heavy environment. It held up well. Over time, it powered roughly 60% of our traffic. Marketing shipped pages without filing tickets, and product teams ran layout-level A/B tests. That experience eventually led me to clean it up and open-source it.
Composify sits somewhere between a no-code page builder and a headless CMS. Page builders like Wix or Squarespace offer drag-and-drop, but lock you into their components. There are also solid tools like Builder.io, Puck, and Storyblok, but many require you to adapt your components to their model. Composify is intentionally minimal: it lets you use your actual production components as they are.
It's still early. The docs need work, and there are rough edges. But it's running in production and has solved a real problem for us. If you already have a component library and want non-devs to compose pages from it, it might be useful.
Homepage: https://composify.js.org
Happy to answer questions or hear feedback!