Contact

Talk to the people behind PeerSync.

Stuck on an install, found a bug, or thinking about running a rendezvous server for your organization? Tell us about it. For anything that touches code, a public GitHub issue usually gets the fastest answer.

Send a message

Your name Please tell us your name.

Email Please enter a valid email address.

Organization (optional)

Topic Please pick a topic.

Message A few more words would help, at least ten characters.

I understand this is a static page: sending opens my own mail client with the message prefilled, and nothing is stored on a server. Please confirm before sending.

Never paste a folder key into a message. Keys are capabilities.

Bugs and feature requests

Open an issue on GitHub so others can find the answer too. Include your Windows build, the PeerSync version and what you expected to happen.

Open a GitHub issue

Attach a sanitized bundle

For anything that misbehaved, run this on each PC shortly after the problem and attach the ZIP. It contains structured events and timings, and leaves out keys, paths, file contents and network addresses.

psp diagnostics --output bundle.zip

Never attach settings files, certificate private keys or the raw service database.

Security disclosures

Found something that weakens the key chain, the transport or the service's permissions? Pick "Security question or disclosure" in the form and keep details out of public issues until we have replied.

Before you write

The two-PC guide covers signing trust, installation, folder permissions and upgrades. The rendezvous guide covers certificates, firewall rules and probes.