Skip to content

CHANGELOG.md

Latest commit

 

History

History
132 lines (111 loc) · 7.92 KB

CHANGELOG.md

File metadata and controls

132 lines (111 loc) · 7.92 KB
Raw

Changelog

All notable changes to SearchMob are documented here. The format is based on Keep a Changelog, and the project uses Ubuntu-style date versioning (YY.MM.VV).

[26.06.00] - 2026-06-02

Added

  • Personalized ranking that learns from your clicks. SearchMob can now quietly move the sites you tend to click higher, and it gets better the more you search. It learns on-device from a position-bias-resistant "clicked over skipped-above" signal, applies a bounded boost (so engine consensus stays primary and your pin/raise/lower/block rules always win), and includes exploration, a cold-start gate, and time decay so it never collapses result diversity or acts on weak evidence.
  • Opt-in, recommended, and private. Off by default, offered as a recommended step in the setup wizard and a toggle on the Result ranking settings page. What it learns is encrypted on your device, never leaves it, and is never trained by, nor applied for, other people on your network. You can export, import, and reset the learned model; the format is shared with SearchMob Desktop, so you can move it between devices.
  • Learns from the served browser page too. Clicking a result from a browser search through the local server trains the model the same way the in-app results do, through an owner-only redirect that only ever sends you to the result you clicked. Network clients get plain links and are never tracked or personalized.
  • Setup wizard re-appears once after a feature update (framed as "what's new") when an update adds a new opt-in setting, so existing users discover it instead of only fresh installs.

[26.05.05] - 2026-05-31

Added

  • Search verticals: Web / News / Forums / Academic category tabs, in the app and on the served page (?vertical=). Each is a scoped site: search over the same engines with a sensible default sort; no new third-party API.
  • Settings in the browser: an owner-only (loopback) Settings page on the served server mirroring the app — default sort, AI-slop filter, Wikipedia summary, suggestions, full domain-rule and scope management, Goggles import, and search-history view/clear.
  • Sample scopes installed by default (no "add them" step); the scope selector appears in the app before a search and on the served home page.
  • Link to the desktop app from the About screen.

Changed

  • The URL tracker-stripping list now matches the desktop app (adds mc_cid, _hsenc, _hsmi, ref_src, yclid).

Fixed

  • Network mode is now authenticated. When network mode is on (binding all interfaces), off-device clients must present a per-install access token to reach the search routes, the Host header is checked against a DNS-rebind allowlist, and every response carries Referrer-Policy: no-referrer (plus X-Content-Type-Options/X-Frame-Options) with rel="noopener noreferrer" on result links. Loopback (the device's own browser and all in-app use) is unaffected.
  • Parity fixes: the served browser route now honors your saved default sort on the Web vertical; the in-app empty-results state keeps the "did you mean" suggestion; the contextual Wikipedia summary card now appears in the in-app results too (was served-page only).
  • Accessibility: served pages declare <html lang>, search inputs and the Sort/Scope selects have accessible names / associated labels, the vertical bar is a labeled nav with aria-current on the active tab (and a contrast-corrected active chip), plus a focus ring and reduced-motion support; the "did you mean" banner and the Wikipedia card now announce correctly in TalkBack.
  • The bundled AI-slop blocklist load is now size-bounded against a corrupt/oversized asset.

[26.05.04] - 2026-05-29

Added

  • Contextual Wikipedia summary box. For entity-like queries, a short knowledge-panel card from the related Wikipedia article now appears above the results, both in the app and on the served page (title, description, lead extract, link). Fail-soft and confidence-gated; adds at most one extra request to Wikipedia (already a search engine here) through the privacy proxy. Toggle in Settings.
  • Personalization controls in the browser. The served results page now offers the same scope/ranking tools as the app: per-result Block / Lower / Raise / Pin by domain and a scope selector. Edits persist to the encrypted store and apply on the next search. The editing routes are loopback-only (a device on the network can search but cannot change the owner's rules) and are same-origin guarded against CSRF.

Fixed

  • Result links are stripped of tracking parameters before you tap them. The tracker list (utm_*, fbclid, gclid, ...) was only applied to de-duplication; the surfaced link now drops trackers too, in the app and on the served page.

26.05.03 - 2026-05-28

Added

  • Typo and "similar sounding" correction. A misspelled query now surfaces a "Did you mean" suggestion, taken from the upstream engines' own correction when they offer one, otherwise from a fully on-device corrector (Double Metaphone phonetics + Jaro-Winkler/Damerau edit distance over a bundled dictionary, enriched by your own search history). No new outbound calls.
  • Result personalization ("filter bubbles"). Raise, lower, pin, or block any site from an inline menu on each result; scope searches with named lenses (include/exclude domains and keywords); and import a subset of Brave Goggles rule files. All rules are stored encrypted on-device, applied locally to results, and can be exported/imported as JSON.
  • Kagi Search API engine as a bring-your-own-key option, alongside the existing Brave and Mojeek API engines. The key is stored encrypted at rest.
  • In-app search history. View saved queries with their time, delete individual entries or clear all, and export/import history as JSON for moving to a new device (Storage Access Framework; no storage permission required).

Changed

  • Encrypted storage is now wired into the live app. Search history (SQLCipher) and BYO API keys (AES-256-GCM) are persisted encrypted at rest via a process-wide store shared by the UI and the foreground service. Bring-your-own keys now also take effect on the browser-facing /search, not only the in-app search.

Security

  • While network mode is on (the search server is reachable by other devices on the network), the /suggest endpoint no longer serves your local search history as autocomplete, so your history is not exposed to other users on your network. History recording, viewing, and export are unaffected. (Browser/network searches were never recorded to begin with; only your in-app searches are.)

Fixed

  • The OpenSpec specs for the implemented work were archived and the encrypted-storage wiring landed with a fix for a main-thread database access and a now-shared history store made thread-safe.

26.05.02 - 2026-05-28

Added

  • Browser-consumable OpenSearch suggestions endpoint (/suggest), sourced from local encrypted history with an explicit, default-off opt-in to upstream (DuckDuckGo) autocomplete via the privacy proxy.
  • Opt-out launch-time update check against GitHub Releases (on by default, routed through the privacy proxy, throttled to about once a day), with a Settings toggle.

Changed

  • Toolchain bump (Kotlin/AGP/Gradle, compileSdk 36). New launcher icon and onboarding/setup polish.

26.05.01 - 2026-05-28

Added

  • First published release: the private, always-on metasearch app (foreground service + loopback HTTP server + OpenSearch descriptor), metasearch over free engines with the privacy proxy, opt-in network mode (LAN/Tailscale) behind a warning, and security-audit hardening.