ihrimech

That's the one measurement I always need. We support three modes: - full manual, where the client enters their own measurements; - semi-automatic, where the client fills out a short form and we estimate measurements from anthropometric statistics; - full automatic, where the client takes two guided photos in specific poses with their phone, and we derive the measurements using a BMNet-based model

I’m working on https://fittingme.ai, a product-page widget for fashion e-commerce.

It answers two questions that are usually handled together inside the fitting room: “How might this look on me?” and “Which size should I order?”

The virtual try-on renders the garment using a shopper’s photograph. The size recommendation component estimates the users measures, use the brand’s size chart estimated measurements and suggests a size plus a fallback.

The merchant integrates both through two widgets.

Extract of the study : We study allowing large language models (LLMs) to process arbitrarily long prompts through the lens of inference-time scaling. We propose Recursive Language Models (RLMs), a general inference paradigm that treats long prompts as part of an external environment and allows the LLM to programmatically examine, decompose, and recursively call itself over snippets of the prompt. We find that RLMs can successfully process inputs up to two orders of magnitude beyond model context windows and, even for shorter prompts, dramatically outperform the quality of vanilla frontier LLMs and common long-context scaffolds across four diverse long-context tasks while having comparable cost. At a small scale, we post-train the first natively recursive language model. Our model, RLM-Qwen3-8B, outperforms the underlying Qwen3-8B model by on average and even approaches the quality of vanilla GPT-5 on three long-context tasks.

research paper : https://arxiv.org/abs/2512.24601

I laughed so hard ...

Very nice idea for the project. The "baby steps" you're taking seems to be the right way to go. You may need to focus a bit more on the documentation though. I was interested in trying the product (for the sake of trying), but couldn't easily go further than the install steps.

This is where command and query (with subscribe) must be neatly separated. An event A launches an updates of the DB, that launches the query part to react, then stop. There is the risk of having an infinite loop, if the event A is launched by the query part, which is very related to the behavior of your app.