You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Lukasz Janyst f54d889ca6
cleanup: Make the bridge StoreFactory public
4 years ago
cmd cleanup: Remove LocationsProvider 4 years ago
doc GODT-1537: Manual in-app update mechanism. 4 years ago
pkg cleanup: Make the bridge StoreFactory public 4 years ago
test cleanup: Make tests work 4 years ago
.gitignore GODT-22: Frontend-backend 4 years ago
LICENSE We build too many walls and not enough bridges 6 years ago
README.md GODT-1516 GODT-1451: KeepassXC is crashing on start. We need to block it until it's fixed. 4 years ago
go.mod cleanup: Remove module dependency on go-autostart 4 years ago
go.sum cleanup: Remove module dependency on go-autostart 4 years ago

README.md

peroxide

Peroxide is a fork of the ProtonMail bridge. Its goal is to be much like Hydroxide except with as much re-use of the upstream code as possible. The reason for the re-use is to ensure that the changes to the service APIs can be merged in as fast and as easily as possible. At the same time, Peroxide aims to:

  • run as a server providing data access using standard protocols, so that a wide variety of devices can use their native productivity tools instead of ProtonMail's proprietary ones

  • implement features that are missing from the upstream version because they are hard to make work with Outlook

  • make things easy to hack on without a deluge of dependencies providing little value in the context of the two above points

To than end, Perixide:

  • is buildable with go build
  • drops the original GUI and CLI
  • drops all the desktop desktop integration and trackers
  • provides a server program and a separate configuration program