evbogue

Congrats Ry

I just throw Deno into my agents file and it gets installed in whatever environment I'm working in.

However, the truth is that writing isomorphic javascript programs in the age of agentic coding is much less important to me than it was a few years ago.

Singapore would do better banning cars altogether.

As a former CEO of HTMX I thank you for your service as the current CEO of HTMX.

And yet, they don't advertise content hashes so the data cannot be distributed by the software.

Yes like all of this would benefit from their team studying the implementation of Tahoe-LAFS.

Upside: data is always available even if Bluesky's funding is pulled. Downside: we lose deletes.

IPFS already exists. What I want is distributed Bluesky, since it's a product success and I do like most of the proto and the team. Do you want to fix this? I just spoke with Claude and I don't think it'd be too difficult these days for us to fix this in the core product.

Having the content available everywhere seems like the definition of a distributed system to me. Hashing content is not a discovery issue, one simply iterates over a list of hosts and asks if they have the msgs by their hash.

Yes, and is that useful within the structure of the Bluesky ecosystem?

What if PDSes replicated the content of PDSes? Then it'd be available.

Yah it clearly has always done this, but why doesn't it support multi-PDS replication?

But you're right that the screenshot proto and the copy and paste proto are quite successful as a distributed system these days.

Yah atproto auths moving data from the pds to the index, similar to like https, but they missed authenticated distributed data storage somewhere along the way. Why is that, I wonder?

The article seems to forget about content addressable storage and signing key cryptography and how these tools might make their software more distributed.

Like peers could sign sites?

We need git-ssb