AIDEV Production Bot pushed new project branch ai/1670-voters-dialog-weight-text-is-s4dd8bf73-v1 at hive / denser
AIDEV Production Bot (945b5b71) at 18 Nov 06:38 Fit voter weights in the three-column voters dialog (#1670) ... and 400 more commits
Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.
AIDEV Production Bot (945b5b71) at 18 Nov 06:38 Fit voter weights in the three-column voters dialog (#1670) ... and 400 more commits
Intake review — the denser tech lead Filed by dan, a follow-up to #1668 (closed)/#1669 (closed). My #1668 (closed) live check measured dialog overflow and row height but not text truncation inside a row, which is how this got past it. Files: apps/wallet/components/voter-row.tsx and voters-panel.tsx exist on aidev/integration. The fix is in the row layout and the weight formatting. Scope: keep #1669 (closed)'s "votes via @proxy" rows and its shares, and the one-line 40 px rows. Conflicts:…
Problem Follow-up to #1668 (closed) and #1669 (closed) (shared voters dialog). On the integration site at 1280x900, the 3-column desktop layout truncates the longest weight texts with an ellipsis. For example: blocktrades: "16.82M HP + 16.60M p…" (proposal #373 (closed)); steemmonsters: "1.23M HP + 8.52K p…"; livinguktaiwan: "278.33K HP + 9.31K …"; showerthoughts: "0.00 HP + 249.19K …". The full values are only in the title. On phones (1 column) they fit. Required behavior In the 3-column…
Intake review — the denser tech lead Filed by the lead from the pre-promote review of #1622 (closed) (review 80586, low finding). implement+bug fits. It changes stack/integration/caddy/Caddyfile.bot-gate, which #1622 (closed) adds (landed on session/denser-simple as 299bb593, promote promote-session-denser-simple-1794562680 in progress), hence Depends-On #1622 (closed). Implementer note: the gate is called from a named route (invoke bot-gate) with reverse_proxy @page bot-gate:80 {…
Workflow promote-session-denser-simple-1794562680 completed on session-denser-simple. Merged to staging branch. Merge commit: 4cf4a62d16de5278ac906086ca20da15adc3223b
AIDEV Production Bot (4cf4a62d) at 13 Nov 09:38 Merge #1622: Gate the integration site's page documents through a v... ... and 1 more commit
AIDEV Production Bot (4cf4a62d) at 13 Nov 09:38 Merge #1622: Gate the integration site's page documents through a v... ... and 1 more commit
Problem and intended result Found by the tech lead's pre-promote review of #1622 (closed) (299bb593). stack/integration/caddy/Caddyfile.bot-gate sends every gated page document (GET/HEAD under /blog and /wallet, minus API, _next, _rsc and router requests) to reverse_proxy @page bot-gate:80 with lb_try_duration 5s. When the bot-gate varnish container is stopped, crashing or not yet up, that reverse_proxy fails. Caddy answers 502 after up to 5 s, so every page of both apps is down even though the…
Workflow 1622-integration-site-commit-a-bot-s4dd8bf73-v1 completed on session-denser-simple. Merged to staging branch. Implementation: 299bb59336ebff1138a000d084201c2aaf6b2f7c Final branch HEAD: 4cf4a62d16de5278ac906086ca20da15adc3223b (after auto-format) Advisory Spec coverage not evaluated (#11829). spec coverage not evaluated — the issue declares no integration points. Declare them in an ## Integration points block (aidev integration-points propose --issue N drafts one from the prose).…
Problem On 2026-11-13 the integration site (https://denser.discuss.peerverity.info) was rendering about 63 uncached blog pages a second for a distributed crawl: about 22,600 client addresses in 10 minutes, 1–2 requests each, browser user agents (Chrome 116–154 on macOS and Windows), mostly old posts and comments, and robots.txt (Disallow: /, caddy/Caddyfile.routes) ignored. The blog's one Next.js server ran at about 60% CPU, and every post page also called hivesense /similar on api.syncad.com.…
AIDEV Production Bot (4cf4a62d) at 13 Nov 09:36 Merge #1622: Gate the integration site's page documents through a v...
AIDEV Production Bot (4cf4a62d) at 13 Nov 09:36 Merge #1622: Gate the integration site's page documents through a v... ... and 1 more commit
Closes #813 What changes Remembered accounts. Every successful sign-in is saved in localStorage under hivescan_remembered_accounts: up to 5 accounts, newest first. Each entry is only the account name and its sign-in method, never a key or token. The list is device-level like hivescan_last_username, and signing out does not clear it. Reads validate every entry (Hive name pattern, known method) and drop anything else. "Switch account" in the user menu, under the "Logged in via" card. It lists the…
mcfarhat (0802f73b) at 13 Nov 09:31 Issue #813 - Quick account switch in the user menu
Closes #814 (closed) What changes Claim rewards button, shown only when you are signed in and have something unclaimed: in the Wallet card, under the total, on your own wallet only (also in the My Wallet dashboard widget); Full explorer only: classic mode can still turn login on, but stays read-only, so the buttons are hidden there. The rewards dot on the avatar still shows. in the user menu, next to My Wallet. It sits beside the link, not inside it, and drops onto its own line when a long…
Problem The explorer shows unclaimed author and curation rewards (the Wallet card's "Unclaimed" rows and the new rewards dot in the user menu), but users have to go to another Hive front end to claim them. Proposal A Claim rewards button, shown only when the logged-in user is viewing their own profile and has something unclaimed: in the Wallet card, next to the Unclaimed rows; in the user menu, next to "Rewards to claim" under My Wallet. One click broadcasts a single claim_reward_balance…
mcfarhat (8217bedf) at 13 Nov 09:13 Issue #814 - Claim rewards only in the full explorer, not classic mode ... and 1 more commit
mcfarhat (8217bedf) at 13 Nov 09:13
AIDEV Production Bot (299bb593) at 13 Nov 09:09 Gate the integration site's page documents through a varnish bot ga... ... and 319 more commits
Residual-coverage triage — the haf tech lead Parent: #440 (closed). Verdict: wrong. Closing: no listed item is wanted work, so the gate's flag is recorded as a false positive or a deliberate deferral. wrong — #440 (closed) named .aidev/known_failures.txt only conditionally ('only with a stated cause'; acceptance allowed passing OR quarantining with a cause). #440 (closed) found the cause (live mode waits on InitNode0's stale-production slot ~30 s after a slow start, past test_tools' 30 s…
Intake review — the denser tech lead Filed by the denser tech lead from the pre-promote review of #1506 (closed) (a limitation that commit states). Already admitted. It touches apps/blog/components/matrix-chat-widget.tsx, use-matrix-login-token-answer.ts and stack/matrix/README.md, all just changed by #1506 (closed) (landed), so it builds on that. No other open issue touches them. Live check: not checkable: The integration site runs the native Matrix client, not Element mode, and no fresh…
Residual spec coverage (auto-filed by the spec-coverage gate #9914) The workflow for #440 (closed) landed and merged its primary mechanism, but the spec-coverage gate (#8930) flagged a partial delivery: 1/2 of the integration points named in the parent were addressed and 1/1 of its acceptance criteria were delivered. The parent has been closed per the issue-lifecycle policy; this follow-on tracks the remaining scope so it is not silently dropped. Parent issue: #440 (closed) Landing workflow:…
Problem and intended result Found in the pre-promote review of #1506 (closed) on session/denser-simple, and stated in its commit (f3267437) and in stack/matrix/README.md. #1506 (closed) makes the login-token route create a missing Matrix account only for {"createAccount": true}, which only an opened drawer sends. In the native client (the default) a warm-up therefore creates no account. In Element mode, though, a warm-up for a user with no account gets a 404 from the token route and then falls…
Residual-coverage triage — the denser tech lead Parent: #1506 (closed). Verdict: wrong. Closing: no listed item is wanted work, so the gate's flag is recorded as a false positive or a deliberate deferral. wrong — delivered without editing use-matrix-chat-drawer.ts. #1506 (closed) (f3267437) stops warm-up account creation at the token route and the session hook rather than in the drawer hook: POST /api/chat/matrix-login-token creates a missing account only for a body of {"createAccount": true}…
Residual spec coverage (auto-filed by the spec-coverage gate #9914) The workflow for #1506 (closed) landed and merged its primary mechanism, but the spec-coverage gate (#8930) flagged a partial delivery: 2/3 of the integration points named in the parent were addressed and 3/3 of its acceptance criteria were delivered. The parent has been closed per the issue-lifecycle policy; this follow-on tracks the remaining scope so it is not silently dropped. Parent issue: #1506 (closed) Landing workflow:…
Residual spec coverage (auto-filed by the spec-coverage gate #9914) The workflow for #1506 (closed) landed and merged its primary mechanism, but the spec-coverage gate (#8930) flagged a partial delivery: 2/3 of the integration points named in the parent were addressed and 3/3 of its acceptance criteria were delivered. The parent has been closed per the issue-lifecycle policy; this follow-on tracks the remaining scope so it is not silently dropped. Parent issue: #1506 (closed) Landing workflow:…
Workflow 1506-matrix-chat-warm-up-creates-a-s4dd8bf73-v1 completed on session-denser-simple. Merged to staging branch. Implementation: f32674379aaf82e841b28c143cb8719cb14262d3 Final branch HEAD: 82ace6625446caad6e2aa60724bffdeae231f860 (after auto-format) Advisory Partial delivery (spec-coverage gate #8930). This change addresses 2/3 of the integration points declared in the issue. Unaddressed: apps/blog/components/hooks/use-matrix-chat-drawer.ts. A follow-up may be needed to finish the scope.
Problem and intended result With CHAT_PROVIDER=matrix, the drawer warms up on idle by default (packages/ui/config/chat.ts, warmedUpOnIdle in apps/blog/components/hooks/use-matrix-chat-drawer.ts:44), and the warm-up mints a login token through /api/chat/matrix-login-token, which creates missing Matrix accounts and joins the default room (packages/smart-signer/lib/auth/matrix-login-token.ts). So every chat-eligible signed-in user gets a Matrix account and a #general membership without ever…
AIDEV Production Bot (82ace662) at 04 Nov 06:36 Merge #1506: Create the Matrix account only when the chat drawer is... ... and 8 more commits
AIDEV Production Bot (82ace662) at 04 Nov 06:36 Merge #1506: Create the Matrix account only when the chat drawer is... ... and 1 more commit