A privacy question for our users:
If PPQ built some sort of detector on our side that could tell which tool a given user was using would that be infringing too much on user privacy?
The reason for doing this currently is to figure out when prompt caching is NOT working for our users. For example it seems like cline prompt caching works but goose prompt caching doesn't work. So it would be helpful to know which tools are causing problems and which not.
Additionally, this is cool info to have for the purposes of user analysis and development priority. If many users are using cline then we should priotize that experience more.
How would the detector work? Well, most of these third party tools have heuristic signatures. For example, goose queries start with "you are goose, a coding agent..." and cline queries start with "you are cline, a coding agent...". So basically we would be searching for mentions of "goose" or "cline" in the prompts being sent through us and categorize them as such.
If we did build some sort of filter we would of course update our terms of service to reflect that.
My instinct is that most users wouldn't really care about this.
PPQdotAI / PayPerQ
npub16g…ekv4h
2025-05-31 12:06:56
Author Public Key
npub16g4umvwj2pduqc8kt2rv6heq2vhvtulyrsr2a20d4suldwnkl4hquekv4hPublished at
2025-05-31 12:06:56Event JSON
{
"id": "c5d654d8b42383986b63d80073545b65cb236aefd91a4d91d429351e2df769c5",
"pubkey": "d22bcdb1d2505bc060f65a86cd5f20532ec5f3e41c06aea9edac39f6ba76fd6e",
"created_at": 1748693216,
"kind": 1,
"tags": [
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://nostr.oxtr.dev/"
],
[
"r",
"wss://nostr.wine/"
],
[
"r",
"wss://relay.damus.io/"
],
[
"r",
"wss://relay.nostr.band/"
],
[
"r",
"wss://relay.primal.net/"
],
[
"r",
"wss://relay.snort.social/"
],
[
"r",
"wss://nostrua.com/"
]
],
"content": "A privacy question for our users:\n\nIf PPQ built some sort of detector on our side that could tell which tool a given user was using would that be infringing too much on user privacy?\n\nThe reason for doing this currently is to figure out when prompt caching is NOT working for our users. For example it seems like cline prompt caching works but goose prompt caching doesn't work. So it would be helpful to know which tools are causing problems and which not.\n\nAdditionally, this is cool info to have for the purposes of user analysis and development priority. If many users are using cline then we should priotize that experience more.\n\nHow would the detector work? Well, most of these third party tools have heuristic signatures. For example, goose queries start with \"you are goose, a coding agent...\" and cline queries start with \"you are cline, a coding agent...\". So basically we would be searching for mentions of \"goose\" or \"cline\" in the prompts being sent through us and categorize them as such.\n\nIf we did build some sort of filter we would of course update our terms of service to reflect that.\n\nMy instinct is that most users wouldn't really care about this.",
"sig": "d778b62d403aa7caabd3377cb0ff03d11cb52ad3d56fa9054069b29289fcf5c74e4bf84bfe064b7f26e91297cf0fc35bd9d95fbcfe972eeafee707037e028a19"
}