Build Nyxt Guard settings and configuration page #5

New issue

Open

opened 2026-09-11 05:16:47 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-09-11 05:16:47 +00:00

(Migrated from github.com)

Parent: #1
Depends on: #3, #4

Goal

Provide an internal Nyxt page for configuring Nyxt Guard without editing source files.

Scope

Show global blocker enabled state and engine status.
Manage filter-list subscriptions: add URL/path, enable/disable, update, remove, inspect errors, and show rule counts/last update.
Edit custom user rules/filters.
Configure per-site exceptions and dynamic rules.
Configure update behavior and persistence locations.
Show diagnostics/provenance for active lists and recent parse/update failures.
Reserve a clearly separated section for the optional LISA expert blocker once that issue lands.

UX constraints

This is a Nyxt internal page, not an external web service.
Changes should be applied through the same stable engine/config API used elsewhere.
Do not make the page itself authoritative storage; persisted config remains the source of truth.
Destructive actions such as removing a list should be explicit and reversible where practical.

Acceptance criteria

A user can add a remote ad/filter list entirely from the UI and see whether it loaded successfully.
List enable/disable state persists across restart.
User rules and site exceptions can be edited from the page.
Engine/list errors are visible instead of failing silently.
The page reflects changes made through programmatic/config interfaces as well as changes made in the UI.

Parent: #1 Depends on: #3, #4 ## Goal Provide an internal Nyxt page for configuring Nyxt Guard without editing source files. ## Scope - Show global blocker enabled state and engine status. - Manage filter-list subscriptions: add URL/path, enable/disable, update, remove, inspect errors, and show rule counts/last update. - Edit custom user rules/filters. - Configure per-site exceptions and dynamic rules. - Configure update behavior and persistence locations. - Show diagnostics/provenance for active lists and recent parse/update failures. - Reserve a clearly separated section for the optional LISA expert blocker once that issue lands. ## UX constraints - This is a Nyxt internal page, not an external web service. - Changes should be applied through the same stable engine/config API used elsewhere. - Do not make the page itself authoritative storage; persisted config remains the source of truth. - Destructive actions such as removing a list should be explicit and reversible where practical. ## Acceptance criteria - A user can add a remote ad/filter list entirely from the UI and see whether it loaded successfully. - List enable/disable state persists across restart. - User rules and site exceptions can be edited from the page. - Engine/list errors are visible instead of failing silently. - The page reflects changes made through programmatic/config interfaces as well as changes made in the UI.