max / makenotwork

Describe the public profile, so a screen says its feed The second of the three pages that wrote `<link rel="alternate">` by hand. `/u/{username}` is a described document now: `templates/pages/user.html` and `UserTemplate` are gone, and the route stays the axum handler it was, for the reason `project_blog` states. Three things the page needed that the vocabulary already had: - `Document::styled` for the creator's Tier 0 theme. The template injected an unlayered `<style id="creator-theme">` so it would outrank every named layer, and that member writes the same sheet last in the head and outside the layer statement. Nothing keyed off the id. - `Act::copies` for the share link, which is what `data-copy-link` meant. The value is absolute now, since a relative path on a clipboard is not an address. - `Discovery` for the whole `{% block head %}`, minus the JSON-LD, which goes in through `Shell::with_head` rather than growing the vocabulary a member for one tag on three pages. The follow control was written three times, and is now written once. `src/quasi/follow.rs` holds it, both pages take it from there, and `routes/api/follows` answers a press with the same node, so the answer cannot disagree with the page that drew it. `follow_button.html` and `FollowButtonTemplate` go with it. What did not survive is `.follow-btn.is-selected`: the vocabulary has no latched control, and the label already says which state the button is in. `src/quasi/tip.rs` describes the tip offer both public pages carry. The disclosure is `Slot::showing_at_most_one` rather than `toggleTipForm`, and the hidden `_csrf` goes the way the reset token did, since `create_tip_checkout` already reads the token header-first. `_hyperscript.min.js` is vendored. `Shell::under` links it on every described document and this server never served it, so the file 404'd once per page and every disclosure and tab strip a screen could draw was inert.