Lightweight and powerful code editor, available for Windows, Linux and macOS.

Discover the world of isomorphic keyboards and learn more about the story of the Janko Project!

At a time when concerns about inequality are high and public attitudes toward the ultra-wealthy have soured, Musk has managed to retain a loyal following.

This week, we launched the Field Guide to Grid Lanes at gridlanes.webkit.org.

(FWIW to you, dear reader, I did not use AI when writing this article) AI cannot desire. It can plan, and it can execute, but it cannot desire. If you desire X, you can use AI to come up with a plan to get X, and depending on the task, AI can execute parts or even all of the plan. But AI cannot want X. AI can plan an app and can build one, but it cannot want the app to be user-friendly/fast/follow a certain aesthetic/etc. You can want it to be all of those things, and if you do, you must tell it to plan for those things, because it cannot want to achieve them itself. What am I getting at here? AI is getting very good. I ask myself: What is becoming less valuable because AI can do it better/faster/cheaper than humans, and more importantly, what can't it do better/faster/cheaper than humans? I think the answer is desire. AI cannot desire. Some people have said that taste is what we bring to the table. I don't think that's wrong, I just think it's a downstream effect of desire. One has taste because they know what to look for, they have values, and they desire that the thing they're evaluating has lives up to those values. You get out what you put in. If you don't tell AI what to do, it will not think of it for you. It's not like asking a human to build or write something, because a human has its own goals, motivations, values, experiences, and ends. Get good at communicating your desires in writing. Cultivate your values. Learn to express them. It is one thing to have taste and values, it is another to be able to be able to express them in words. Criticism is valuable.

Three kinds of work, three success criteria, and why confusing them is costly. Early in my career I worked at Bell Labs, where one could work on any intellectually challenging problem, whether or n…

University of Nottingham is first of many, Shiny tells The Reg

This video demonstrates the general concept that makes a differential wrist joint work. Both motors working together achieve two degrees of freedom. submitted by /u/Icy_Hat_7473 [link] [Kommentare]

One app. No data centers. Every claim it makes, signed. Open-source ethical AI you can run on your phone today — and check.

A five-year scenario about AI and Europe's impending slide into irrelevance, with a 2034 epilogue that describes how the collapse of the European model could have been prevented.

Critics say the systems we use to educate the brightest kids are flawed and exclusionary. What if it’s the very premise of giftedness that’s faulty?

Obsidian Security found three chained LiteLLM CVEs that let a default low-privilege user reach admin access and RCE (CVSS 9.9). We also demonstrate how a compromised gateway can inject arbitrary tool calls to further compromise downstream agents like Claude Code. Full breakdown and the fixes.

Is the Trump phone actually made in America? Our deep-dive teardown reveals the Trump Mobile T1 is basically a gold-painted, rebranded HTC U24 Pro.

Published Jun 11, 2026 Launching supso: the CLI for paid licensing with Supported Source A command-line tool for paid licensing, so project owners get paid Today we're introducing supso, the official command-line tool for Supported Source. Supported Source helps maintainers get paid, by selling paid licenses to their projects. But how will companies certify they bought a license? The answer is supso: companies can use supso to sync their license certificates from our website to their local file system. You can find it on GitHub at github.com/SupsoOrg/supso. What supso does Supported Source projects are commercial open source: hobbyists and evaluators can use them for free, but companies pay for a license. A license is just a certificate that cryptographically proves your organization is allowed to use a given project. supso is the tool that manages those certificates on disk and verifies them, so your projects work and your builds stay green. The mental model is simple: certs is what you have installed, projects is what you're licensed for, and verify is the scriptable yes/no gate you can drop into CI or a build script. Getting started supso ships as a single static binary, so installing it is a one-liner whichever way you prefer: brew install SupsoOrg/tap/supso # Homebrew cargo install supso # or from crates.io Once it's installed, sign in and pull your certificates down: supso login # sign in via the browser supso sync # pull your licensed certificates into ~/.supso supso certs # see what's installed After that, your licensed projects just work. You can also use supso verify to double check that the certs you've synced are verifying. Built for deploys Verification happens offline at runtime. When you ship a service that embeds a Supported Source project, the supso-project library checks the license certificate locally. There's no network call or login flow in production. You provision the certificate the same way you'd provision any other deploy secret, either by mounting it into a directory and pointing SUPSO_LICENSE_PATH at it, or by baking it into your build artifact: supso sync --dir ./.supso/license_certificates # at runtime: SUPSO_LICENSE_PATH=/app/.supso/license_certificates Because a certificate identifies your organization, you can treat it like your existing secrets. Just keep it out of public source control, and don't run the interactive login flow inside a deployed service. Why this matters The point of supso isn't really the certificates. It's what they make possible. Open source built the modern world, and it did so with almost no financial support. The people who maintain the libraries everyone depends on are, with very few exceptions, not paid for it. They do it on nights and weekends until they burn out and walk away, at which point the multi-billion-dollar companies depending on their work scramble to find someone else to do it for free. It's the tragedy of the commons, and it's a structural problem, not a personal one. Supported Source exists to fix that. Companies are happy to pay for software that's reliable, supported, and secure. They do it all the time. What's been missing is a good way to do that with their dependencies. Supported Source is the missing piece: it's how a company licenses a project, and it's how the revenue from that license flows back to the maintainer who built it. If you maintain a project that companies depend on, that means you can get paid for it. The license fees companies pay to use your project go to you, so the work everyone relies on is funded. This helps a project stay healthy because there's an actual business model behind it. If you maintain a project companies depend on, get in touch to see how we can help you get paid for it. Open source built the world. Supported Source helps the people who build it.