I have long sessions and the queries are surprisingly cheap....

npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6
hex
0bdc590926e029c86ceffc4cb356e53daf7cfb911b08c4a6dd5123a242b623b7nevent
nevent1qqsqhhzepynwq2wgdnhlcn9n2mjnmtmulwg3kzxy5mw4zgazg2mz8dcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsydl97xpj74udw0qg5vkfyujyjxd3l706jd0t0w0turp93d0vvungxd5vsuKind-1 (TextNote)
↳ 回复 d22bcdb1... (npub16g4umvwj2pduqc8kt2rv6heq2vhvtulyrsr2a20d4suldwnkl4hquekv4h)
Additionally, caching is not a complex thing we are implementing on our side anymore. It is handled by the providers who know what they are doing. So ...
I have long sessions and the queries are surprisingly cheap. As I told you, the switch to "save a bit" resulted in record high queries consistently.
These are all from the same session and the 83ct one is where I switched to autoclaw/premium.
But ... it might be false alarm. Sorry. It would be great if the activity list would show if it was autoclaw-kimi or just kimi but just now I'm getting kimi and before might have been opus being configured on the specific agent, ignoring the default model that I had changed to autoclaw. Sorry. Will test again and please leave autoclaw/premium in place! 🙏
原始 JSON
{
"kind": 1,
"id": "0bdc590926e029c86ceffc4cb356e53daf7cfb911b08c4a6dd5123a242b623b7",
"pubkey": "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d",
"created_at": 1771613937,
"tags": [
[
"e",
"239869f01ce7c636fa9978ca0ae504494c5ca5b790f75e5dbce7d5d07fe63ee3",
"wss://relay.primal.net/",
"root",
"d22bcdb1d2505bc060f65a86cd5f20532ec5f3e41c06aea9edac39f6ba76fd6e"
],
[
"e",
"969075798ba445fd77cf920a00bae75366773ed33782c38a10d3eceae7e3b432",
"wss://relay.primal.net/",
"reply",
"d22bcdb1d2505bc060f65a86cd5f20532ec5f3e41c06aea9edac39f6ba76fd6e"
],
[
"p",
"d22bcdb1d2505bc060f65a86cd5f20532ec5f3e41c06aea9edac39f6ba76fd6e"
],
[
"client",
"jumble"
]
],
"content": "I have long sessions and the queries are surprisingly cheap. As I told you, the switch to \"save a bit\" resulted in record high queries consistently.\n\nThese are all from the same session and the 83ct one is where I switched to autoclaw/premium.\n\nBut ... it might be false alarm. Sorry. It would be great if the activity list would show if it was autoclaw-kimi or just kimi but just now I'm getting kimi and before might have been opus being configured on the specific agent, ignoring the default model that I had changed to autoclaw. Sorry. Will test again and please leave autoclaw/premium in place! 🙏",
"sig": "3761b204cb3a0d0c5e0cd0b718260433a29a143c1bbb7b9b83cc24ad54b418927c4ca623baa8ee2488e452aa717c3dd31ce8ff95bfa547700df58946b9510ee8"
}