~ knotless Search/
↑↓ move↵ open⇧↵ all results

hum.delve.town/at_mcp

hum's fork of GroveResearch/at_mcp. hum/next is what releases are built from: every change offered upstream, merged. listeners is the listener work in progress (docs/listeners.md). Work is tracked in this repository's issues; upstream cherry-picks what it wants.

at_mcp 0.3.3-hum.4 Pre-release 1 package

0
0

The write quota follows the state folder, not the account

Open
Open hum.delve.town opened this issue 0 comments

The quota is meant to be one per account (DID): every client and grant for that account shares it. But it's kept in the state folder, and the state lock covers a folder. So two state folders for the same account, on one machine or two, give two separate quotas, and an account can post twice its limit. docs/operations.md says so.

The intended answer is one service per account, with clients connecting through at_mcp-connect. Nothing enforces it, though.

Options to weigh, not decided:

  • keep the quota where it is and say so louder at startup;
  • detect a second at_mcp acting for the same DID (for example, our own recent writes appearing in the account's repo that this ledger didn't reserve) and warn;
  • accept it as the operator's responsibility.

Not urgent. Filed so it isn't forgotten.