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 d91afce3e7
dist: Add a systemd service file
4 years ago
cmd peroxide/perixide-cfg: Change the default configuration path 4 years ago
pkg credentials: Refactor the encryption/dectryption functions 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 doc: Add example configuration 4 years ago
config.example.yaml docs: Update the example config 4 years ago
go.mod cleanup: Modulo bookkeeping 4 years ago
go.sum cleanup: Modulo bookkeeping 4 years ago
peroxide.service dist: Add a systemd service file 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

Example configuration file is provided as config.example.yaml.