gitonthescene

For posterity, this is even easier with Jython. (I have no prior experience with either...) ``` from org.apache.commons.text.similarity import LevenshteinDistance ld = LevenshteinDistance() return ld.apply(cells.col.value, cells.coord.value) ```

@wetneb Added doc about basic Clojure access [here](https://github.com/OpenRefine/OpenRefine/wiki/Recipes#11-clojure).

I don't know if this should be a new issue or not, but reconciliation feels slow again. Above @tfmorris says that this went away in OpenRefine 3.5 and I seem...

P.S. I'm happy to open a new issue if that's preferred. I just wanted to draw the connection to the old issue.

@vbmithr If you’re looking for an open source K, I can recommend [ngn/k](https://ngn.codeberg.page/).

There is a [pull request](https://github.com/daneads/pycallgraph2/pull/20) you might want to try.

One way to make servers more defensive is to add a [rate limiting reverse proxy](https://www.nginx.com/blog/rate-limiting-nginx/) to control the flow of requests.

If the services are to stick to one version, why would they supply a list of versions in the spec? If there hasn’t been a plan for how version updates...

I don’t follow. I’m trying to be constructive. I’ve even spelled out how a scenario could work. It might be more constructive to speak to that. I’m not clear though...

Concurrency is about parallelism and rate limiting is not. I agree that the service doesn't have much control over what a client may attempt and that rate limiting is one...