Can this be extended as an inbox/outbox proxy relay? I want to only define my own relay in mobile clients, and the proxy relay will do the rest.
Stats for wss://chorus.mikedilger.com:444/ running the chorus relay software https://github.com/mikedilger/chorus
Host System: AMD EPYC 2313 16-Core Processor, 3 GHz, 512K Cache
Guest System (VPS): 2-core, 3GB ram, 30GB disk
Uptime of chorus: 8 days
CPU time consumed (9 minutes 55 seconds, or less than 1/1000)
Memory resident (38.424 MB)
Clients being served: 51 connections currently open long-term, no data on short-term.
This 'personal' relay isn't getting much traffic. But it is good to see that it is using less than 1/1000 of the CPU of a cheap VPS. It has also been rock-solid reliable, not just in never crashing but also in serving the events it is supposed to serve.
Discussion
A nostr client proxy is a far bigger project than a nostr relay. A nostr client proxy would have to have all the low-level code of a nostr client, which is probably more than 10x as much code as a relay needs.
So technically yes it could be extended into that, but the extension would be far larger than the current chorus relay is.