The "this wasted my time" comments are missing the point...

In addition to his great sense of humor, Steve is usually ahead of the curve in terms of trends. There's a lesson in this. LLMs have become incredible constraint solvers ("SAT-solvers for code"). Well-thought-out tests, types, specs, and docs are all incredibly valuable constraints. This has big implications - for example what happens to licenses when you can cheaply rewrite the codebase and therefore unencumber it.

Is it really re-writing - legally - if you are starting from the codebase itself? Not a lawyer, am wondering however if the Google vs Oracle Java lawsuit has some implications for this.

You can add this as a bookmark in your browser, and just click it to toggle between x.com and xcancel.com

javascript:(function(){const p=['https://x.com','https://xcancel.com'],u=location.href,i=p.findIndex(x=>u.startsWith(x));if(i!==-1)location.href=p[(i+1)%p.length]+u.slice(p[i].length)})();

I do something similar since I don't want to trust yet another extension, I made a small Tampermonkey script.

https://gist.github.com/dobladov/62c4be59d774347cb480b115969...

that still gives X the impression though, which some are not to keen on.

We're building a similar product at https://gitlip.com

We would love to speak to any Glitch users about their particular use case. Please reach out to natalie [at] gitlip.com

Very good first impression. Well done!

Name suggestion for the wall: "Hydrobit generator"

They should periodically change the name at random, and let the name contribute to the entropy. Of course, this won't work if everybody votes to name it, say, "Wavy McWaveface."

OP here. Oops, thank you for pointing that out! We weren’t aware of it. We will investigate ASAP. In the worst case, we’ll change our name.

Doesn't sound worse case to me. It could use a better name anyway.

gitlip is not a good name, but you can be sure that if a new name does not include git it will be a worse name.

How so? I think they'd want to make a more generic name, because their success so far seems to be in gluing a couple of things not directly related to git together. These are running WebAssembly on the server and using a centralized storage backend. Even if they're laser-focused on the same problem of multi-tenant version control, I wouldn't be surprised if they wanted to support using CRDTs in a similar matter down the road.

right... they should call it Cloudflarelip /s

Great question! By default, with libgit2 each write to a repo (e.g. push) will create a new pack file. We have written a simple packing algorithm that runs after each write. It works like this:

Choose these values:

* P, pack "Planck" size, e.g. 100kB

* N, branching factor, e.g. 8

After each write:

1. iterate over each pack (pack size is S) and assign each pack a class C which is the smallest integer that satisfies P * N^C > S

2. iterate variable c from 0 to the maximum value of C that you got in step 2

* if there are N packs of class c, repack them into a new pack, new pack is going to be at most of class c+1

OP here. We're not an AI company; we're aiming to be AI-adjacent and simplify the practical application of AI models.

Honest question: how is this "AI-adjacent"? How does it specifically "simplify the practical application of AI models"? Focus of the question being on "AI"...

OP here. Thank you and good catch! :-) We have a blog post planned on that topic.

OP here. Not yet - it's about 50% complete. I plan to open-source it in the future.

Definitely interested in seeing this as well. What are the key features?

OP here. We’re building a new kind of Git platform. "Infinity" is more beneficial for us as platform builders (simplifying infrastructure) but less relevant to our customers as users.