Curate

Blog

Notes on saving things properly.

How Curate reads what you send it, why it is built the way it is, and what it does with what you save. Written for people who already have four hundred bookmarks.

RSS · llms.txt

  1. Privacy and data · · 2 min read

    What we keep when you delete something

    Deleting a recipe does not delete the photograph it came from. A deliberate decision with a real cost, and a plainer explanation than a policy line.

  2. Recipes · · 2 min read

    Why quantity and item are separate fields

    Storing "3 tbsp white miso" as one line makes a recipe readable. Splitting it into three fields makes it searchable and editable. Here is what that buys.

  3. Capture · · 2 min read

    The share sheet is the product

    Capture has to take under five seconds or it does not happen. That one threshold decides most of how Curate is built, including what it refuses to ask you.

  4. Capture · · 2 min read

    What happens when a page will not let us in

    Some pages want a subscription, some never answer, some are behind a login. What Curate does with each, and why your link is safe either way.

  5. Recipes · · 2 min read

    Two things we could not read

    When extraction is unsure, Curate asks instead of guessing, and shows the crop it is unsure about. Why asking beats being confidently wrong.