I just did a few tests. Thanks for sharing. It seems to perform quite well compared to using the underlying OSS models directy. Whatever Proton is doing to route and potentially augment requests seems to be working. For something that's meant to be privacy-oriented, it's not nearly as bad as I was expecting.
Don't get me wrong… it still hallucinates like there's no tomorrow and can't code to save its life… But it did find go-nostr all by itself and even linked it to nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp (even though the "official" repo is actually at github.com/nbd-wtf/go-nostr ).
Ignoring the code and the hallucinated duration bit (the library itself uses a hardcoded primitive exponential backoff strategy, retrying every 30 + 2^nFailures seconds), it sorta, kinda, almost gave me a good explanation of what the obscure library feature I asked about is supposed to do. Given that this isn't JavaScript or Python, and I haven't hooked it up to any Nostr-specific MCP or documentation file, I'm almost impressed.
