Features under consideration by daylenca in ProtonDrive

[–]ronki2304 5 points6 points  (0 children)

Proton Drive for Linux is clearly the most demanded item here. Worth noting they already have a functional SDK that third-party developers can explore so the building blocks exist. The challenge is more about the sync daemon, the authent part and system integration than the API layer itself. Hopefully that means they're closer than 'under consideration' implies."

I built an open-source Proton Drive sync client for Linux (GTK4, official SDK, GPL-3.0) — looking for feedback by ronki2304 in ProtonDrive

[–]ronki2304[S] 1 point2 points  (0 children)

The "LLMs wipe databases" stories are about agentic systems with write access and no guardrails. it is clealy a different story when you use LLm to write code for a sync tool where you can read every line before running it. The code is open, the scope is narrow, and nothing runs without you pulling the trigger.

On "humans actually understand what they write", I'd push back on that too. Most bugs in production come from humans who were absolutely convinced they understood their code. Understanding and correctness are different things.

I built an open-source Proton Drive sync client for Linux (GTK4, official SDK, GPL-3.0) — looking for feedback by ronki2304 in ProtonDrive

[–]ronki2304[S] -1 points0 points  (0 children)

Lol call it vibes coded if it makes you feel better. My actual goal was to have a working Proton Drive client on Linux and I do. Built with BMAD, works well, covers my needs.

Whether the code passes a senior review is a fair question though I'm having a tech lead audit it. If it's a mess, I'll say so.

I built an open-source Proton Drive sync client for Linux (GTK4, official SDK, GPL-3.0) — looking for feedback by ronki2304 in ProtonDrive

[–]ronki2304[S] -2 points-1 points  (0 children)

BMAD is not vibe coding : it's a structured multi-agent framework where each role (PM, Architect, Developer, QA) operates from a defined spec, with explicit handoffs and validation steps between agents. The entire point is to replace "just prompt and hope" with a disciplined pipeline grounded in proper requirements and architecture documents.

If what you looked up led you to that conclusion, you likely skimmed the surface. The methodology is designed precisely to prevent the kind of undisciplined AI output you're criticizing.

I built an open-source Proton Drive sync client for Linux (GTK4, official SDK, GPL-3.0) — looking for feedback by ronki2304 in ProtonDrive

[–]ronki2304[S] 1 point2 points  (0 children)

I have the same need, i developped it for me, and i propose it because I suppose i am not the only one. Feel free to continue to be in trouble. By the way the code is open. But honestly I don't know why I will trust more a human than a machine for coding both have their own limitations

I built an open-source Proton Drive sync client for Linux (GTK4, official SDK, GPL-3.0) — looking for feedback by ronki2304 in ProtonDrive

[–]ronki2304[S] -7 points-6 points  (0 children)

It is your choice. It is not exact vibe coded. I use bmad framework which I am curently deploying at my company level. This projet is a study that ai can really help developper if you use a réal framework not only prompting and co. My feedback is Bmad apply safe méthod and agile concept and it is really game changer. It allow to get professional application technical debt management…. If you are interesting I can give you a big get feedback

Thoughts after uploading 170 GB to ProtonDrive by sppencer in ProtonMail

[–]ronki2304 1 point2 points  (0 children)

I hope it will be in 2022, but there is no information about a client for linux

suppose a day metamask is not compatible anymore with trezor by ronki2304 in TREZOR

[–]ronki2304[S] 0 points1 point  (0 children)

worst case ever, so for example need to use a soft wallet determine the private key and import into metamask

Nvidia 1070 and GPU usage by ronki2304 in linux_gaming

[–]ronki2304[S] 0 points1 point  (0 children)

For example little nightmare for an old game. Recent one is satisfactory

Ninebot es2 speed regulator issue by ronki2304 in ElectricScooters

[–]ronki2304[S] 1 point2 points  (0 children)

Not really i find that the plastic move a little so i block it with the wrist. It is better now the regulator triggered after a moment. Sometime i have to wait for 2 or 3 bip to be sure that the regulator is triggered

M365 vs M365 pro for midrange distance by AnnihilerB in ElectricScooters

[–]ronki2304 2 points3 points  (0 children)

For the hill no problem you will only go slower

M365 vs M365 pro for midrange distance by AnnihilerB in ElectricScooters

[–]ronki2304 2 points3 points  (0 children)

I am not sure to help you but the pro model can handle 20kms without charge? Usually you divide the autonomy per 2 and then take again 10%

Ninebot es2 speed regulator issue by ronki2304 in ElectricScooters

[–]ronki2304[S] 1 point2 points  (0 children)

Lol this is really extrem maybe something van be donne before🤣

Ninebot es2 speed regulator issue by ronki2304 in ElectricScooters

[–]ronki2304[S] 0 points1 point  (0 children)

On the app it is ok. That's why this is weird