I actually had a plan (around 2015) to make a DSL for REST API generation/automation on top of Leptus. But I couldn't afford to work on it.

The least you can do is to emphasise the issue, maybe point to libraries that can be used in conjunction with your framework: a library for creating/using links and link templates, libraries for some existing vocabularies, like Siren or HAL.

Keep it up ;)

It saw some usage in Rdio (the music streaming service) and a couple of other places. chef.io wanted to switch to Leptus back then, but I don't know if they did. I brought it back to life for personal use, and also because I was still receiving requests to do so.

Ranch is merely a socket acceptor pool. Condor takes care of framing and buffering, also.

Doesn't native erlang handle that? With {packet, Len} and {active, once}?

Not the buffering.

You can set a user level buffer size of the socket driver, and a receive buffer size (see http://erlang.org/doc/man/inet.html).

Why is another level of buffering needed?

Dammit, I should be looking for an alternative rss reader