iiinova — where your digital self keeps evolving

Reposted by Miroslav Bajtoš

so long; thanks for all the fih @crumb.bsky.social · 15h

news.ycombinator.com/item?id=4998...

ihoggan
I was a graph theory junkie long ago and even moved to Budapest for awhile to study among the greats. While I was there I started working on Barnette's Conjecture which came to occupy my thoughts over the next 24 years of my life, on and off as I worked in many different fields. Last summer I even thought for a few days that I had actually solved it. But it's supposedly proven here - problem 180. I don't know what to think exactly. I spent thousands of hours on that problem. I really enjoyed it. Hearing that it is solved somehow makes me sad in a far-off way, like hearing an ex-girlfriend died suddenly in a car crash. I don't know, there's probably a lot of people feeling odd emotions tonight. There's no Lean proof for this one so I'm digesting the paper. On the surface it looks like an approach I considered 24 years ago and abandoned.
I revisited the problem this summer, along with my partial solutions, when the previous round of stunning proofs came out. Several hours of work with Fable simply convinced me it wasn't yet solvable and reinforced how hard of a problem it was.

jboggan
I went back to that Fable chat and showed it this new preprint. It coded up the new constructive algorithm and ran it against the existing test suite, that looks good at least.
It has been super helpful in delineating where the crucial concept came from. The proof is rather simple as graph theory proofs go, but it does seem to use some constructions that would only seem obvious if you had serious physics experience with partition function and calculating energy states that cancel out. It's not a wholly alien bolt from the heavens, but I can also see how there hasn't been a human being with the broad theoretical physics knowledge combined with the deep graph theory experience in planar graphs to come up with this idea. I don't know, I'm looking for precedents of this formulation and some old papers of Penrose counting the number of edge colorings of this same graph type are coming up, the line of argument at least rhymes. But I agree with the thought that this sort of progress should not be siloed inside those companies. I propose a tax so that every slop cannon Al video pays for another hour of compute time for advancing mathematics.
reply

823051

Reposted by Miroslav Bajtoš

Matteo Collina @nodeland.dev · 14h

In the era of AI, our network is what makes us valuable, and the work more enjoyable. (The work is mysterious and important). Go to more conferences.

2255

Reposted by Miroslav Bajtoš

b5 @b5.bsky.social · 30/09/2026

All it took was writing our own DNS resolution crate & some number of months shaving down dependencies ☺️

4501

Reposted by Miroslav Bajtoš

Rob Palmer @robpalmer.bsky.social · 30/09/2026

ECMAScript excitement 😉 Congrats to @nicr.dev on advancing `export defer` to Stage 2.7 at @tc39.es today 🎉 It is a performance feature that permits lazy evaluation of re-exported bindings. It is useful for reducing the cost of partially-used barrel files 👍

export defer { y } from "mod1";
export defer { z } from "mod2";

2478

Reposted by Miroslav Bajtoš

Rob Palmer @robpalmer.bsky.social · 30/09/2026

ECMAScript excitement 😉 Congrats to @ashley-c.bsky.social from TechAtBloomberg on advancing the Composites proposal to Stage 2 at @tc39.es today 🎉 Composites are objects that are compared by value instead of identity. They are an evolution of Record & Tuple proposal.

const pos1 = Composite({ x: 1, y: 4 });
const pos2 = Composite({ x: 1, y: 4 });
pos1 === pos2; // true

const positions = new Set(); // the standard ES Set
positions.add(pos1);
positions.has(pos2); // true

913124

Reposted by Miroslav Bajtoš

Rob Palmer @robpalmer.bsky.social · 30/09/2026

ECMAScript excitement 😉 Congrats to @nicr.dev on advancing "Include default export in export * from" to Stage 2.7 at @tc39.es today 🎉 Today re-exporting the contents of another module omits the default export. It is believed this behavior change is web-compatible.

export * from 'mod';
export { default } from 'mod'; // redundant!

1332

Reposted by Miroslav Bajtoš

Rob Palmer @robpalmer.bsky.social · 30/09/2026

ECMAScript excitement 😉 Congrats to Richard Gibson on advancing BigInt from Exponential to Stage 2 at @tc39.es today 🎉 🔶 BigInt("1e2") It allows a BigInt to be created from a number that includes an exponential component 👍

2194

Reposted by Miroslav Bajtoš

James Snell @jasnell.me · 30/09/2026

Some traditions must be upheld. It's mandatory.

1231

Reposted by Miroslav Bajtoš

Rob Palmer @robpalmer.bsky.social · 27/09/2026

ECMAScript excitement 😉 Sony Interactive Entertainment will host this week's TC39 meeting in Tokyo. Potential advancements: 4⃣ Dynamic Code Brand Checks 4⃣ Iterator Chunking/Includes/Join 3⃣ Thenable Curtailment 2⃣.7⃣ default in export * 2⃣.7⃣ export defer 2⃣.7⃣ JSON.parse opts 🧵

2518

Reposted by Miroslav Bajtoš

Shannon Vallor @shannonvallor.bsky.social · 25/09/2026

‘We’re going to lose some fine intellectual dexterity.’ This is a CEO openly confessing to a level of acquired mental indolence that, were he not coddled 24/7 by an army of paid underlings, would make him incapable of living independently and feeding himself. He’s fine with it. Your kids won’t be.

7340106

Reposted by Miroslav Bajtoš

James Snell @jasnell.me · 26/09/2026

This is the variation I'm gravitating towards... Especially witnessing bad behavior on all sides of the contribution pipeline.

1101

Reposted by Miroslav Bajtoš

Gergely Orosz @gergely.pragmaticengineer.com · 16/09/2026

Fresh data from GitHub: Agent-generated PRs have exploded in size. 9x the last 8 months (!!) No signs of slowing down. This is why everyone is rethinking code reviews, deploys, possibly even o11y thanks to the GH team for sharing this data with me! (Slide from my talk yesterday)

65613

Reposted by Miroslav Bajtoš

Bryan Cantrill @bcantrill.bsky.social · 13/09/2026

The contagion of fear bcantrill.dtrace.org/2026/09/13/t...

bcantrill.dtrace.org

The contagion of fear | The Observation Deck

1624283

Reposted by Miroslav Bajtoš

Bryan Cantrill @bcantrill.bsky.social · 05/09/2026

The revolt of the reader bcantrill.dtrace.org/2026/09/05/t...

bcantrill.dtrace.org

The revolt of the reader | The Observation Deck

1112431

Reposted by Miroslav Bajtoš

Michal Illich @michalillich.bsky.social · 25/08/2026

Apple introduced new Mac Studio and Mac Mini computers. Here's how they compare to AMD/Nvidia offerings. So they are good, but imho only two configs are worth considering: - M5 Max 18c/40c 48GB - $2,799 - M5 Ultra 30c/64c 96 GB - $5,499 All the others are just overpriced.

021

Reposted by Miroslav Bajtoš

Gergely Orosz @gergely.pragmaticengineer.com · 26/08/2026

Well this is damning and explains SO MUCH about why Meta is losing its best engineers; why morale is rock-bottom; and why an engineering culture built up in 20 years was destroyed overnight. Zuck + execs wanted to lay off ~60% of staff. When the business does better than ever.

713733

Reposted by Miroslav Bajtoš

Daniel Norman @norman.life · 19/08/2026

Must read for those curious about GitHub alternatives, like @radicle.dev and @tangled.org and how they embrace local-first workflows. Exciting to see the Zig community embrace @radicle.dev!

One issue is that Tangled doesn’t seem focused on local-first workflows, meaning that it doesn’t have a way to download Issues in order to view and manage them while offline. It would definitely be possible to implement this, given how atproto works, although it would be less elegant than Radicle’s solution where Issues and PRs are stored in the repository itself, meaning that one pull is enough to get everything at once.

A bigger reason why Radicle is better suited, is that Tangled is federated, while Radicle is p2p. The difference between these two approaches is sometimes hard to see, but here’s an aspect that makes it pretty clear: looking at Issues.

On Radicle there is no authoritative view of what “the Issues” of one repository look like. It all depends on your seeding policy. If you decide to seed all “forks”, then you will see all Issues that exist on the network, but you could also choose a more restrictive policy, where you only seed “forks” from a short list of authors that you follow. In this second case you wouldn’t have to worry about spam because even if a malicious user somewhere is creating spam Issues, those would never reach you (and if you were to choose the ‘seed all’ policy, you would still be able to ban them).

Most importantly, this is a choice made per-node. Each Radicle user can choose for themselves what they want to see.

052

Reposted by Miroslav Bajtoš

Dan Luu @danluu.com · 17/08/2026

The benchmarkpocalypse: danluu.com/benchpocalyp...

There's been a lot of talk about the vulnpocalypse, to which I don't have much to add because I'm not a security person, but I haven't seen much discussion on the closely related (and to be fair, less serious issue), the benchmarkpocalypse.

While it's become easier than ever to make serious performance gains, it's also become easier than ever to reward hack a benchmark and make fake performance gains. The former is probably happening quietly across many different companies, but the latter is something I see at least once a week nowadays. Someone will claim they optimized X and got some huge performance improvement over existing software but, when you look at it, what they did was make some optimization that improves benchmark performance without actually improving real-world performance. This is often some kind of "we re-wrote X in Rust"1 project or a new startup that's looking to either fundraise or sell something, but it happens on other kinds of projects as well2.

Rather than point to someone's bad claim, I'll point to FRE, this regex engine I had an agent build, which I could claim is the world's fastest regex engine because it beats the Rust regex crate at the fairly comprehensive rebar regex benchmark suite. But this was created by putting an agent in a loop for a month with instructions to not overfit to the benchmark but no real supervision. For the most part, getting an LLM to give you a good benchmark score is fairly easy, and this case was no different; it took a couple weaks to roughly match Rust regex crate performance and then another couple weeks to get to 1.4x faster3 on rebar. But, agents are wont to reward hack and ovefit unless you put serious guardrails in place to avoid that, which I didn't do in this case as an experiment.

To check for overfitting, I somewhat arbitrarily4 used the ripgrep benchmark corpus as a benchmark a holdout and instead of being 1.4x faster it was 10x slower on cases where the benchmark didn't take forever due to an alg…

5619

Reposted by Miroslav Bajtoš

James Snell @jasnell.me · 10/08/2026

In the unlikely case that you needed another reason to attend @nodeconf.eu this year, we'll likely be having a fun round of PowerPoint Karaoke with actual prizes. We will definitively determine who among the Node.js ecosystem is quickest on their feet at talking about absolute nonsense.

051

Reposted by Miroslav Bajtoš

James Snell @jasnell.me · 07/08/2026

Remember! @nodeconf.eu tickets are on sale!

085

Reposted by Miroslav Bajtoš

Kent Beck @kentbeck.com · 30/07/2026

My daughter Beth went seven years without writing tests, then converted a whole team. There's a trick she found in code review. Stop pointing out bugs, point out the missing test. Every test caught a bug. "It's your fingers on the keyboard. Write more tests out of defiance."

1339

Reposted by Miroslav Bajtoš

Chris Peikert @chrispeikert.bsky.social · 29/07/2026

Also: HAWK’s entire foundation was very new—just 4-5 years old, an infant by cryptographic measures! Most brand-new cryptography gets broken or severely weakened before long. This is normal and good. Now AI will help speed up that process more systematically.

0226

Reposted by Miroslav Bajtoš

Bailey Townsend 🦀 @pds.dad · 27/07/2026

I’ve been working on an Exaclidraw fork for about a week that syncs your drawings to your Atmosphere account as well as uses Iroh for realtime encrypted end to end collaborative work. I feel like it’s at a stage where I can share it. Meet lexidraw.app!

lexidraw.app

Lexidraw, an Excalidraw fork where your drawings follow you

Lexidraw is an Excalidraw fork where your drawings follow you. Share publicly with the Atmosphere or privately with iroh.

2336463

Reposted by Miroslav Bajtoš

Mosh Lee @mosh.bsky.social · 28/07/2026

Are there any Bluesky clients that automatically strip location data + suggest alt text for images?

341

Reposted by Miroslav Bajtoš

NodeConf.eu @nodeconf.eu · 17/07/2026

🥁 𝐒𝐩𝐞𝐚𝐤𝐞𝐫 𝐀𝐧𝐧𝐨𝐮𝐧𝐜𝐞𝐦𝐞𝐧𝐭🎙️ Thrilled to have Lois Zhao on the NodeConf EU 2026 stage! She'll tell us the story about "`𝐝𝐢𝐚𝐠𝐧𝐨𝐬𝐭𝐢𝐜𝐬_𝐜𝐡𝐚𝐧𝐧𝐞𝐥` 𝐃𝐞𝐬𝐞𝐫𝐯𝐞𝐬 𝐁𝐞𝐭𝐭𝐞𝐫 " 🎟️Don't miss it out, secure your tickets nodeconf.eu

052

Reposted by Miroslav Bajtoš

TC39 @tc39.es · 23/07/2026

ECMAScript Excitement 🎉 This week, at its 115th meeting, TC39 advanced these proposals: 3️⃣ Await dictionary 2️⃣.7️⃣ Thenable curtailment 2️⃣ Error code property 2️⃣ Fused multiply-add 1️⃣ Intl.DateTimeFormat alignment with other standards 1️⃣ Linear matching 1️⃣ Map.take

56817

Reposted by Miroslav Bajtoš

Robin Berjon @robin.berjon.com · 18/06/2026

I tried to explain to myself the behaviour of some people who only seem to reheat one another's ideas — and are the same people still on X today, irrespective of political alignment. berjon.com/rt/

berjon.com

The Retweeting Class

I have often found myself confounded by the behaviour of some people who seem impervious to reality — like the people still on X today. Here, I try to understand what grounds their epistemology and it...

65011

Reposted by Miroslav Bajtoš

David Gasquez @davidgasquez.com · 16/06/2026

The future is now! - Dial keys, not IPs, thanks to Iroh - Fetch hashes, not URLs, thanks to DASL - Build on shared records, not siloed databases, thanks to the AT Protocol

0306

Reposted by Miroslav Bajtoš

dan @danabra.mov · 19/06/2026

just migrated to @eurosky.social check check?

152678

Reposted by Miroslav Bajtoš

James Snell @jasnell.me · 14/06/2026

Oh. After many long years... HTTP now officially has a standard QUERY method. Think: cacheable, idempotent GET that can carry a meaningful payload. We can now all stop bastardizing POST. auth48-transition.rfc-editor.org/authors/rfc1...

auth48-transition.rfc-editor.org

37114

Reposted by Miroslav Bajtoš

Iroh @iroh.computer · 15/06/2026

We just released the first stable version of iroh, v1.0! Read about it: www.iroh.computer/blog/v1 We're super proud of where we landed with iroh's 1.0. Since version 0.35 it feels like we've entirely replaced the "engine underneath". Are you a fellow key-dialer? Come tell us how you use iroh!

iroh.computer

Iroh 1.0 - Dial Keys, not IPs

Iroh 1.0 is out. Now is the time to build.

721862

Reposted by Miroslav Bajtoš

Robin Berjon @robin.berjon.com · 13/06/2026

This could happen with your phone. This could happen with your laptop. This could happen with your credit card. It's a long list. Some of us have been working on this, but most large players, public and private, have stayed in fantasyland. Care to join us? www.euractiv.com/news/anthrop...

euractiv.com

Anthropic blocks all Mythos access after US order to cut off non-citizens | Euractiv

The company says it disagrees with the US government order and looks to restore access

719078

Reposted by Miroslav Bajtoš

Chad Fowler @chadfowler.com · 05/06/2026

Every outage, support ticket, strange customer behavior, and performance bottleneck teaches the system something. The problem is that we usually record the lesson as code instead of knowledge.

021

Reposted by Miroslav Bajtoš

James Snell @jasnell.me · 21/05/2026

Looks like the DTLS implementation has a fair chance of landing in Node.js soon so I wrote up a blog post about it www.jasnell.me/posts/experi...

jasnell.me

Experimental DTLS Support in Node.js

An experimental implementation of the DTLS protocol is coming to Node.js, bringing TLS-equivalent security to datagram-based communication over UDP.

041

Reposted by Miroslav Bajtoš

Feross @feross.bsky.social · 20/05/2026

Today is a big day for @socket.dev. We raised a $60M Series C at a $1B valuation, led by Thrive Capital. 20,000+ orgs, 1.5M repos protected, 1,000+ supply chain attacks blocked per week. 3/5 FAANG companies are customers. We're just getting started.

118514

Reposted by Miroslav Bajtoš

James @43081j.com · 20/05/2026

Woooo yeaaah! The missing piece 🎉 everything is about to get a lot more secure

docs.npmjs.com

Staged publishing for npm packages | npm Docs

Documentation for the npm registry, website, and command-line interface

512628

Reposted by Miroslav Bajtoš

Rob Palmer @robpalmer.bsky.social · 16/05/2026

Axel is perhaps the most professional and diligent JS educating author. I remember when it felt like a new JS feature wasn't "done" until he had written the corresponding explainer article. You can thank him by buying his books 📚

29224

Reposted by Miroslav Bajtoš

Socket @socket.dev · 04/05/2026

🧊 Big release for #JavaScript supply chain security: @pnpm.io 11 now defaults to a 1-day Minimum Release Age, blocks exotic subdependencies, and adds a new Allow Builds model. A strong step toward reducing exposure to fast-moving npm attacks → socket.dev/blog/pnpm-11... #nodejs

socket.dev

pnpm 11 Adds Supply Chain Protection Defaults for Minimum Re...

pnpm 11 turns on a 1-day Minimum Release Age and blocks exotic subdeps by default, adding safeguards against fast-moving supply chain attacks.

14515

Reposted by Miroslav Bajtoš

Liran Tal @lirantal.com · 05/05/2026

have to tell you, Microsoft really cooked with apm (agent package manager) and it is so underrated... highly recommend

021

Reposted by Miroslav Bajtoš

Liran Tal @lirantal.com · 30/04/2026

I'm going to follow Frank's advice and also update my open source contribution guidelines on my repos on GitHub with this kinda wonder though to which extent do AI agents actually parse the CONTRIBUTING.md file. Maybe I should stick this into README.md too.

021

Reposted by Miroslav Bajtoš

Matteo Collina @nodeland.dev · 01/05/2026

20x lower median latency than HPA. 6x lower than KEDA. 17x fewer failed requests than HPA. 9x fewer than KEDA. Same app. Same cluster. Same metric. The only thing we changed was the autoscaler. 🧵

121

Reposted by Miroslav Bajtoš

Robin Berjon @robin.berjon.com · 02/05/2026

Not to take you out of any kind of discourse, fam, but next Friday it's David Attenborough's 100th birthday. How do you plan to celebrate?

1143

Reposted by Miroslav Bajtoš

Zed @zed.dev · 29/04/2026

We've shipped more than a thousand versions of Zed, but all of them began with zero. Today, that changes. zed.dev/blog/zed-1-0

1642863

Reposted by Miroslav Bajtoš

Rob Palmer @robpalmer.bsky.social · 29/04/2026

ECMAScript excitement 😉 Congrats to @bartlomieju.bsky.social on landing experimental (flagged) support for @tc39.es Stage 3 Import Defer in upstream Deno 🎉 import defer * as lazyNs from "expensive"; Module evaluation is delayed until the first namespace access. github.com/denoland/den...

github.com

feat(unstable): support TC39 import defer proposal by bartlomieju · Pull Request #32360 · denoland/deno

This commit adds an experimental support for import defer ... syntax, for https://github.com/tc39/proposal-defer-import-eval proposal. Closes #30053

1204