top | item 33441636

(no title)

twleo | 3 years ago

> Bridge is open source, and as a result relies upon open-source components

I don't get it. Bridge is open source does not imply it should relies upon open-source components.

> Addressing this issue at the source requires replacing the core IMAP library.

Why building an IMAP library from scratch instead of fixing/forking go-imap? Even a temporary fix to go-imap when you are developing gluon? Another repetitive work which does not guarantee the mentioned issues will be resolved completely.

discuss

cryptonector|3 years ago

> I don't get it. Bridge is open source does not imply it should relies upon open-source components.

It could be open source and depend on proprietary components, but then the public wouldn't be able to build and use it from source.

twleo|3 years ago

Proton should be responsible no matter it uses the third-party open-source/propriety components or not.

If they decide to use third party libraries, that's their responsibility to review those libraries and include them to their code base.

Not "it's not my fault; it's others fault"

9935c101ab17a66|3 years ago

In the comment from the Proton team member, they repeatedly bring up the open-source nature of Bridge as if that fact alone is an excuses the litany of bugs in Bridge. ProtonMail are selling a premium service at premium prices, and yet a catastrophic data loss bug has existed in Bridge for a while. The dev team knows about it, and nothing has been done it seem? Have users been warned? are mitigations in place? It's just wild.