External/beardrive
1
0
Fork 0
mirror of https://github.com/runbear-io/beardrive.git synced 2026-08-25 08:08:08 +02:00
Code Issues Packages Projects Releases Wiki Activity

fix(history): stop reporting the device IP on every change (BEA-43) (#81)

Browse Source 
* fix(history): stop reporting the device IP on every change (BEA-43)

The history API embedded the whole DeviceInfo, so every project member
read a teammate's server-observed IP (plus user/last_seen) next to every
change on a page whose job is "who changed this file". Project a
three-field historyDevice instead — id/name/os — mirroring heatByDevice.

The device registry is unchanged: Observe/requestIP and both MetaStore
backends keep recording the IP. This is a response projection, not a
change in what gets collected.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* docs: history shows device name and OS, not the IP (BEA-43)

README, SKILL.md and the docs site all promised the History view would
show the connecting IP. It no longer does — the registry still records it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Snow Lee (Sungwon)
2026-07-31 09:10:18 +09:00
committed by GitHub
co-authored by Claude Opus 5
parent af9ef4d181
commit b408e004b3
10 changed files with 58 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files
web/docs/src/content/docs/guides/agent-artifacts.md
+1 -2
View File
@@ -94,8 +94,7 @@ bdrive log -n 50 # more of them
```
The web UI's **History** view shows the same thing with view and download of any
past version, including which device (name, OS, and the IP the server observed)
made each change. Folder rows have a history shortcut for a subtree feed.
past version, including which device (name and OS) made each change. Folder rows have a history shortcut for a subtree feed.
This is the part a memory API can't give you: when an agent asserts something,
you can see which agent wrote it, when, from where, and what the file said
web/docs/src/content/docs/self-hosting/authentication.md
+2 -1
View File
@@ -82,7 +82,8 @@ alone can't grant. `bdrive login --device` forces that flow.
Every sync and every `bdrive init` then authenticates with that token. The hub's
device registry records per-device name, OS, account, and the IP the server
observed — that's what History displays.
observed. History shows the device name and OS; the IP stays in the registry
and is never reported to project members.
## Password reset