@oxyhq/core 12.5.0 → 12.5.2

package/dist/cjs/i18n/locales/zh-CN.json

@@ -118,7 +118,8 @@
         "passkeySigningIn": "正在登录…",
         "getCommons": "获取 Commons",
         "commonsNotInstalled": "没有 Commons？获取应用以使用您的 Oxy ID 登录。",
-        "showQrAnyway": "我在另一台设备上有 Commons"
+        "showQrAnyway": "我在另一台设备上有 Commons",
+        "switchWhileSignedInAs": "切换账号，当前登录为 {{name}}"
     },
     "common": {
         "actions": {
@@ -220,6 +221,7 @@
             "subtitle": "Apps you authorize to sign in with your Oxy account will appear here"
         },
         "item": {
+            "granted": "已于 {{relative}} 授权",
             "lastUsed": "Last used {{relative}}"
         },
         "confirm": {

package/dist/cjs/mixins/OxyServices.user.js

@@ -105,7 +105,15 @@ function OxyServicesUserMixin(Base) {
                     handle,
                 }, {
                     cache: true,
-                    cacheTTL: 24 * 60 * 60 * 1000, // 24h cache — matches server-side staleness window
+                    // 5 min — matches the sibling profile fetches (getUserById /
+                    // getProfileByUsername). /profiles/resolve now carries the viewer-relative
+                    // `relationship` (isFollowing / followsYou); `followsYou` is target→viewer,
+                    // so the viewer can't self-refresh it via a follow action. The GET cache is
+                    // identity-scoped (keyed by the caller's access-token identity tag → no
+                    // cross-viewer poison), so a short TTL keeps "Follows you" reasonably fresh
+                    // without a per-call bypass. The identity fields alone tolerate a longer
+                    // window, but a 24h stale relationship is not acceptable.
+                    cacheTTL: 5 * 60 * 1000,
                 });
                 return (0, userIdentity_1.normalizeUserIdentityOrNull)(result);
             }