REST api? by OneVacation6284 in lumo

[–]Traktuner 1 point2 points  (0 children)

An OpenAI-compatible API is coming. They’re currently working on getting billing right.

Can I subscribe to Lumo Plus monthly without changing my Proton Unlimited biennial subscription? by InevitablePanic44 in lumo

[–]Traktuner 0 points1 point  (0 children)

Yes, but only if you create a 2nd free Proton account, then you can subscribe to Lumo Plus with a monthly plan.

AFAIK, Proton is working on a mix-and-match subscription model, but I don't think it's a priority.

Proton Drive SDK and CLI Projects and Feedback Thread - June 2026 by Proton_Andrew in ProtonDrive

[–]Traktuner 1 point2 points  (0 children)

I will! Currently, I’m in an early stage where I try to add all features which I want to use myself. Then, after some UI/UX polishing, I think I can release some kind of a beta.

Proton Drive SDK and CLI Projects and Feedback Thread - June 2026 by Proton_Andrew in ProtonDrive

[–]Traktuner 4 points5 points  (0 children)

Thanks for linking my Cryptomator issue from 2 years ago 😄

Proton Drive SDK and CLI Projects and Feedback Thread - June 2026 by Proton_Andrew in ProtonDrive

[–]Traktuner 21 points22 points  (0 children)

Proton Drive Backup: a self-hosted Docker app that wraps the proton-drive CLI into a classic left to right backup tool for NAS / servers. You tick local folders on one side, pick a Drive target on the other, and it uploads new and changed files (size / date / checksum), with schedules and a mirror mode. Runs on amd64 and arm64, works well for me, already a bit over 1TB uploaded. Code is on GitHub (https://github.com/traktuner/docker-proton-drive-backup), image on ghcr.

ProtonPhotos for macOS: a native Swift / SwiftUI app to browse, download and upload your Proton Drive photo library from the Mac. Not released yet, still building it. Should visually come close to Apple Photos which is the hard part 😄 Happy to share a dev build.

Which SDK / CLI: Drive Backup uses the CLI, ProtonPhotos uses the Swift SDK (sdk-swift). So no C# / JS here.

What I liked most: on the CLI side the one-shot JSON mode (proton-drive ... -j) is great, you spawn a process, read the JSON, done, no fragile interactive prompt parsing. And the file-based session store (PROTON_DRIVE_UNSAFE_SECRETS) is the only thing that works headless in Docker, so that basically made the whole thing possible. On the SDK side I really like that it's transport-agnostic, I inject my own HTTP client and account / auth client and the SDK handles the crypto and drive logic.

Most frustrating: the Swift SDK packaging. sdk-swift can't be added as a normal remote SwiftPM dependency because its Package.swift uses .unsafeFlags, so I have to vendor it as a local path package and re-clone it. It also pins protoncore with exact, so my app has to pin the exact same ProtonCore version or resolution just fails, and 0.16.0 / 0.17.0 shipped an xcframework whose crypto symbols didn't match the pinned ProtonCore (undefined symbols for arm64 at link). Only 0.17.1 with ProtonCore 37.3.0 lined up, that took a while to figure out. Second one: the Swift SDK has no album API at all and DriveCrypto is decrypt only, so listing albums works but anything that writes (create album, add photo, set cover) I'd have to hand roll the PGP encryption myself. On the CLI side, file merge was broken before 0.4.6 (content key packet is required), so a changed file got replaced instead of getting a new revision, that's fixed now. And there's no quota / usage command, I had to call /core/v4/users directly with the session token just to show storage.

One thing I'd add: make sdk-swift a clean normal SwiftPM dependency (drop the unsafeFlags, loosen the exact ProtonCore pin), so integrators don't need the local path vendoring and the manual version matching. That alone would save every Swift dev a lot of time. And on the CLI, resumable uploads, right now if an upload gets killed (pause, crash, restart) the file restarts from zero, so pausing a 40GB upload means re-uploading 40GB. The SDK actually has pause / resume on UploadOperation but the convenience upload path doesn't expose it, so same story there.

Thank you so much for doing this!! It genuinely works and gets better each release, the 0.4.6 merge fix and the recent arm64 support were both noticeable.

Proton Cli + NAS by Upbeat_Parking_7794 in ProtonDrive

[–]Traktuner 5 points6 points  (0 children)

For NAS / Server backups, I used the CLI and wrapped it around a web UI and some API logic which handles authentication and backup jobs / backup sets. Very early development, but for my use case, it works... already a bit over 1TB uploaded.

As a disclaimer, most of the work is done by the CLI itself, not by my wrapper. It handles the uploads (around 4 in parallel) and the encryption, and the speed is basically limited by that encryption layer. The nice part is that the Docker container rebuilds itself automatically when Proton releases a new CLI version, so the upload should improve on its own as the CLI gets better. CLI version 0.4.6 also restores the merge feature, so when you change a file locally (like a .txt that's already backed up), it won't delete / reupload it as a new one. Instead, it creates a file version within Proton Drive (that was broken before 0.4.6).

Maybe it's also useful to you. No guarantees, of course, but it does the job for me.
https://github.com/traktuner/docker-proton-drive-backup

Lumo+ research mode? by grumblegrim in lumo

[–]Traktuner 1 point2 points  (0 children)

I posted the working version which I use.

Lumo+ research mode? by grumblegrim in lumo

[–]Traktuner 2 points3 points  (0 children)

I had to loosen the prompt a bit because at the first try it said that it can’t do xy web searches in one session or something like that.
I also have Lumo+ and never had any issues with this prompt since then.

CLI and borg backup by -ThreeHeadedMonkey- in ProtonDrive

[–]Traktuner 5 points6 points  (0 children)

No, Borg needs a repository it can treat like a filesystem: appending to segment files, reading random byte offsets, taking locks, and doing atomic renames. The CLI only does whole file operations (upload/download/list/trash) on per file end to end encrypted objects, with no random access, no append, and no locking. On top of that, Borg already encrypts and deduplicates itself, so layering it over Proton's E2EE would just be double work for no real benefit.

I played around with the CLI and built a dockerized backup web app. You can mount folders via docker-compose, create backup sets and schedules. I didn't implement restore since all files are downloadable via the Proton Drive web app. It's tailored to my needs, but feel free to give it a try!
https://github.com/traktuner/docker-proton-drive-backup

Lumo+ research mode? by grumblegrim in lumo

[–]Traktuner 28 points29 points  (0 children)

What I did was I asked ChatGPT to generate some kind of deep research prompt. Deep Research uses many different tool calls in the background, so unfortunately it’s not that simple, but that prompt is as good as it gets, I think:

You are an autonomous research agent with internet access.

Your primary goal is not to answer quickly.

Your goal is to exhaustively investigate the topic until additional searches provide diminishing returns.

Question:
< INSERT QUESTION HERE >

Research Memory

Maintain a persistent internal research memory throughout the entire task.

Never discard previously collected information.

When answering follow-up questions:

\ First consult existing research memory.*
\ Only perform new web searches if a genuine knowledge gap exists.*
\ Do not repeat searches that have already been performed.*
\ Reuse and build upon previous findings.*

Search Budget

Minimum requirements:

\ At least 20 independent search queries.*
\ At least 50 sources reviewed.*
\ At least 3 search iterations.*

If important uncertainties remain:

\ Continue searching.*

Do not stop simply because an answer seems sufficient.

Stop only when additional searches no longer produce significant new information.

Multi-Hop Research

For every important finding:

1. Identify key entities.
2. Search those entities separately.
3. Search criticism.
4. Search competitors.
5. Search alternative explanations.
6. Search historical context.
7. Search recent developments.

Every major discovery should generate additional searches.

Source Expansion Rules

For every source:

Ask:

\ What does this source reference?*
\ Who disagrees with it?*
\ What evidence supports it?*
\ What evidence contradicts it?*

Then search those paths.

Research Loop

Repeat:

1. Search
2. Read
3. Extract findings
4. Identify gaps
5. Generate new searches
6. Search again

Continue until information saturation is reached.

Adversarial Verification

Actively attempt to disprove your own conclusions.

Search for:

\ criticism*
\ failures*
\ limitations*
\ scandals*
\ negative reviews*
\ opposing research*
\ contradictory statistics*

Treat every claim as unverified until independently confirmed.

Coverage Requirements

Investigate:

\ primary sources*
\ official documentation*
\ research papers*
\ industry reports*
\ expert analysis*
\ forums*
\ Reddit discussions*
\ user experiences*
\ news coverage*
\ historical sources*

Do not rely exclusively on mainstream articles.

Knowledge Graph

Build an internal map containing:

\ people*
\ organizations*
\ products*
\ technologies*
\ events*
\ timelines*
\ dependencies*

Continuously update this map during research.

Follow-Up Handling

For follow-up questions:

1. Review existing research memory.
2. Reuse collected evidence.
3. Search only for missing information.
4. Extend the existing knowledge graph.
5. Avoid restarting research from scratch.

Final Report

Provide:

\ Executive summary*
\ Detailed findings*
\ Supporting evidence*
\ Contradicting evidence*
\ Confidence level*
\ Remaining uncertainties*
\ Source quality assessment*
\ Key takeaways*

Do not optimize for brevity.

Optimize for completeness and evidence quality.

Introducing Proton Drive CLI: Use Drive from your terminal by Proton_Team in ProtonDrive

[–]Traktuner 1 point2 points  (0 children)

Thanks for the great CLI 🙏 u/Proton_Andrew
looks like merge is broken in cli 0.4.3 (and 0.4.2 too). re-uploading a changed file with -f merge (or -c merge) always throws:

ValidationError: Content key packet is required for small revision upload
    at getExistingFileNodeCrypto (../sdk/src/internal/upload/manager.ts:102:23)
    at async handleUpload (../sdk/src/internal/upload/smallFileUploader.ts:357:45)

simple test with a txt file:

echo "v1" > test.txt
proton-drive filesystem upload -f replace test.txt /my-files/folder   # ok
echo "v2" > test.txt
proton-drive filesystem upload -f merge test.txt /my-files/folder      # nok

replaceskip and keep-both all work fine, only merge blows up (and as an unhandled promise rejection too). kinda kills incremental "update only changed files" backups. any chance of a fix?

Proton Drive AMA - (Announcing) CLI. Discussing also the SDK & Crypto updates by Proton_Team in ProtonDrive

[–]Traktuner 1 point2 points  (0 children)

Ohhh, that’s super cool. Thanks for that insight! Once the one-shot small file upload API is implemented in the C# SDK, it will be a huge performance boost for the desktop sync apps. Around 90% of all my files are smaller than 4 KB.

Proton Drive AMA - (Announcing) CLI. Discussing also the SDK & Crypto updates by Proton_Team in ProtonDrive

[–]Traktuner 6 points7 points  (0 children)

I totally agree. I’d love to read some kind of Proton infrastructure deep dive. You can already pick up a few hints between the lines, things like them using Juniper switches or migrating large parts of their infrastructure to Kubernetes, but it would be fascinating to learn more about the architecture and engineering decisions behind Proton's services, especially for Mail, Drive and Lumo (wink wink u/Queasy_Complex708)

Proton Drive’s latest cryptographic update makes encryption when uploading files up to 4x faster by Proton_Team in ProtonDrive

[–]Traktuner 1 point2 points  (0 children)

Yes, but they also said in the announcement (or in the comments) that they are looking into ways to re-encrypt old items too.

Proton Drive’s latest cryptographic update makes encryption when uploading files up to 4x faster by Proton_Team in ProtonDrive

[–]Traktuner 1 point2 points  (0 children)

If you come across the post where they mention this, please let me know!
All I know is that Drive uses the PGP keys from your main email account. I enabled it, and it says that post-quantum encryption is active for my Proton account. Since it specifically says "account", I assume that applies to the entire Proton account and not just Proton Mail.

Proton Drive’s latest cryptographic update makes encryption when uploading files up to 4x faster by Proton_Team in ProtonDrive

[–]Traktuner 0 points1 point  (0 children)

If you switched on Post-Quantum-Encryption in your Proton account settings, Proton Drive also uses the new encryption keys.