🔗 David Sommerseth

F/OSS hacker, mostly working on #OpenVPN
- speaks only for himself.
ex-Twitter account (now inaccessible): https://twitter.com/DavidSommerseth

“Don’t aim to be someone. DO something.”

#nobridge - because I believe in the real #fediverse, and I don’t want my own views/data to be abused by yet another “closed-service which can do whatever it wants for profit”.

**If you want to follow me**, you will now **MUST** have some content on your profile where we have some common ground on interests. I will no longer accept random profiles wanting to follow with no toots or no other follows or followers in the same interest sphere.

  • 0 Posts
  • 5 Comments
Joined 2 years ago
cake
Cake day: December 28th, 2022

help-circle

  • @abobla

    I kinda struggle to believe it’s that difficult. I mean, Tresorit has a pretty good and functional Linux client. What have they done which makes it sustainable for them?

    Filen.io also has a pure sync-client, which is distributed as an AppImage. This also works, but the FUSE integration Tresorit provides is quite awesome and performing quite decently.

    I would actually recommend Proton to start the development on an older Linux distro. Like RHEL/Alma/Rocky 9 or Debian 11 (which is EOL, though) and make it run there. Moving from that distro to newer distros will then go smother and you’ll get other distros supported quicker.

    The mistake too many Linux efforts does is to take the “latest and greatest” distro version - often coupled with what a single Linux developer considers the “most used distro” and then hits lots of challenging when needing to support older distros. That’s going to be painful.

    @protonprivacy Please take note and forward to Andy and other managers.




  • @Dark_Arc @bl4kers

    I can understand the confusion. But it kinda makes sense… if my hypothesis is correct.

    Proton Drive has the concepts of “My Files” and “Computers”. Files stored under “Computer” (where you can have synced files for up to 10 computers, according to docs) tracks the files for each computer individually.

    So when you uninstall Drive and delete the files, they are only stored in the cloud. But after reinstalling it again, it sees the files locally for that computer is gone … so it gets removed in the cloud.

    Had these files been moved to “My Files” in before the reinstall, this should not have happened.

    At least, that’s my theory.