fedipod 1.8.0 → 1.11.0

package/run-agent.mjs

@@ -325,12 +325,14 @@ export class Agent {
       actorId: this.urls.actor, edPrivate: keys.edPrivate,
       proofKeyId: assertionKeyId(this.urls),
       log: this.log, passive: this.viewer,
+      onGone: () => this.publisher.publishCollections({ followers: true }),
     });
     this.publisher = new Publisher({
       config, remote: this.remote, store: this.store,
       deliverer: this.deliverer, publicKeyPem: keys.rsaPublicPem,
       assertionKey: keys.edPublicMultibase, log: this.log,
       resolveMention: (h) => resolveHandle(this, h),
+      resolveActor: (u) => this.intake.fetchAP(u),
       // Inside a pod server the client surface answers on the pod's own
       // origin, so it can be advertised. Standalone it is on loopback, and
       // naming it in a world-readable actor would send clients nowhere.
@@ -586,6 +588,10 @@ export class Agent {
     if (repair) {
       this.ensureActorPublished()
         .catch(e => this.log(`actor check failed: ${e.message}`));
+      // The human page, rewritten only when what it shows has changed: one
+      // local digest compare, and a write the first time after an upgrade.
+      this.publisher.publishProfilePage()
+        .catch(e => this.log(`profile page: ${e.message}`));
     }
     this.seedFollowNotifications().catch(e => this.log(`notification seeding failed: ${e.message}`));
   }

package/scripts/stage-site.mjs

@@ -94,6 +94,7 @@ fs.writeFileSync(path.join(site, '_redirects'), [
   '/api/agent              /.netlify/functions/front  200',
   '/u/*                    /.netlify/functions/front  200',
   '/.well-known/*          /.netlify/functions/front  200',
+  '/@*                     /.netlify/functions/front  200',
   '/install                /.netlify/functions/front  200',
   '/run                    /.netlify/functions/front  200',
   '/roster                 /.netlify/functions/front  200',

package/web/app/agent.mjs

@@ -88,6 +88,7 @@ export class BrowserAgent {
       // Own posts the outbox names and the timeline index lacks come back
       // here, before anything acts on the index.
       await this.publisher.healStatuses().catch((e) => this.log(`healing the timeline index: ${e.message}`));
+      await this.publisher.publishProfilePage().catch((e) => this.log(`profile page: ${e.message}`));
       // And start delivering again, since demote() stopped it. startQueue() is
       // idempotent, so a goActive() that was already active costs nothing.
       this.deliverer?.startQueue?.();
@@ -223,6 +224,7 @@ export class BrowserAgent {
       // The relay finds the account by the front's own key for it, which for a
       // mail-door account is the full address, not the bare handle.
       handle: doorKeyOf(config.gateway?.url) || config.handle, sessionFetch: session.fetch,
+      onGone: () => this.publisher.publishCollections({ followers: true }),
     });
 
     this.publisher = new Publisher({
@@ -232,6 +234,7 @@ export class BrowserAgent {
       // gives its publisher. Without it no mention from the browser ever
       // resolved: a direct message went to nobody, a mention notified no one.
       resolveMention: (h) => resolveHandle(this, h),
+      resolveActor: (u) => this.intake.fetchAP(u),
     });
 
     // The Bluesky connection, stamped to this actor. The same client the Node

package/web/app/dist/boot.js

@@ -33444,6 +33444,7 @@ async function signUp(answers, { onStep = () => {
     handle,
     name: handle,
     issuer: credential.issuerOrigin,
+    createdAt: (/* @__PURE__ */ new Date()).toISOString(),
     ...gateway ? { gateway } : {}
   };
   const cfgRemote = new BrowserRemotePod(session, { webId: credential.webId, role: "signup", log: () => {