diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-08-15 00:50:05 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-08-15 00:50:05 +0200 |
| commit | f4d04741379e77d2ef86cccc93856e590bfe1082 (patch) | |
| tree | e3a094f9a8778cfcb8b3bd49ca422a28e2434104 /poc | |
| parent | 76724252d08162d4df39090af19796054bf4add8 (diff) | |
| download | meshbay-f4d04741379e77d2ef86cccc93856e590bfe1082.tar.gz | |
feat(logs): keep the username on records the account no longer answers for
The connection log took the name from a join on `users`, and deletion
tombstones that row — so every record belonging to a deleted account
reported `deleted-3f9a1c`, which is the one answer that helps nobody. The
log is kept for a legal retention period precisely so it can say who did
what; losing the name at deletion kept the data and lost the point of it.
`ip_logs.username` is written as the account is erased, and stays NULL
while the account is alive, where the join is better because it cannot go
stale. The admin view prefers the stored name when there is one: the join
still answers after deletion, just with the tombstone.
Releasing the username for re-registration and keeping it in the log are
separate things, and the guide now says so.
On the node side, the pre-proof audit line records the username the
session already knew, instead of leaving the column empty.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat (limited to 'poc')
0 files changed, 0 insertions, 0 deletions