toomim

For this stuff, I'm most excited about https over iroh.

- https://github.com/aflin/iroh-webproxy

- https://github.com/n0-computer/iroh-proxy-utils

No port forwarding. No public IP required. No special proxy to set up.

Iroh already runs public relays. Your two computers will signal through those, and then port-knock and form a direct connection to each other, perfectly encrypted.

We just need to define a new https:// url, like ... let's call it "irohttps://" maybe, so then you could contact my laptop with "irohttps://<hash>/path?query".

We can be more specific than "the incentives are wrong in Academia", because we know what the incentive is: it's peer-review.

The problem is that today's peer review, while better than nothing, is far from a perfect judge of research quality. If peer-review was a perfect judge of research quality, there would be no incentive problem. The incentives would be aligned.

I happen to be working on an improvement to peer review. An early prototype can be viewed at https://peeryview.org/about. Holler at me if you're also working on this problem!

Yes, I need a recommendation, too! I'm currently living with loud A/C-noise fans and need to swap them out for something better, and I don't know where to look.

Artificial General Intelligence.

It means AI that is General, as in it is not specific to one narrow task, like object recognition or playing chess.

This was a hard problem for decades. No AI was general, until GPT 3 or 4. Now we have General AI.

So we have AGI.

> ceding more power to agentic AI will eventually reduce the primacy of the CCP’s ideological control.

Yeah, right.

This is dumb politics. Go away.

They said it was too dangerous to release before the companies that run internet for civilization could patch the holes it was finding.

That's a threat to civilization.

This phrase makes it sound like the author wasn't, himself, a developer. Like, maybe he wasn't even human.

It's interesting that I disagree with all of these points.

I'm starting to notice that LLMs tend to speak in the form of movie trailers.

Say this in a deep masculine dramatic voice:

     One man.  One gun.   A story that would could never die.

Compare that with this Coldcard page:

     Two files, four lines, five years unnoticed.   This is the COLDCARD
     entropy failure

It's trying too hard to replicate a dramatic movie arc with every... single... sentence...

This is a nice writeup of the problems in using Webhooks for State Synchronization. I also noticed that the proposed solution is a pseudo IETF-style draft protocol called SCROLL... that happens to be remarkably similar to an actual IETF draft I am bringing to IETF 127 this November called "Braid-HTTP Subscriptions."

Both drafts request a subscription with a GET plus a header:

    Scroll Request:
      GET /scroll/feed/customers
      Prefer: stream
    
    Braid Request:
      GET /customers
      Subscribe:

In both systems, the GET leaves its response open to stream events. SCROLL responds with application/x-ndjson. Braid subscriptions are a 209 Multiresponse, with content-type application/http-history. This lets them support more than just JSON. You can send updates to the state of CSV, or PNGs, XML, HTML, plain text, or any media type.

The author noted that it's hard to get adoption. Well, the reason that Webhooks are so common is that they are bog-standard HTTP. For this to get adopted, we need to put it into bog-standard HTTP. So we need to go to the IETF, and and extend HTTP in a general way to support state synchronization. It should just work for any existing HTTP media type (not just JSON), and any resource/URL (not just special /scroll/* URLs), and any way of marking timestamps (not just the ordered strings proposed in SCROLL).

Then we can bake this stuff into HTTP, and thus into all our bog-standard libraries, utilities, and code, and you won't have to reimplement the same sync-logic-over-webhooks again, and again, and again.

Reach out if you're interested!

Complex Message Transfer Protocol

Good point. You don't even need to rename the upstream project. Just create a new project, and get the code there. Since it's open source, it will eventually make its way into the upstream libwacom as well.

AT does have instances. They are just grouped differently.

In BlueSky, there is only one single "AppView" instance in the entire network. There is one instantiated "Firehose". Each user can instance his own "PDS".

In ActivityPub/Mastadon, the instances are "sender's server" vs "receiver's server."

The difference isn't that there aren't "instances" in AT proto. It's just that the instances are segmented differently.

Because tribalism. NAACP is lefty, and Musk is righty. So they fight.

I just installed it, but I can't get it to switch spaces, or show the grid overlay. It just beeps at me with the "you can't do that" beep. When I click "Add Desktop", it says "Could Not Add Desktop" and "GridLion could not read the current Spaces for this display."

This is a M1 macbook air. I really want to try this.

It's compiled to wasm for "performance", but...

1. WASM FFI has a big overhead when interacting with the javascript DOM.

2. Any DOM UI has a big overhead compared to a canvas.

I would be curious to see an actual performance evaluation. This looks like it was built for the wrong tradeoff otherwise...

How do you compare this to the effort in https://braid.org, which is also a decentralized web, which adds subscriptions that can operate in a tree (or DAG) of reactive state, each with its own validator and supporting different media types, and merging with merge-types?

Freenet seems to not interoperate with the existing WWW as much, while at the same time giving more specification on a specific routing and WASM validator. The existing WWW and Braid leave those decisions up to each particular host/authority to decide.

If you like darcs, try Pijul. It's darcs' spiritual successor, and quite performant and capable.

"An AI model is incapable of that."

"Good designers will reject this."

^ Famous last words.

It released in February 2026.

How about hacking a remarkable e-ink tablet as an easy prototype? The remarkable is basically a "better paper" already.

The git porcelain is functional, like a toilet.

You can generically represent copies and renamed (aka "moves") in a CRDT, OT or CTM using a Portal: https://braid.org/meeting-62/portals

Pijul does both. It's a VCS, that is a CRDT, that preserves conflicts until a human resolves them.

Look it up: https://pijul.org

It also makes cherrypicking and rebasing wayyyy easier. You can actually add or remove any set of patches, at any time, on any peer. It's a dramatic model shift -- and is awesome.

CRDTs actually have a long history in version control.

  - The original 1977 version control system, SCCS, was a CRDT: https://braid.org/meeting-60/sccs-is-a-time-collapse

  - It called its data structure a 'weave"

  - Brahm's old project "Codeville" used a weave for version control

  - But then git blew up in popularity.

  - The project "DARCS" tried to make a robust "theory of patches," and eventually led to the development of Pijul

  - Pijul is a VCS that is a CRDT: https://pijul.org

It depends strongly on the city, and became more pronounced since covid.

Seattle is the worst. They call it the "seattle freeze." The San Francisco Bay Area became almost as bad in covid.

The south is still friendly. Austin is incredibly friendly with strangers. Miami has strong stranger vibe. NYC is still alive, too.

You can do this by (1) extending your CRDT into a CTM (see https://braid.org/time-machines) and then (2) use the antimatter algorithm (braid.org/antimatter), or something similar, for acknowledgements.

The antimatter algorithm allows peers to learn where the rest of the network has caught up to, without a central actor, or relying on consensus, across arbitrary P2P connection & disconnection events in the network. It even allows subnetworks, after a partition, to prune the history that they generate while partitioned, while still holding onto the necessary older history to reconnect with the other half of the partition.

From just 14 hours ago!?

Faster and cheaper transactions that don't get locked up by the whims of a bureaucracy. They continue to operate on non-business days.