Hacker News new | ask | show | jobs
by kuschku 3779 days ago
Warning to anyone trying to self-host:

Despite N1 calling their cloud engine "open source", the authentication part isn’t – and isn’t included.

If you set up the open source variant yourself, you’ll end up without any authentication.

1 comments

When you say authentication, do you mean the cloud engine doesn't authenticate against your email providers, or that the desktop client doesn't authenticate against the cloud engine?
I mean that there is no password between desktop client and the open source cloud engine – anyone can log in to it just like that.

The tokens to auth are world-readable under /accounts or /n

This sounds like a job for Sandstorm.io...
Or like any firewall, Nginx config, VPN, etc. Everyone picks a different way to do it, so it's not included in the default sync engine.