Skip to content

Design and wording ​

The look, the wording, and Anubis's own pages. Part of Experiments and decisions. Newest notes go at the top of each section.

Tag and list marks in Settings (2026-10-27) ​

  • Marks: list rows wore a diamond in the list's colour, the mark tags wear on search pages, while Settings → Tags showed each tag's colour as a round swatch. Lists now have no mark, and a tag's colour picker is a diamond (input[type='color'] in assets/theme.css).
  • Tag rows: spaced like list rows (16px above and below), and an open tag's Add site form labels both fields above them, so they line up when the "Why" label wraps. The site field's placeholder is example.com, as is Your sites' and the tag menu's prompt, in every language.

A new user's walk through Anubis (2026-10-26) ​

A review of the welcome page, the popup, Settings, and the mock search pages, as someone who has just installed Anubis. The owner chose what to change; what was left, and why, is below.

  • Load more results: kept at 3 pages by default, with nothing on screen moving once someone is reading. See "Load more results" in search-pages.md.
  • Starting choices on the welcome page: Remove AI answers, Hide AI-generated sites, and Lower paywalled sites, as switches that change the real settings (entrypoints/welcome/choices.ts), between the practice search and More to try. Every Remove panels switch starts off and the AI content list only labels, so someone who installed Anubis for those had to find them in Settings. The lead's "Nothing you do here is saved" now says "on it", the practice search, since these are saved. The welcome part checks each switch sets its setting and puts it back.
  • Settings → Results: Rerank results and Load more results (until now "Extra pages per search") left Appearance, since they change what happens, not how it looks. The setting is named after the summary's button and has a hint again, under which the robot-check warning still shows from 4 pages.
  • Publish your list: five steps, the first of them editing the downloaded file's header by hand, are now a form for the name, description, author, and where to suggest changes, saved into your list before the download (setListInfo in utils/personal.ts), then three steps pointing to gist.github.com. Your list keeps the details for next time. The browser's own check of a web address is off on that form, so Anubis's message shows instead.
  • Lists: the rows trimmed on 2026-10-17 stay trimmed. The owner chose the update button's tooltip for a list's size and when it last arrived ("1,566 instructions, updated 3 hours ago. Update now."), with tAgo back in utils/i18n.ts and the old translations of "just now". Not done: how many sites a list in More lists would hide, which means downloading lists nobody subscribed to; their descriptions already say what they hide. Nor what each list changed on your searches, which would need counting on every search page.
  • Tags: shown as they are; the owner chose not to move broad tags into the menu. Settings → Tags said AI slop came "From FOSS tools", which only shares the tag's definition (on purpose, tests/lists.test.ts), while AI content gives it its sites. "From …" now names defining lists only when no list gives the tag to a site; the options part checks it and failed before.
  • Numbers in messages are written as the interface's language writes them (tNumber in utils/i18n.ts): "1,566 sites", not "1566", and Bengali's own digits.
  • Part of a site: on Reddit, YouTube, Medium, GitHub, GitLab, Codeberg, X, TikTok, LinkedIn, and DEV, the menu, the popup, and Add a site offer someone's own part of the site when the address names it, such as reddit.com/r/rust (spaceOf in utils/domain.ts). Your list writes it as /r/rust^$site=reddit.com, which the list format already matched, and reads that form back as one entry, so Your sites, sync, and Undo treat it like any site. A rule for part of a site now comes before the site's own rules whatever their order in the list, as the wiki's "the most specific one wins" says; tests/matcher.test.ts failed on that before. Only those sites: elsewhere a path is rarely someone's, and offering one on every result would crowd the menu. A YouTube video's address doesn't name its channel, so a channel's videos can't be ranked by their channel.
  • Left as is: the engine's own order for one search (turning Anubis off does it), and Edge, which installs from the Chrome Web Store. A way to report problems without a GitHub account stays on the roadmap.

Organising Settings (2026-10-21) ​

Asked for, after the first pass below. Your lists folding by itself past five was unwanted: all of Lists' sections start open again, and fold only when someone folds them. "Remove panels the sections" had meant the Remove panels page: its groups now fold their parts under the group's name, which says how many are on, so the page reads as five rows. A list's buttons were a bordered Suggest changes beside a switch and two icons, centred in the row; Suggest changes and Homepage are now small text buttons under the description, and the switch and icons sit level with the name. Lists and tags only came in one order (subscription order, and by name), so each row has a handle to drag, or to focus and move with the arrow keys. Tag order is stored as order in sync:tagPrefs, so backups and sync carry it with no new key, and collectTags sorts by it, which the popup and the result menu follow. Hidden results became a drop-down and tag colours a switch: a row of three bare words read as text, not as a choice. Tags got column names for the drop-down and the switch, which had none, and a tag's "From" line names only lists the sentence above it doesn't. Backup comes first on its page, as the sidebar names it. The colour scheme button had no place on phones, where the sidebar's foot is hidden; it now ends the row of sections there.

Google's Always open the Web tab then sat folded under AI answers, whose switch didn't turn it on, which read as a bug. It isn't a panel, so it's now a switch of its own, last on the page.

Rejected: native HTML drag and drop, which doesn't work on touch screens; pointer events do both. A sort menu (by name, by sites), which orders but doesn't let someone put a tag first.

Less crowded settings (2026-10-21) ​

Asked for. The colour scheme was a three-word choice row in Appearance and again in the sidebar; it is now one icon button in the sidebar that steps Auto, Light, Dark (themeButton in utils/theme.ts). Appearance lost its "Anubis is on" switch, which repeated the popup's. "Load more results automatically" had a hint, a help link, a unit, and a cost tip that changed with the amount; it is now "Extra pages per search" with a warning only from 4 pages up. On Lists, a long Your lists pushed More lists and its Subscribe buttons out of sight: the three parts fold under their headings (foldable in options/parts.ts), and Your lists starts folded past five, which the nine default lists already are. Names of lists published from this repo were up to 37 characters ("Independent wikis (Indie Wiki Buddy)") and show after "from" beside each tag, so they are held to 20 like tag labels (tests/lists.test.ts); the source is still credited in the description and author. Lists by other people have no limit. The wiki lost "Turn Anubis off" and "Help", which said only what the popup shows.

Filter by pressing a result's tag (2026-10-17) ​

The summary used to carry a row of every tag on the page, each with a count, to show only that tag. It made the header tall and repeated what the extension's menu already offers under This page. Now the tag under each result is the button (pressed again, it clears), and the summary keeps only Show all.

Grouped switches in Remove panels, and quieter list rows (2026-10-17) ​

  • Remove panels: ten switches in a flat column, led by "All" and an "On every search" heading, read as a wall. They're now five groups: AI answers (with Google's Web tab under it), videos, images, and news, questions and discussions, advertising, and other search engines. A group's switch sets all of its parts and rests half-way (:indeterminate) while only some are on; the parts drop their notes, since their names say enough.
  • Lists: each subscribed list showed its format, "built in", rule and tag counts, author, update time, licence, and its tags. It now shows its name, one-line description, and links; "lens" stays, since it changes what a search shows. List and directory descriptions were cut to a few words.

Shorter interface text (2026-10-17) ​

  • Shipped: about 90 of the longest messages in Settings, the welcome page, the popup, and the search-page summary were cut to one short sentence, taking the English interface from about 3,700 words to 2,850. Explanations that only mattered to maintainers (how sync merges, why encryption works as it does) live in code comments and the wiki now. The README, CONTRIBUTING, SECURITY, lists/README.md, and the pull request template were shortened the same way.
  • Placeholders kept: a message that drops a $2 its translations still use breaks them, so every shortened message keeps its placeholders, even where the shorter English could do without one.
  • Not yet: the 17 machine translations show the changed messages in English until they're retranslated.

The column on the left, in Graphite (2026-10-17) ​

  • Level with the icon, not the first line of words (live DuckDuckGo and Bing): both put a 28 to 32px site icon beside a name over an address, so the first line sat about 9px above the icon's middle and the button with it. The button now centres on the icon that starts the row. Bing's icon is a .tpic box, which no icon selector matched. The column check asserts it (levelWithTheIcon); the DuckDuckGo padded mock now has the live icon and two lines.
  • Asked for: the result menu was cluttered: a third of the size, a smaller title, no gold, and a new palette. Then the dial had to go too: it only works where a result shows an icon (Mojeek has none). Designs were drawn as mocks on a design canvas before any code, as for the dial.
  • Tried and dropped, for the menu:
    • horizontal strips above the result: too cramped, then too spread out, and hard to read;
    • a watch, pointer, and clockwork theme in place of the ancient scales, and an old tally counter for Raise and Lower;
    • Pin and Hide on the same scale as Lower and Raise: they're separate ideas, not more of a raise or a lower;
    • "Raise more" buttons and dots to count presses: too crowded and unclear.
  • Tried and dropped, for the button: the dial on the icon, buttons in the page's left margin (a narrow window takes the margin away), several more dials, and a bracket that half wraps the result.
  • Chosen: one small round button in a column left of each result (entrypoints/content/column.ts), showing the ranking's icon: the balance, an eye struck through, or a pin. It's 12px from where the result's words or icon start, not its box: DuckDuckGo pads its results, which first left a 23px gap (padded mock).
  • Chosen: a simpler menu that pops out above the result, pointing down at its button so the result stays in view, or below where there's no room above. It keeps the balance, smaller and grey; the rankings are Hide | Lower, Normal, Raise | Pin; one hint line; the site's tags on one line with + Tag. Raise and Lower always show two arrows, and each press lights one more, so the unlit arrow says there's another step. Icons not chosen share one dim grey, about 3.5:1, while the words stay brighter. About 340 × 205.
  • Dropped from the menu: the cartouche, the Why section with its "Wrong? Report it to…" and "Suggest it to…" links, the footer, and the cog. Reports now go through suggest changes in Settings → Lists; a quieter home for pre-filled reports is in ROADMAP.md.
  • Graphite: neutral greys, with the text colour as the accent, everywhere Anubis draws: search pages first, then its own pages and the wiki. Then the logo too: the jackal in near-white on a graphite tile, with the toolbar icons, the badge, the store tiles, and the wiki's slides drawn from it. The grey icon for while Anubis is off stays as it was. The Appearance choice that was Gold is now Tag colours, still stored as gold.

The dial on each result (2026-10-16) ​

  • Asked for: the ⚖ button in each result's top-right corner looked fine on DuckDuckGo but awkward against a pinned result's frame. It should be quiet, and always in the same place. Designs were drawn as mocks on a design canvas before any code.
  • Tried and dropped:
    • the button beside the site's name, cut into the pinned frame, shown only on hover, or leading the tag line;
    • a column on the left of the results, saying what moved;
    • a badge on the site's icon. The icon itself can't be the button: DuckDuckGo uses it to search the site;
    • a pocket-balance gauge, a weight dial, and five dots with one lit;
    • the scale beside the icon rather than round it.
  • Chosen: a scale round the site's icon, with a watch crown that opens the menu (utils/dial.ts, entrypoints/content/dial.ts).
    • The scale is the left half of a ring, in a 2px line with round ends. Its zero is at 9 o'clock, so up means raised and down lowered, matching the result's height on the page. Raise and Lower fill it the same way, by how far the site moved, a quarter at most.
    • Pin fills the whole half circle, distinct from the most a raise can show. Hide is the empty line: a cross-out and a dashed line both read as noise.
    • Greys only, no gold. The pinned frame turned grey too, and takes in the crown rather than cutting through it.
    • The crown went through many rounds. Guards on the ring itself crowded it, so they moved to a wider circle, at the same 2px weight. The crown sits a layer behind the scale, so its tip never pokes through, and slides out on hover.
  • Where there's no icon (Yahoo, DuckDuckGo's HTML and Lite pages), the dial goes round a plain disc before the title. A hidden result's line has its dial round the line's eye, or in the discs' column where the page has no icons, so the column doesn't jump.
  • Image and video results: a ring has no room on a picture.
    • Tried: moving the pictures to make room, a rail or a dial under the picture, a straight line inside it, the dial in the caption, and six wilder ideas.
    • Chosen: the same crown and an upright scale on a small dark tab in the picture's top-right corner, where the ⚖ button was. The tab is white on 62% black, so it reads on any picture.
  • Phones keep the ⚖ button on the title's line for now: a dial there would be hard to press and would crowd the title. To be reconsidered.
  • On Brave, the crown reaches a few pixels past the card's left edge, since its icon sits close to it. It stays inside the window (dial e2e part).

Tag marks and a balance that weighs (2026-10-08) ​

  • Asked for, later the same day: a pin sign. No tag could pin, so a sign alone would never show. Tags got a Pin choice in Settings → Tags: results carrying the tag go to the top as if you'd pinned the site, with the pinned frame, and the pin sign, a 10px version of the ranking's pin, takes the tag's diamond's place. Like Raise and Lower, it adds to your own ranking, so your Lower still orders a pinned result among the others; a Hide tag still hides, and your own ranking beats a Hide tag as before. Lists still can't pin.
  • Asked for: the balance in the result menu and the popup tips by how far the result moves, not only by its ranking, so two Raise tags tip it further than one. tiltFor in utils/balance.ts grows with the score and levels off below a pin or a hide (one Raise, 5 places, tips it 6° as before; 10 places 8.7°; 15 places 10°; never past 11°). The balance now weighs the result's whole verdict, your ranking included; before, it showed the ranking you pressed, or else the lists'.
  • Asked for: a tag that raises, lowers, or hides the result shows that ranking's icon, simplified to a 10px sign in the tag's colour, where its diamond was (tagMark); a tag that does neither keeps the diamond. It shows what the tag actually does to that result: your choice for it, or the list's own rule when you follow the list, and nothing once your own ranking replaces the lists'. A list's pin still counts as its strongest raise and shows the raise sign. Screen readers hear the meaning after the tag's name, and the tooltip says it too.
  • Removed: the "Raised" and "Lowered" labels under a title, which the marks and the button's tilt now cover. Screen readers still hear the ranking in the button's label. A result raised only by a list or your own ranking, with no tag, shows it on its button alone.

Undo instead of "Are you sure?" in Settings (2026-10-08) ​

  • Reported: after pressing delete on a tag, the browser's confirmation box offered to stop the page showing more dialogs. With that ticked, the tag could no longer be deleted: the browser suppresses confirm(), which then answers "no" at once, so the button silently did nothing. Unsubscribing from a list and Reset settings asked the same way.
  • Considered: a two-click button ("Delete", then "Confirm?" for a few seconds). It still asks before acting, and the second click lands where the first one was.
  • Shipped: all three act at once and say what they did, with Undo beside the message for 15 seconds (flash in entrypoints/options/flash.ts takes an undo). Undo focuses itself, since the button that was pressed is gone, and keeps focus through the renders that follow a save. A tag's undo puts the list back only if it hasn't changed since; a list comes back where it was, with its downloaded copy; a reset puts back the settings, tag choices, and subscriptions as they were stored. It matches the summary's Undo on search pages. The settings-undo e2e part, in checks, dismisses every dialog and fails on the old build; tests/i18n-coverage.test.ts fails on any confirm(), alert(), or prompt().

Report a problem (2026-09-30) ​

  • The owner asked for a bug report button people can find easily. Report a problem is in the toolbar popup's footer, beside Help, and in the Settings sidebar's links; the troubleshooting guide starts with it. It opens GitHub's issue form (.github/ISSUE_TEMPLATE/bug-report.yml) with the fields filled in by id from the link: Anubis's version, the browser and system from the user agent ("Firefox 143 on Linux"), and, from the popup on a search page, the engine's name. Nothing from the page goes in (no address, no search), and nothing is sent until the issue is submitted. Not put on search pages: the summary stays quiet, and the popup is one click away. tests/bug-report.test.ts checks the link only names fields the form has.

Tags in the site popup (2026-10-03) ​

  • Popup collapsed in Firefox (2026-10-05): 0.2.1 changed the popup's width from 340px to min(340px, 100vw) so it wouldn't overflow narrow viewports. Firefox sizes a toolbar popup from its content while the popup's window is still tiny, so the width followed the window down and the popup opened as a sliver at the screen's edge. Chromium's e2e pages have a fixed viewport, so they never showed it. The width is fixed again, with max-width: 100% keeping narrow viewports from overflowing. tests/popup-size.test.ts fails on viewport units or width media queries in the popup's CSS.
  • Race fixes (2026-10-05): the popup-tags e2e part failed in CI and in 6 of 8 local runs. Background list updates draw the popup again at any moment, and four things went wrong. A render that started before a click could finish last and draw the older list over it, so renders now carry a ticket and drop when overtaken. A redraw wiped what was typed in New tag and its error, so both carry over for the same site. Focus came back a frame after a redraw, leaving a gap with nothing focused, so it now comes back at once. A render of the older list used up the request to focus a just-created tag that wasn't there yet, so the request now waits until its tag appears. The e2e part also measured buttons that a redraw had just replaced; it now reads the button on the page. It now changes storage while a name is typed, which failed 3 of 3 runs before the fix. After the fix, it passed 30 of 30.
  • Found: the toolbar popup let people press a tag for the current site, but the selected state was too subtle to spot. It also had no way to create a tag there, despite both actions being available in the search-result menu.
  • Changed: selected tags now use their own colour for a 2px underline and bold text, without a fill. The popup always shows a compact New tag field, which adds a tag to the personal list and applies it to the current site; an existing shared tag is reused. Empty or duplicate names are explained beside the field. The action keeps keyboard focus on the selected tag after the popup redraws.
  • Checked: a new popup e2e part covers selecting, creating, styling, focus-safe redraws, and narrow viewports; it runs in CI.

Explanations on tagged sites (2026-10-04) ​

  • Race fix: the tag-notes e2e part failed about half the time, on main too. A change from elsewhere while typing makes Settings wait until the field loses focus before it renders again. Adding a site blurs the field, so that late render showed the older list and put the cursor back in the Add field. When the save landed, its render waited on the focused field, and the new site never appeared. The cursor now goes back only on a render that shows the saved list. The e2e part changes storage while the field is focused to force the race; it failed 2 of 3 runs before the fix and passed 10 of 10 after.
  • Added: every tagged site in the bundled FOSS tools list has an inline comment saying why it belongs. The Anubis list parser ignores trailing # comments, so these explanations do not change matching.
  • Added: Settings → Tags accepts an optional reason alongside a site. It is saved as a comment on the personal-list rule and shown under the site in the tag editor.
  • Compatibility: the note stays in the existing plain-text personal list and follows site edits and sync merges; old rules without notes remain unchanged.
  • Layout fix: the shared inline-form input rule also matched the reason nested inside its label, giving the text field a 260px flex basis on the column axis. The tag-note e2e check now asserts that it remains a single-line field.
  • Not used: the tag's definition description; that describes the label for every site, not why one site fits it.

Finishing touches (2026-09-29) ​

  • Second follow-up (2026-09-30): red for a ranking is now a written rule, not only a fix: STYLEGUIDE.md's principles, CLAUDE.md, and CONTRIBUTING.md say --danger is only for errors and deleting, and tests/palette.test.ts fails when a CSS rule for Hide uses it. "Clean up" in Settings read as housekeeping rather than what the page does; it's now Remove panels everywhere people see it (the settings section, the README and wiki features, the guide's title, the homepage, and the store listing), with #cleanup and guide/clean-up kept so links still work. The tag switch lost its "Shown" label, which only repeated what a switch in that place does (its tooltip and label for screen readers stay). Tags describe a result, so the Paywalls list's tag is now "Paywalled" (its id stays paywall, so tag choices carry over), and lists/README.md asks list authors to name tags that way. The name and logo at the top of Settings open the wiki.
  • Follow-ups (2026-09-30): the welcome page's logo read as too small beside the taller header; it's now 112px (72px on phones). The balance no longer swings as the page opens: the owner wanted it to move only when clicked. A chosen Hide was red (--danger) in the popup, the result menu, Settings, and the Introduction's demo, which the owner found out of place in the palette. It's now grey: the text colour with a --muted underline, the same weight as the other rankings. --danger is kept for errors and destructive actions. In Settings → Tags, Edit followed each tag's sentence, so it sat somewhere different on every row. It's now in the row's controls, after Shown, with a fixed-width dropdown so it lines up.
  • Asked for: the project owner wanted the extension to look better, with small, tasteful additions rather than anything loud. Ten were mocked up beside the current build, in both schemes. The mockups aren't in the repository.
  • Shipped: a diamond before the popup's status, gold while Anubis is on and hollow while it's off. A second, fainter hairline inside the cartouche, as carved cartouches are drawn, in the popup and the result menu. Each ranking's icon over its name, muted until it's chosen. In Your sites (the popup and Settings), the ending a site shares with others (.org, .co.uk) is muted, and a site with only a tag shows that tag instead of "1 tag". The popup's empty Your sites list shows the balance, level and empty, in grey. The matched rule under Why is split into its options (utils/ruletext.ts) and breaks only after a comma; before, it wrapped mid-word ("tuto" / "rial"). The welcome page's balance swings and settles level as the page opens, and a click on either side presses that pan down to swing again (the owner asked for it to react to something). It holds still with reduced motion.
  • Rejected: a faint gold glow behind the balance, with a ground line under its foot ("too much"). A grain on extension pages' backgrounds, to make the light scheme look like honed stone ("not needed"). Counts in the summary's sentence set in the text colour at 500, to be read at a glance ("no").
  • Checked: unit tests for splitSuffix and ruleParts, including that the parts join back into the exact rule; the popover e2e part checks that the menu shows the rule as written. The checks, responsive, welcome, a11y, mobile, and options parts pass. The regenerated popup, menu, and Your sites screenshots were rendered in a container whose fonts differ from the other screenshots'; regenerate them with node e2e/run.mjs docs on the usual machine to match.

Patterns from Dark Reader (2026-09-29) ​

  • Reviewed: Dark Reader's dynamic style-position watcher batches and deduplicates DOM work; its content-script lifecycle accounts for page freeze and resume. The useful lesson is to bound repeated work and make lifecycle transitions explicit, not to transplant its stylesheet-specific machinery.
  • Adapted: Anubis already batches mutations to one pass per frame. It now disconnects the observer and cancels any queued frame on pagehide, then observes and schedules a fresh pass on persisted pageshow, so a restored page catches up with changes made while frozen. The checks e2e part simulates that lifecycle and asserts both the pause and rescan.
  • Compared with uBlock Origin: its content-script DOM watcher centralises mutation subscribers and disconnects when unused. Anubis has one consumer, so a separate watcher service would add indirection today; extract one if more independent DOM features need the same lifecycle. uBlock's listener-error suppression is deliberately not adopted.
  • Deferred: Dark Reader and uBlock Origin Lite's CSS handler show ways to deduplicate and bound mutation work. Incremental per-result passes could reduce work on busy pages, but Anubis also recalculates cleanup, grouping, filtering, reranking, summary placement, and page statistics. Retain the full pass until profiling and a complete invalidation model justify changing it; do not transplant stylesheet-specific or miss-count heuristics.
  • Compared with Vimium's Firefox build: its unit-test helper and browser DOM tests support the same split Anubis uses: fast rule tests, then fixture-backed browser checks. Vimium's build checks also reinforce checking generated browser artifacts; Anubis already checks the built Firefox minimum in CI. Keep permissions narrow rather than borrowing Vimium's broader host access, which serves a different feature set.
  • These projects point to small, testable patterns, not a reason to replace Anubis's plain TypeScript/WXT structure. Browser fixtures still complement, rather than replace, live engine checks.

Settings on narrow screens (2026-09-29) ​

  • Found (2026-10-08): the Your sites table overflowed at 390px once the AI content list added a tag named "Some AI content". A closed select is as wide as its longest option, so each row's Add tag picker grew with the lists' tag names. The pull request's own CI passed, because the e2e run downloads lists from main. Shipped: cap the picker at 8em; the open list still shows names whole. The responsive e2e part now adds a long tag name itself, so it doesn't depend on what the lists hold.
  • Found: at 320px, the Your sites table forced the whole Settings page wider than the screen. The labelled ranking choices in the Add a site form also wrapped as an accidental run of buttons.
  • Rejected: changing the table to display: block stopped the page overflow, but made site names wrap one character at a time and separated the table columns.
  • Shipped: keep the table semantic and scroll it horizontally inside its own wrapper below 390px; keep its columns together, wrap the labelled ranking choices in a small grid, and put Add on its own line.
  • Follow-up: the original breakpoint stopped at 360px while the table's minimum width remained 390px, leaving the 361–389px range unprotected. The Your sites header also stayed on one line there and could force the page to overflow. Extend the page-width guard, header wrapping, toolbar, table wrapper, and labelled-ranking layout through 389px.
  • Checked: every Settings section stays within the viewport at 320px, 360px, 375px, 389px, and 390px in light and dark schemes. At 390px the sites table fits without scrolling; below that only the table can scroll.

Welcome page ​

Asked for: pinning and the starter lists were only explained in the user guide, which people rarely open before their first search.

  • An academic search (2026-10-20, asked for): the owner asked for an academic search. Offered sleep and memory (pinning PubMed), black holes (pinning arXiv), and the trolley problem (pinning the Stanford Encyclopedia of Philosophy), they chose "trolley problem". Almost everyone has heard of it, and in a search like this, students' notes behind a sign-up wall come first. A Studocu page is first and is the one to hide. The Stanford Encyclopedia is third and is the one the tour pins, "more than someone's lecture notes". The example tags are Course notes, Trusted, and Sign-up wall.
  • Pin Wikipedia, not Reddit (2026-10-20, asked for): the owner didn't want the tour telling people to pin Reddit. Wikipedia's page on noise-cancelling headphones is now third, and the tour pins it as a site you'd trust more than a shop. Reddit moved down to fifth and keeps its Discussion tag.
  • Wording a person would write (2026-10-20, asked for): the owner said the page's text read as written by AI. It explained every mechanic, joined clauses with colons, and used set phrases ("That's all it takes", "You're ready", "on this search and every one after it"). It's now shorter and plainer, in the second person, and says why as a person would ("You'd probably rather hear from real owners on reddit.com, but it's stuck in third"). The rankings keep their names.
  • Headphones, not banana bread (2026-10-20, asked for): the owner said "banana bread recipe" wasn't it: nobody much minds which recipe site comes first. Offered headphones, a health search, and a travel search, they chose "best noise cancelling headphones", where shops and listicles come first and many people already add "reddit" to the search. Reddit is third and is the one the tour pins. Amazon is first and is the obvious one to hide. Wirecutter (nytimes.com, Paywalled) and Wikipedia carry starter-list tags. The example tags are Reviews, Trusted, and Too many ads.
  • One thing to press, and a search anyone makes (2026-10-20, asked for): the tip said "Press Pin" but every ranking worked, and "python list comprehension" only meant something to programmers. While a tip asks for one control, the others it would compete with are now dimmed and do nothing (aria-disabled, so they keep their place in the tab order); step 3 still lets any site not yet ranked be the one to hide, and Close, Skip, and Escape always work. Dimming the whole menu of the site just pinned, while step 3 pointed at the results, looked broken, so a tip that asks for no one control dims nothing. The search is now "banana bread recipe": a recipe site worth trusting is third (bbcgoodfood.com), Pinterest is first and is the obvious one to hide, and NYT Cooking, Reddit, and Wikipedia carry tags from the Paywalls, Discussions, and Reference starter lists. The lists example now shows tags coming and going; with Official docs gone, none of its lists moves a result. The example tags became Recipes, Trusted, and Too many ads.
  • A dot, not a ring (2026-10-20, asked for): the tour ringed the control to press next, but in the menu a ring around a ranking is how the chosen one looks, so a ringed Pin read as already chosen. The next control now gets a dot on its corner (beside the icon, on a ranking's button), like an app's notification badge, whose halo pulses three times; the result's button in step 1 gets the same dot, so there's one sign for "press this next".
  • Wide, and worth staying for (2026-10-20, asked for): in one 760px column the page looked thin on a wide screen, and the practice search, a list of small grey lines, didn't look like a search page; the owner said they'd close the tab. Now: two columns in 1200px, the headline and a checklist on the left (it stays in view as the page scrolls), the practice search on the right, drawn as a results page with a search field, round site icons, addresses, and a line from each page. The headline is two short sentences, "Put the sites you trust first. Hide the ones you don't.", and the lead names Google, DuckDuckGo, and Bing. The checklist, "Try it in three steps", gives a visible goal and ticks each step off, and says "That's all it takes" at the end. Below 1040px it's one column without the checklist (the tips number the steps); on phones results drop their snippet, so the first tip stays on the first screen. Not done: a pointer that plays the steps by itself, as the docs site's RankDemo does, which would show rather than invite.
  • A first introduction (2026-10-20, asked for): the tips still assumed people knew what the button and its rankings were, and the page opened on a large logo and section titles in a side column, with the practice search second. The page is now one column with the practice search straight under a headline that says what Anubis is for ("Choose which sites come first in your search results") and a lead that says it works on your usual search engine and that the practice search saves nothing. The tips now introduce rather than instruct: the first says Anubis adds this button beside every result; the second says what Pin, Raise, Lower, and Hide each do; the third says what just happened (first, raised, or lowered, on every search) before asking for a site to hide; the last points at the summary and Undo and says to search as usual. The docs are third rather than fourth, so step 1's tip is on the first screen of a phone. Checked by keyboard (each step's control takes focus, Got it returns it to the results), off the expected path (another site first, Raise first, Pin pressed twice, Hide first, Normal on an unranked site, which now does nothing), right to left, and at 1440, 1180, 390, and 320px in both themes. Found on the way: closing the menu with its own button lost the focus, because redrawing put the rows back; the redraw now keeps it. While results slid after Hide they covered the tip in the summary for a moment; the summary now sits above them.
  • Tips beside the target (2026-10-20, asked for): the tour's line above the page went unread: it looked like the page's own text and changed out of view. Each tip is now a callout in the primary button's colours with a pointer, placed under the control it's about (the result's button, then the menu, pointing at Pin or Hide) or by the summary (pointing down at the results for step 3, and up at Undo for the last tip, which closes with Got it). A new tip fades in where it lands. The line above the page now only says it's a practice page with tips.
  • Tour and polish (2026-10-19, asked for): the example page wasn't obviously something to press. A three-step tour now sits above it: open the menu beside the official docs (fourth on the page), rank the site, then hide one. Each step reads the page's state rather than demanding an order, so a person who opens another result or presses Raise first is still led on. The next control gets a ring in the text colour that pulses three times, then holds still (still from the start with reduced motion). Skip is quiet, and the tour ends with a line on Undo, Show hidden, Raise, and Lower. Rejected: a dimming overlay or modal coach marks, which block the page and read as a gate. A pinned result now has the search page's frame, around the result and its button but not the menu under it. Tags: "Read later" went (Anubis tags sites, it doesn't keep reading lists); the examples are Tutorial, Trusted (raises), and Paywalled (lowers), with Tutorial on at the start, and their marks show what a tag can do. Lists: Reference starts off, so there's a switch to turn on. Panels: the AI answer is a shaded box under a sparkle (ICON_SPARKLE) above three results.
  • Ranking first (2026-10-19, asked for): the page is now a first impression of ranking. An example search page for "python list comprehension" with six results comes first (demo.ts); each result's button opens a copy of the result menu under it (name, balance, the five rankings, and the hint), and pressing a ranking moves the result as a search page would: Raise and Lower five places a press, Pin to the top, Hide away with Undo and Show hidden. The summary uses the real sentences (summarySentence, changeSentence) and pressing again follows nextLevel. The menu opens under its result rather than floating over it, so it fits at 320px without covering the page. Tags, lists, and removing panels became "More to try": each a short example folded in a <details> (extras.ts), with tags hinted on the main example's results. The starter list wall was cut, leaving a count and Open list settings. The toolbar section is last and optional ("Anubis works without it"). Cut: the clickable balance under the lead (the menu's balance now shows the ranking instead), the "Try a real search" section with engine links (asked to remove), and Raise and Lower buttons that moved a result one place, which taught a different rule from the real five. Checked at 1180, 390, and 320px in light and dark; the welcome e2e part ranks, hides, undoes, and opens each example.
  • Found on the way: setting the balance's tilt inside requestAnimationFrame left it level in headless Chromium, where frames can wait; the demo forces a layout instead, so a just-opened menu still swings from level.
  • Shipped: entrypoints/welcome/, opened by the background script when runtime.onInstalled says install (never on updates, and it needs no permission). It gives this browser's steps to pin the toolbar button, a search to try on four engines, and the lists you're subscribed to with the tags each adds. The search is "python list comprehension", which brings up official docs, forums, and Wikipedia, so three of the four starter lists show a tag. The lists come from storage rather than the directory, so a reinstall that syncs other subscriptions shows those.
  • Pinned or not: Chromium browsers answer action.getUserSettings() with isOnToolbar, and newer Chrome fires onUserSettingsChanged. The page checks on load, on that event and when the window regains focus, and says "Anubis is in your toolbar." instead of the steps once it is. Where the browser doesn't say, the steps stay. The e2e browser can't pin, so only the unpinned state is tested.
  • Not done: browser_action.default_area: "navbar" for Firefox, which would put the button on the toolbar straight away. Firefox's own default keeps new buttons in the Extensions panel, and the steps cover it.
  • Firefox for Android has no toolbar for extensions; the page still shows Firefox's desktop steps there. Fix that when Android is checked (ROADMAP.md).
  • Example results (2026-10-18, asked for): a first section, "See how ranking works", with four sample results for the page's search, each with Raise and Lower, which move it one place (entrypoints/welcome/demo.ts). Only reranking is shown: hiding, tags, and lists were judged too much for a first look, and the page's lists and search sections cover them. It moves only when pressed, like the balance, and holds still with reduced motion. Not tried: a copy of the real ⚖ menu, which would teach the real button but needs the menu's five rankings and its styling outside a search page. The welcome e2e part presses the buttons and checks the order.
  • npm run dev starts with a fresh browser profile, so it opens the welcome tab each time.
  • Too narrow on a desktop (2026-09-29): one 580px column in a wide window read as a phone layout. It now uses the settings page's shape: 1040px, section titles in a 220px column and what to do beside them, the lists two across. Below 900px it's one column again. Checked at 1920, 1180, 820, and 390px.

Translation ​

  • Vietnamese (2026-10-14, asked for): added as locales/vi/messages.json with its review skill (.claude/skills/review-vi), written first so the translation followed its glossary. "Tag" is nhãn, not thẻ, because Chrome, Firefox, and Google call a browser tab thẻ. Vietnamese has only the other plural form, so the 41 _one messages aren't needed; each _other reads right for 1. Google's and Firefox's Vietnamese names couldn't be checked from the cloud session. Still a machine translation.

  • Turkish and Traditional Chinese reviewed (2026-10-13, asked for): Turkish had about a third of its messages translated from other text than today's English: syncFirefox was just "Firefox Eklenti Senkronizasyonu", webdavEncrypted one short sentence, deeperTipMany "$1 pages loaded", and popupHintLists, tagEffect*, and choiceRaise* said something different. sources.json still recorded them as fresh, so locales.mjs status and the tests passed: they check keys, placeholders, and records, not meaning. A length ratio against English (under 0.4 or over 2.2 for messages over 60 characters) flagged 26 of 91 in Turkish and none in the other fifteen; it only finds gross mismatches, so Turkish was retranslated in full. Traditional Chinese matched English in meaning but was mainland wording in Traditional characters (加載, 文件, 菜單, 視頻, 導入, 倉庫, 地址) with leftover Simplified (仅, 它们, 復製, 合並); it now uses Taiwan wording (載入, 檔案, 選單, 影片, 匯入, 儲存庫, 位址) and the Firefox names the skill lists. Turkish placeholders sit in built sentences without suffixes ("$1 tanesini yükseltir", "Kaynak: $1") because vowel harmony can't be applied to a name filled in at run time. Both are still machine translations.

  • Turkish (2026-10-09, asked for): Turkish added as locales/tr/messages.json with standard direct register (sen), fixed glossary, curly quotes, dedicated review skill (.claude/skills/review-tr), and complete 572-message coverage.

  • Traditional Chinese (2026-10-09, asked for): Traditional Chinese added as locales/zh_TW/messages.json with Taiwan/Hong Kong standard vocabulary (釘選, 擴充功能, 搜尋, 清單, 伺服器, 資料, 預設, 支援, 復原, 分頁), a dedicated review skill (.claude/skills/review-zh-tw), and unit list join test coverage.

  • Ten more languages (2026-10-09, asked for): Arabic, Bengali, Chinese (Simplified), Hindi, Indonesian, Italian, Japanese, Korean, Russian, and Urdu, machine translated as before. One agent drafted each language and wrote its review skill (.claude/skills/review-<lang>); a second read the draft against the skill. The first six had a full read of every message, which changed 3 to 8 messages each (Firefox's own names, checked against Mozilla's translations; built sentences; a misreadable phrase). The last four had a cheaper check of built sentences, plural forms, names, and punctuation only, which found one error (Urdu). Google's names for its panels couldn't be checked: Google is unreachable from the cloud sessions.

  • Code the new languages needed: facts joined as a unit list ran together in Chinese ("120 条指令3 个标签") and were only spaced in Japanese, Korean, and Russian; tJoin now adds the language's comma there. Chinese and Japanese put no space between sentences, so the summary's two sentences, the hidden line's parts, and the machine-translation note use gap(). "Updated never" read badly in most languages and only stood beside "not downloaded yet", so it's gone.

  • Right to left: Arabic and Urdu turn Anubis's pages, and its elements on search pages (dir on each host), right to left. The CSS uses start and end instead of left and right; the switch and the select's caret are mirrored by hand. Chrome's @@bidi_dir said "ltr" with an Arabic interface, so Settings stayed laid out left to right; the direction now follows the messages' language. A list's own description, usually English, sets its own direction (dir="auto"), or its full stop lands on the wrong side. Seen in Settings and the popup in Arabic; responsive passes in Arabic, Chinese, Japanese, Russian, and Hindi.

  • A translation can stop the extension loading: the Chinese draft had "$1$2", which Chrome reads as a named placeholder $1$ it doesn't know, and then refuses the whole extension (web-ext lint warned with MISSING_PLACEHOLDER). tests/i18n.test.ts now fails on it.

  • Left: counts inside sentences without plural forms ("raises it by $1" gives Urdu "1 درجے"); a second count in one message (importRead's "$3 updated") can't agree; Chrome has no Urdu interface.

  • Reviewed against English (2026-10-09, asked for): a project skill per language (.claude/skills/review-de, review-fr, review-es, review-pt-br) sets its register (du, vous, tú, você), typography, glossary, the names Google and the browsers use in it, and what machine translation gets wrong there. With them, all messages were read side by side with English, built sentences filled in. Fixed: French spaces before « : ; ! ? » and inside guillemets, and between numbers and units, were plain, so a line could start with « : » (they're no-break spaces now; 91 messages); Spanish said "ordenadores" (Spain only), and the summary's "fandom.com oculto." read as a caption, not a sentence ("Se ocultó fandom.com." now); Portuguese mixed "guia" and "aba" for a tab; German's "Ihre Einstufung" read as the formal "your", and a list was "es". About 25 meaning and grammar fixes in all; most messages were already right. Still not read by a speaker, so the notes stay.

  • Found in the code: the line for a run of hidden results, "fandom.com and 2 more hidden by your list", reused the one-result text, so French, Spanish, and Portuguese said "masqué", "oculto", "oculto" for several. The barHidden* messages now have plural forms, counted by the results the line stands for; English gains "hidden because they’re tagged" for a run.

  • Left alone, as style: French « Gardé normal », Spanish "petición de permitir anuncios", Portuguese "uma pull request", and the German double "von" in "von 12 Ergebnissen von 2 Seiten".

  • Machine translations shipped (2026-10-09, asked for): German, French, Spanish, and Brazilian Portuguese, all 568 messages, machine translated with a fixed glossary: the rankings (Ausblenden, Abwerten, Normal, Aufwerten, Anheften; Masquer, Rétrograder, Normal, Promouvoir, Épingler; Ocultar, Bajar, Normal, Subir, Fijar; Ocultar, Rebaixar, Normal, Elevar, Fixar), "tag" and "list", and each engine's own names for its panels (Google's "Übersicht mit KI", "Aperçu IA"…). Sentences built from parts were reshaped per language rather than translated part by part ("Official docs: 51 aufgewertet").

  • Why not unreviewed and untracked: a translated file keeps its old text when the English changes, so people would read an outdated meaning, not English. Translations moved out of public/ to locales/<lang>/, beside sources.json, the English each message came from; the build's build:publicAssets hook ships only messages whose English is unchanged, and a stale one falls back to English. A test fails on a translated message with no record. Considered: failing CI on stale messages, which would block every English change on four languages.

  • Says so everywhere: Settings (above every section), the welcome page, and the popup show "Machine translated." with a warning to use it with caution and a link to Help translate; the README, Introduction, Getting started, Help translate, and the store description say the same. Not shown in English.

  • Layout: responsive passed in all four languages at 320 to 390px (ANUBIS_LANG). The ⚖ menu's five rankings didn't fit in German or French ("AusblendenAbwertenNormal…" ran together): the row is now five equal columns whose words wrap, and the long ranking words carry soft hyphens, since hyphens: auto did nothing in the test browser. Anubis's elements on search pages now carry the interface's lang, not the page's, for hyphenation and screen readers.

  • Not checked: by anyone who speaks the languages; right-to-left; search pages in a translation beyond the menu and the summary.

  • Ready for translators (2026-10-08): the rest of the interface moved into messages: Settings (about 200 strings), list errors (utils/listformat.ts), the result menu's reasons, the names of the panels clean-up removes, the theme switch, download and backup errors, and relative times (tAgo, from Intl.RelativeTimeFormat, so "5 minutes ago" where it said "5 min ago"). Every message now has a description for translators (93 older ones had none). New helpers: tParts puts elements (code, a link, bold) in a message's placeholders, and tJoin(…, 'unit') joins facts like "34 instructions, 3 tags". The result menu's reasons are translated, but each also keeps an English report, since issues go to a list's maintainers in English. Kept in English on purpose, under a comment saying so: those issues and the start of a list file. Words matched on search pages stay as the engines write them.

  • Guards: tests/i18n-coverage.test.ts parses the code with @babel/parser (TypeScript 7 has no JavaScript API) and fails on text-like strings outside the messages, on HTML text without data-i18n, on a message without a description or that nothing uses, and on a stray $. tests/setup.ts installs English for every unit test. A test in a made-up bracketed language checks that reasons follow the interface and reports stay English; it found that a translation with a malformed langCode threw from Intl on every page, so lang() now falls back to English. localizePage() sets dir from the browser's @@bidi_dir.

  • Found on the way: welcomePinAndroid existed but was never used, so Firefox for Android was shown the desktop toolbar steps. It shows the Android line now.

  • Longer text: with the built English swapped for a pseudo-translation (accented letters, about 40% longer, one 25-letter compound per message), Settings and the popup overflowed at 320 to 390px in four places: the choice rows (Auto / Light / Dark, Remove / Collapse / Dim), Your sites' ranking row, the popup's Add a site buttons, and Settings at 390px, where main could grow past the screen. Choice rows, the ranking row, and the popup's buttons now wrap; main never grows past the screen, and only the sites table scrolls sideways, at any width. English looks as before (the responsive part, and the same measure on English). Left: the Load more results row at 320px, only with a made-up doubled word. The pseudo-translation isn't in the repository: the e2e parts find controls by their English names.

  • Tried: WXT's @wxt-dev/i18n module. It's typed and reads YAML, but its README says its plural forms don't support languages with separate "few" or "many" forms (Arabic, Polish, Russian…), and it adds three dependencies.

  • Shipped: the browsers' own _locales/<language>/messages.json format, which translation tools read as they are, with a small helper (utils/i18n.ts). Keys are type-checked against the English file. Counts use Intl.PluralRules with keys like popupListCount_one and popupListCount_other, falling back to _other. A langCode message gives the language the text is actually in, for the page's lang attribute, since a missing translation falls back to English.

  • WXT types getMessage with one overload per key, which a key held in a variable can't satisfy, so the helper calls it through a looser signature.

  • The fake browser in unit tests has no i18n; useEnglish() in tests/english.ts answers from the English file.

  • The summary's buttons (2026-09-29) now use the popup's messages (showHidden, loadMore…), so the two can't drift apart: the page's Load more results tooltip had its own wording. The cog's label, shared by the popup, the summary, and the result menu, lost its popup prefix (anubisSettings).

  • The summary sentence (2026-09-29) read "Anubis raised 1 and hid 2 of 7 results, and removed an AI answer, a video panel…": two "and"s in one sentence, the second after a comma, so the clean-up part read as tacked on. What clean-up removed is now a second sentence ("… of 7 results. It also removed an AI answer, a video panel…"); on its own it stays "Anubis removed a question list." The sentence moved into messages on the way: each shape has its own message (summaryActed, summaryAlsoRemoved, summaryRemovedOnly, summaryUnchanged, summaryFiltered), counts use plural forms, and lists are joined by tJoin with Intl.ListFormat. Plain en joins "a, b, and c"; the English text is British, so English lists use en-GB, "a, b and c", as andList did. tests/english.ts answers getMessage from the English file for any test that needs it.

  • The serial comma (2026-09-29) replaced that choice the same day: lists of three or more now take a comma before the last "and" or "or" ("Hide, rank, or tag"), in the interface, the wiki and the repository's own docs. tJoin uses plain Intl.ListFormat for the language again, andList adds the comma, and STYLEGUIDE.md states the rule. Quotations of earlier wording in this file keep their original punctuation.

Wording, icons, and the motif ​

  • The summary's mark is gone (2026-10-08). Asked for from use: the Anubis head before the summary's sentence went, on search pages and in the docs' demos. The summary is plain text now, which suits "stay quiet on search pages"; the motif stays in the logo and the result menu's balance.

Feedback from use: "weigh" was too ambiguous for the functions people rely on ("Weigh deeper", "Weigh a site", "Weigh this site"), the settings button's icon read as a sun, and the Anubis logo on every result said who made the button, not what it does. The motif (the balance in the menu, the cartouche) was liked; it was the words and icons that got in the way.

  • Inspiration: Scott Jenson's talk "Are we really going to use the same Desktop UX forever?" (KDE Akademy 2026) treats UX as layers (style, structure, strategy, technology) and argues for tools shaped around the task in front of you rather than around the software. Here the style layer (the Egyptian theme) had leaked into the structure layer (the names of functions). The ux-heuristics skill (Krug's Don't Make Me Think, Nielsen's heuristics) was installed in .claude/skills/ for the review. It flags this exact pattern: clever names lose to clear names, and icons without labels make people guess ("mystery meat navigation").
  • Changed: "Weigh deeper" is now "Load more results" (and "Loading…"), and "Look deeper automatically" is "Load more results automatically". "Weigh a site" is "Add a site". The per-site choice is called its ranking everywhere (Hide, Lower, Normal, Raise, Pin). The button on each result shows up and down arrows with the label "Hide, rank or tag this site". The summary's gear is now a text button, "Settings". The fallback summary "Anubis weighed 9 results" is now "Anubis left all 9 results as they were".
  • Later: the Settings buttons (in the summary, the result menu, and the popup) went back to an icon on request, this time a toothed cog (Lucide's "settings" icon) rather than the earlier circle with rays, which read as a sun. A cog is one of the few icons almost everyone recognises; each has a label for screen readers and a tooltip.
  • Kept: the balance and cartouche in the menu, the logo as the summary's mark (it says the line comes from Anubis), and the myth in the README.
  • Considered: a "⋯" button for the result menu. Rejected because Google and DuckDuckGo already put their own "⋮" menu on each result, and two lookalike menus would be confusing.
  • The button on each result (2026-09-29): the up and down arrows only said "move", and the project owner asked for something better. Four Egyptian-themed glyphs were drawn at their real 15px on light and dark mock results: the balance, a balance that tips with the site's ranking, an upright cartouche, and Ma'at's feather. The owner chose the balance, tipping with the ranking but without colour, and asked for a pin on pinned sites and something else for hidden ones. The button now shows the balance level for Normal, the site's (left) pan down for Lower, and up for Raise, as the menu's balance tips; a pinned site shows the ranking's pin and a hidden one its crossed-out eye. Its label adds the ranking ("Hide, rank or tag fandom.com (lowered)"), since the tilt is a state. The cartouche was hard to recognise at that size, and the feather already stands for Normal and can read as "edit". Docs now call it the ⚖ button.
  • Also considered: Vercel's web-design-guidelines skill. Not installed, because it downloads its rules from the network on every run.

Toolbar icon when off ​

  • Turning Anubis off now swaps the toolbar icon for a grey copy (public/icon-off/) and sets its tooltip to "Anubis is off". The grey icons were made once from the colour ones with a canvas in Chromium: luminance, flattened, 75% opacity, so they read as "off" on light and dark toolbars. The icon is set every time the background script starts, because the browser forgets a changed icon on restart.

Design ​

  • First pass (rejected by the project owner as loud and "a bit like Discord"): filled pill badges with coloured dots, gradient gold buttons, and segmented controls, ALL-CAPS section labels, rounded cards everywhere, a bordered summary with stat counters.

  • Second pass, following Anthropic's frontend-design skill (now in .claude/skills/): on search pages Anubis uses the page's own font and muted text; tags are a small diamond and a name; the summary is one sentence; hidden results are one line. The one flourish is the weigh menu: the site's name in a cartouche (the oval that encloses names in hieroglyphs) over a small balance that tilts with the chosen weight. Settings use rows and hairlines; the light theme is a cool stone grey instead of cream; tag colours are muted Egyptian pigments.

  • Consistency pass and a style guide (2026-09-29): STYLEGUIDE.md now writes down the palette, type scale, radii, controls, states, and wording. Differences found and removed on the way: the result menu's light scheme was warm (#fbfaf8 card, #6f695e muted text) while the popup it's meant to match was cool stone, and the dark hairline was #36322b against #35312a, so shadow.css now carries the same tokens under the same names as theme.css (--text, --raised, --line-strong); small print came in 12px and 12.5px, now 12.5px; the popup's sentence was 13.5px, now body size; selects used the browser's arrow everywhere except the cartouche, now all use its small caret; a tag filter's underline was 1.5px against 2px for every other choice; Hide chosen in the popup was underlined in gold, in the menu and settings in red, now red; the menu's new-tag field was 28px with a faint border, now an input like the others; the logo was rounded in CSS on top of its own rounded tile; the settings tab's title was "·"-joined.

  • The cartouche's bar (2026-09-29): the name sat in a gold oval with a short bar 3px off its right end, the tie at the end of a real cartouche. At this size it read as a text cursor, and the project owner asked what it was. Tried touching the oval at full height, and taller than the oval: both still read as a cursor or a stray line. Dropped; the oval alone carries the motif.

  • The cartouche's name was off centre (2026-09-29): a select is as wide as its longest option, so wikipedia.org sat left in a box sized for en.wikipedia.org, with a gap before the caret. The name is now text with the caret after it, and the native select lies unseen over the whole oval (it still opens the browser's own list and works from the keyboard; the oval shows its focus ring through :has(select:focus-visible)). With one choice there's no select at all, where before a disabled one greyed the name. Choosing another part of the site keeps focus on the picker; before, it jumped to Hide. The popover e2e part switches developer.mozilla.org to mozilla.org from the keyboard.

  • The popup changes with the tab (2026-09-29): the popup showed the same four sections everywhere, and gave the most room (and the only gold button) to typing a domain by hand, the rarest thing people open it for. It had a dropdown for the ranking where the result menu has a choice row, three unlabelled theme icons next to the on/off switch, and × to forget a site with no undo. Three layouts were drawn: a list of every site Anubis acted on in the page's results, with the reason (needs the content script to report per-site verdicts); one "Find or add a site" field at the top; and a popup that changes with the tab. The project owner picked the last. On a search page it shows the summary, its buttons, and the tags to show only (the set-filter message the summary already used); on another site, the result menu's cartouche, balance, rankings, hint, and tags, worked out in the popup with evaluate() on the tab's address; elsewhere, Add a site opens by itself, with Hide, Lower, Raise, and Pin as buttons instead of a dropdown and an Add button. The theme moved to Settings only; forgetting a site moved there too, and the footer's list count opens Settings → Lists. The balance moved to utils/balance.ts so both draw the same one. Mockups of the three are not in the repository.

  • Clean up settings read the wrong way round (2026-09-29): the page listed nouns ("AI answers", "Videos") each with a switch, all off, so "AI answers: off" could read as AI answers already turned off. The project owner found it unclear. The list now sits under "Remove from every search" with one line saying on removes and off leaves it, the intro says to turn on what you'd rather not see, and labels that only named a topic say which part of the page goes ("Video panels", "Discussion panels", "Image rows"); "Discussions" also clashed with the Discussions tag. The Google switch's heading is "On Google" and its hint starts with what it does. Not tried: "Remove …" on every label, which repeated the verb seven times.

  • "Share and back up" was too long for the settings sidebar (2026-09-29): it wrapped onto two lines. The sidebar now says Backup, the most common reason to open it, and the page's title names all three things it does: "Back up, import and share". The address stays #share, since the guide and earlier builds link to it.

  • Tagging sites from Settings → Tags (2026-09-29): a tag's row only had its colour, an inline name field, what it does, and Shown, so the only way to tag a site was the ⇅ menu on a search result, and a tag's sites weren't visible anywhere. The project owner asked to add sites to a tag and edit it from there. Each row now has Edit, which opens the tag's name (a labelled field, where before the name was an input that only looked like one on hover), its description for your own tags, your sites with the tag (× untags), a field that tags one or more sites, and up to eight sites from each list that gives the tag. Open tags stay open when the page renders again after a change, and the cursor goes back to the field, so several sites can be added in a row. At phone width a row's controls now wrap under its name; the name was cut to one letter.

  • Saying what a tag does (2026-09-29): a tag's row read "Most articles need a subscription. From Paywalls, on 23 sites.", which said what the tag means but not what it does; the project owner took Paywall to lower sites, when the Paywalls list only labels them. Each row now opens with a sentence worked out from the tag's setting and, on "Follow the lists", from the lists' own rules: "Marks 23 sites from Paywalls. Only a label: their ranking stays the same.", "Marks 60 sites from Official docs. Official docs raises 51 of them." The tag's description follows in small print. Paywall's description now says which sites it marks. Tag names were left short, since they're also the labels under results.

  • Plain colours on search pages (2026-09-29): the project owner asked for a way to make what Anubis adds to search pages plainer in colour. Settings → Appearance → Colours on search pages now has Gold (the default) and Plain. Plain swaps the tokens rather than each rule: gold becomes the muted grey or the text colour, red becomes grey, tag marks turn grey, and the pinned frame and highlights take the page's text colour. Tags stay distinguishable by name, and what you can press keeps its weight. Settings and the popup stay gold, since the request was about search pages. Not tried: separate switches for tags and gold, which would give two settings for one wish.

  • Style guide redone with examples (2026-09-29): screenshots from the user guide, h() snippets for each control, a table of wording to use and avoid, and the summary as its own section. Checking the code against it found two classes that did nothing: .btn.ghost (Disconnect in Sync) and .danger on a .btn (Reset settings) had no CSS. Disconnect is now a plain button, and .btn.danger exists: red text, a red border on hover. The focus ring had 3px corners on search pages and square ones on extension pages; both are 3px now. Keyboard and screen reader guidance moved out to ACCESSIBILITY.md, which the guide links.

Released under the GNU AGPL v3.