fix: improve <title> tag of dashboard

[kerbo7]

the current title tag is:
<title>Freenet — Local Peer</title>

Problem

• the dash is an "EM Dash" which looks overly long on the browser tab
• usually there are a lot of open tabs and you don't see the full tab title
• therefore it should be short and concise and the beginning counts.
• "Freenet ..." as a beginning can be anything, you dont know what it is, if you just see the first 4 chars

Solutions

<title>FN Peer</title>

or just

<title>Peer</title> // The favicon makes it clear what peer it is

or

<title>Dashboard</title> // The favicon makes it clear what dashboard it is - and Dash as a beginning is definitive

bad: starting with freenet:
<title>Freenet ....</title>
bc. on a squeezed narrow tab you have no idea what it is. could be Freenet home page

Source

freenet-core/crates/core/src/server/home_page.rs

Line 46 in a085374

<title>Freenet — Local Peer</title>

[github-actions]

🤖 Auto-labeled

Applied labels:

• T-enhancement (95% confidence)
• E-easy (90% confidence)

Reasoning: The report requests a small UX improvement to the dashboard <title> tag in a single source file (home_page.rs). This is not a bug or new feature but an enhancement. The change is localized and trivial (rename/change a string), so effort is 'easy'. No other areas from the schema match UI/dashboard better than developer-experience related code, so A-developer-xp was chosen with moderate confidence.

Previous labels: none

If these labels are incorrect, please update them. This helps improve the auto-labeling system.

[sanity]

Issue Priority Assessment

Generated: 2026-03-12T22:22:17.078462919+00:00
Issue hash: 29165fbc

Value Assessment

The dashboard HTML still hardcodes <title>Freenet — Local Peer</title> in crates/core/src/server/home_page.rs:46, so the issue remains relevant: the reported tab-title problem hasn’t been resolved and the code hasn’t drifted away from the described rendering path, so the dashboard will keep opening with the same EM dash title as of the current tree.

Every Freenet node instance serving this page opens in the user’s browser with that long, Freenet-first label, so anyone who keeps many tabs open is still at a disadvantage identifying the local peer’s dashboard quickly; the favicon/column is helpful but the dashboard title itself is what shows once the tab is collapsed, so a short prefix like “Dash” or “Peer” improves discoverability for all running nodes rather than just a niche case.

Tweaking this title is a trivial change in the HTML template, so there’s no dependency on other work and it doesn’t block anything else; it simply removes a small usability friction and keeps the dashboard UI polished, which aligns with ongoing efforts to keep the node interface clean and approachable.

There’s no deadline pushing this change, so it can sit in the backlog until someone is working around that snippet, but because the fix is quick it’s worth grabbing when touching other dashboard markup.

Cost Assessment

crates/core/src/server/home_page.rs still constructs the dashboard HTML that drivers the public web UI, and the <title>Freenet — Local Peer</title> string is still hardcoded near the top of homepage_html(), so the issue’s premise remains actionable—no refactor or redesign of the rendering stack has happened that would invalidate the approach. The work boils down to choosing one of the suggested replacements and updating this single template, maybe also keeping CSS/JS unchanged; there are no downstream templates or data models to touch.

Because the change only touches this one constant, the implementation scope is trivial—just one file and no branching logic—so the cost is in the “easy” category. There are no tricky edge cases: the title is static and served to every HTTP GET / request, so switching the literal to FN Peer, Peer, or Dashboard is straightforward string editing. No additional dependencies, approvals, or configuration changes are needed, and the favicon already distinguishes the dashboard origin so the shorter text isn’t ambiguous.

Regression risk is nearly zero because the UI is otherwise unchanged; the only thing that might break is if some script relied on the old title text, but nothing in this module hints at such coupling. Since the change is purely presentation, automated testing isn’t needed beyond standard smoke checks—the existing integration tests (if any) won’t fail because page titles aren’t asserted. Given all of that, the overall implementation cost is minimal: a quick edit, no extra builds, and no new tests.

---

Generated by issue-prioritizer