mbien

Thanks for your feedback! Indeed we tested it mostly for firefox & chrome compatibility for now

As stated in readme, the dataset is downloadable from our website

yes, we got quite a long queue :D

Short version: https://www.aclweb.org/anthology/2020.inlg-1.4.pdf Long version: https://www.researchgate.net/publication/345308878_Cooking_r...

They're both in README.md

Hi, after gathering the model and tokenizer, you can use the generic huggingface tutorial for text generation: https://huggingface.co/blog/how-to-generate

We use custom control tokens, so you have to provide the specific structure of the recipe, simply typing it in the huggingface prompt won't work. The details are available in our papers about the solution.

Good question! I'd say, ultimate task is to achieve both, but what is fully achievable atm is to get the right recipe structure. The idea of "validity" is very hard to evaluate and often has high regional and personal variance, but many teams around the world are working on this problem at the moment!

Hard to say per recipe, as in the current setup they are generated on demand and not pre-generated. But as you can see, we're hosting the solution in academia so it's basically for free vs around 2$/hour with GPU on AWS

Yes, you might be right about the timer, we'll think about changing it!

Perfectly understood! We just cannot afford to run it on GPU in the backend so the generation takes up to 3 minutes which is terrible thing to do interactively :( You're invited to check it with 10minutemail or so, or you can try our model on your own if you have some python experience: https://huggingface.co/mbien/recipenlg

I'm truly impressed how wide the response is. It makes me sure that this project is truly worth continuing. Thanks HN!

I agree, I don't claim it's ready Please, treat it as interesting project to follow that has just started, and is surely not meant to be deployed in production environments, at least not in this state

Currently we have only what CapacitorSet prepared: https://github.com/Glorf/lear/issues/1 I'll try to fix HTTP/1.0 support and post some more detailed benchmark in few hours

Currently, it's architecture is similar to modern nginx, while simplicity is the point that makes it faster. I'll surely, look at your links and ideas, as this is still highly WIP. If you want to help creating this, feel free to join! :)

TBH, it was simpler in implementation and maintance, while creating just a little bit slower than pthread on initialization time.

- Main advantage is simplicity, but architecture is in fact very similar to nginx. So, server should be faster than nginx but scale similarly. But it's all still highly DIY

- You're right, I mean non-blocking architecture of network IO.

https is one of the first features I'd like to implement in the near future :) Do you know if there is some framework that I could test my server with, against eg. nginx? I was looking for one to do profiling, but am unsure if there exist some that allows you to create high traffic with many clients.