Astra c1c7db325f users: never cache a deleted user's base row ... redisstore.userBaseValue has no Deleted/DeletedAt/Status field, so caching a deleted user silently reset Deleted back to false (and Status to the zero UserStatusUnknown) on every round trip. That never self-healed: each later cache miss reloaded the correctly tombstoned DB row and immediately re-corrupted it on write, so once anyone looked a deleted account up, it kept showing a blank name with "last seen recently" instead of "Deleted Account". Keep deleted users off the base cache entirely so lookups always hit the authoritative store, and stop presence overlay from touching a Deleted user's Status at all as defense in depth. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>		2026-09-13 22:08:06 +01:00
..
doc.go	Initial open source release	2026-06-04 01:37:39 +08:00
premium_test.go	feat: sync monoforum and collectible emoji status	2026-07-19 20:37:10 +08:00
service.go	users: never cache a deleted user's base row	2026-09-13 22:08:06 +01:00
service_test.go	users: never cache a deleted user's base row	2026-09-13 22:08:06 +01:00