Thread

Do we trust proton?

I have seen no reason not to. IMO, it's best in class for what it does. That said, no privacy tool can replace good OPSEC, or ultimately save anyone from bad OPSEC. Though I no longer use it for business (it's just not ready yet), the rest of what I have to say below still holds true. nostr:nevent1qqswgp692z8cgay5ersweuv7x89vk302dglwl546am5eu6utenl28aqpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsyawyrzrttfmv4cmtx5w2m85702kdct7hv3amfrkhagpdf9cz46mgrqsqqqqqpy7xymy

Nice. I n I like. A lot. Worked for Personal AI for a year from 2023 - 2024 and they also shared an Our vision …for “AI that puts people ahead of profits.” #AI

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.

nostr:nprofile1qqsrkl7gyds37xh2af37uwlknvjm32ska3hgr5d0cwgzdqy0ux2r2ncppemhxue69uhkummn9ekx7mp0qy0hwumn8ghj7mn0wd68ytfsxghxgmmjv9nxzcm5dae8jtn0wfnj7w57882 would know best.