Auth: per-user default IPFS gateway + clear error when gateway lacks review files #23

Open
opened 2026-10-23 00:08:57 +00:00 by rhelwig · 0 comments
Owner

Problem

During the 2026-10-22 ronhelwig.com publish on Auth 0.1.21-mainnet, the review failed with the generic "The release could not be verified." The real cause was Auth's default IPFS gateway: a public gateway that didn't have the review files, so the fetch timed out. Switching Auth's gateway to https://ipfs.ronhelwig.com (the site's own Kubo) fixed it.

1. Per-user default gateway

  • Add a persistent setting in Auth for the default gateway, and encourage users to point it at their own Kubo.
  • Optional: Admin includes a gateway hint in the review QR or site record (e.g. reviewGateway: https://ipfs.ronhelwig.com). Auth tries it first or offers it, then falls back to the user's default.

2. Clear error when the gateway lacks the files

  • On a timeout, 404 or other non-2xx response, say: "The IPFS gateway at doesn't have this release's files."
  • Suggest the site's own gateway, and offer one tap to switch and retry.
  • Keep a separate error for hash mismatches.

3. Name version mismatches

Auth 0.1.18 rejects v2 ("only-changed") release requests (NEWER_AUTH_REQUIRED; 0.1.20 or later is needed) but shows the same generic message. It should say: "This release needs Auth 0.1.20 or newer; this device has 0.1.18."
ReleaseReviewActivity.kt (around line 81) currently catches every buildReleaseReview exception with one message.

Context

2026-10-22, mainnet, Auth 0.1.21 (versionCode 22, commit 89acef3) on a Pixel 4a. v2 release with 23 content records, 12 reused.

## Problem During the 2026-10-22 ronhelwig.com publish on Auth 0.1.21-mainnet, the review failed with the generic "The release could not be verified." The real cause was Auth's default IPFS gateway: a public gateway that didn't have the review files, so the fetch timed out. Switching Auth's gateway to https://ipfs.ronhelwig.com (the site's own Kubo) fixed it. ## 1. Per-user default gateway - Add a persistent setting in Auth for the default gateway, and encourage users to point it at their own Kubo. - Optional: Admin includes a gateway hint in the review QR or site record (e.g. reviewGateway: https://ipfs.ronhelwig.com). Auth tries it first or offers it, then falls back to the user's default. ## 2. Clear error when the gateway lacks the files - On a timeout, 404 or other non-2xx response, say: "The IPFS gateway at <url> doesn't have this release's files." - Suggest the site's own gateway, and offer one tap to switch and retry. - Keep a separate error for hash mismatches. ## 3. Name version mismatches Auth 0.1.18 rejects v2 ("only-changed") release requests (NEWER_AUTH_REQUIRED; 0.1.20 or later is needed) but shows the same generic message. It should say: "This release needs Auth 0.1.20 or newer; this device has 0.1.18." ReleaseReviewActivity.kt (around line 81) currently catches every buildReleaseReview exception with one message. ## Context 2026-10-22, mainnet, Auth 0.1.21 (versionCode 22, commit 89acef3) on a Pixel 4a. v2 release with 23 content records, 12 reused.
Sign in to join this conversation.
No labels
feature request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rhelwig/DecentSite#23
No description provided.