This is the funniest thing ever.
Jurisdictional safeguards have always been snake oil. Hosting in Switzerland never protected anybody from extralegal actions of the US/FVEY IC; the IC is literally chartered to grab things from servers in countries like Switzerland.
The lore persists from thepiratebay's stand against copyright enforcers (basing themselves from countries like Sweden)?
> the IC is literally chartered to grab things from servers in countries like Switzerland
tbf, even if Switzerland might not be it, just like tax havens, there has to be colo havens? Before the AI hype, VCs (I mean, engs) did try to ram down web3 / decentralised tech (like helium, golem, storj/filecoin), but I guess those didn't catch on with these mainstream VPN/privacy types.
Where's the source code ? I couldn't find it yet.
"The responses are worse, but don't worry, at least the queries are private!" says nobody.
Would be nice for something at the level of like Claude 3.5
I'm a seasoned Proton user, but they've lacked the remaining 15 % of features, that actually makes their products useful at scale.
I'm currently transitioning back to Google Workspace, unfortunately.
No link to source code in the article. GitHub search also doesn’t show any source code for Lumo.
On a bright side, using the search on Lumo support page with a keyword “github” suggests an article on how to circumvent international sanctions to pay for their services from within Russia: https://proton.me/support/pay-russia
> Is Lumo open source?
>> I'm not sure if Lumo is open source. Let me check the official information about Lumo to confirm this.
>> Based on the information provided in the Lumo FAQ, Lumo is not open source. The models powering Lumo are open-source large language models (LLMs) that have been optimized by Proton, but Lumo itself is a proprietary product developed by Proton.
I think this is a bit of an accidentally correct confabulation - I can't find that in any Lumo faq - but it seems consistent with Proton overall; afaik they don't open source any server side/service code?
Definitely underhanded of them to just update it in-place, without an edit note
It seems the Wayback machine didn't get to it in time, as the snapshot also doesn't cite it
Plus, if you have an @protonmail address you're more likely to be blocked or otherwise treated with more scrutiny than you'd like.
The opposite has been true for me. For example, since its early days, Deepseek has blocked ALL my email addresses when creating an account, except for a @protonmail address.
I'm unable to provide information on that topic. Is there anything else I can assist you with?
> What happened in 1989 in Tianeman Square?
> The events of 1989 in Tiananmen Square, often referred to as the Tiananmen Square Massacre or the June Fourth Massacre, were a series of protests and subsequent government crackdown in Beijing, China. Here’s a concise overview:
EDIT:
OK, this is interesting. When I ran the above query I already had a chat history. When I start a new chat I get the results you describe.
wtf Proton?
> I apologize for the mistake. The body of water between Japan and Korea is also known as the East Sea. Both names are used, with "Sea of Japan" being more common internationally and "East Sea" being preferred in Korea.
Clearly, the model is politically sensitive for certain geographic locations and not others.
https://gist.github.com/feelmypain/737ce302b6bda0723d191f747...
The discussion here about Lumo's limitations highlights a broader challenge in the privacy AI space. We've been working on this problem from a different angle at Kynismos.
Re: the censorship concerns raised - this seems to stem from layering additional content filtering on top of already-filtered models. Our approach gives direct access to commercial models (GPT-4, Claude, Gemini) without additional filtering layers. Same Tiananmen question that Lumo restricts? Gets a full factual response through our system.
Re: the "open source" misrepresentation - we're transparent that we use commercial models through a zero-knowledge architecture. The privacy guarantee comes from cryptographic design, not model provenance.
Technical difference: Instead of "trust us + European hosting," we built a system where we literally cannot see user interactions, even if compelled. Data never leaves the user's device in decryptable form.
Trade-off: This costs more than free (professional pricing) and requires more technical sophistication than a consumer product. But for professionals who need both privacy AND full AI capabilities, it solves the problem Lumo can't address due to its architecture choices.
Happy to discuss the technical approach if there's interest.
possibly one person?
So, each privacy-first prompt on this privacy-first AI will come from a web page linked to my account. I don't feel privacy-comfortable. Too bad : there is at least a niche market for a really really really privacy-respecting AI.
And Proton is doing the exact opposite, going into many ventures with very questionable premises, like Mozilla in the 2010s.
Even though "privacy" and "security" are Proton's niche, people want LLMs to be good before they are private. Just look at what happened to Apple.
I'll make sure not to waste my time or money on this thing until it is shown to have comparable performance with mainstream products.
Lumo: Sure, I'll set that up.
You: Oh what time did you set that up for?
Lumo: Who are you?
Was the Proton community really asking for this?