Torrere
Torrere docs · Getting a recipe in Torrere
Torrere reads some sites from your phone
When a recipe site answers Torrere's server with a browser check instead of the page, the iPhone and Android apps read that page on the phone itself, in the phone's own browser view. On the web, Torrere hands the link to your phone. A site that refuses Torrere, turns it away as too many requests, or asks in robots.txt not to be read isn't read from anywhere. Torrere can still write its own version of the dish.
Torrere tells you which kind of no it got
Torrere's message names the site and what it did, because each answer means something different:
| What Torrere says | What happened |
|---|---|
| "site only lets a browser read it." | The site answered with a browser check. The phone apps read it. |
| "Couldn't reach site just now." | The site timed out or had an error. The phone apps try it too. |
| "site won't let Torrere read it from here." | The site refused Torrere, or said it had too many requests. |
| "site asks Torrere not to read its pages." | The site's robots.txt names Torrere, or everyone, and says no. |
| "That page isn't there any more." | The address is gone. |
Torrere reads browser-checked pages on the phone
Several of the biggest recipe sites answer Torrere's server with a browser check, and Which recipe sites Torrere can read names them, from Torrere's monthly test of 100 sites. A server is never a browser, but a phone is. So in the iPhone and Android apps, Torrere opens the page in the phone's own browser view, in a see-through sheet that says "Reading" and the site's name. It has 25 seconds. You can swipe the sheet away to stop it. The same happens when a site couldn't be reached from Torrere's server.
Torrere on the web hands the link to your phone
A browser tab on the web can't read another site's page, so when a site only answers browsers, Torrere on the web says so and that the Torrere app on your phone can read it. In a phone's browser there's an Open in Torrere button. On a computer there's a QR code: point your phone's camera at it, tap Open in Torrere, and the app reads the page and the recipe lands there.
Torrere doesn't read a site that says no
When a site refuses Torrere, turns it away as too many requests, or asks in robots.txt not to be read, Torrere doesn't try again from the phone. A site that asked Torrere not to read its pages didn't ask for them to be read from somewhere else. The sites that refused Torrere in its latest monthly test are listed on Which recipe sites Torrere can read.
Torrere can write its own version of the dish
On the web, the message about a browser-checked page comes with Write my own version. Inside a recipe you're already changing, a link Torrere couldn't read gets a plain sentence saying so and an offer to write its own version. Anywhere else, ask Torrere for the dish by name. Whichever way, what Torrere writes is its own recipe for the dish, not the site's, and Torrere never calls it the site's recipe.