Menu ▾ ▴

#476 Plan a model that screens whether a timeline's events should be indexed

open
nobody
None
2 days ago
2 days ago
Anonymous
No

Originally created by: athanclark

Follows [#467], whose automatic rule decides which moments' and durations' pages search engines get by fixed checks.

The current rule:

  • an event needs at least 150 characters of notes and a title of its own;
  • a timeline whose notes are mostly one template (the same text with numbers and names changed) lists none.

That catches log imports and generated notes. It can't judge whether the notes are worth a page: thin but long text, near-duplicates the template check misses, spam, or a timeline that's a test or a scratchpad.

Wanted: a plan for screening a timeline with a model, suggested as "jev" (to be confirmed which model that means), to decide whether its contents should be indexed. Questions to answer:

  • Input: a sample of a timeline's titles and notes, as the template check samples them; whole timelines or single events.
  • Output: list all, list automatically, or list none, perhaps with a reason the owner sees in the timeline's settings.
  • When: on publishing and after large saves, with the verdict cached by revision as the template check is. Never on each page view.
  • Self-hosted servers: off unless configured, with the fixed rule as the fallback.
  • Cost and privacy: where it runs; only public timelines are sent; and what it costs per timeline.
  • The owner's choice: an owner's explicit All or None setting stays above the model.

🤖 Generated with Claude Code

https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B

Related

Tickets: #467
Tickets: #477

Discussion


Log in to post a comment.