Jason Rhinelander

Upon installation of the sogs-proxied package you should have a: ``` /etc/nginx/sites-available/sogs-proxy ``` set up for sogs, and a symlink to this in `/etc/nginx/sites-enabled/sogs-proxy` that activates it. Can you check...

There is PR #88 as a starting point, but I'm not entirely sure how persistent long-term storage works there (I think it's more intended for a dev environment).

> doesnt this break backwards compat? There's no such endpoint right now; clients in the group collect member lists from the authors of posts they observe.

This actually needs to be changed on the Session side to change what it expects for SOGS URLs, so that it understands a URL such as `http://sog.caliban.org/r/espanol?public_key=...` (i.e. with the...

It doesn't exactly run as root, but rather as the `_loki` user it installs during installation (which owns the files, including the database, etc.). It needs root to be able...

The wrapper script itself is pretty simple: https://github.com/oxen-io/session-pysogs/blob/debian/sid/debian/sogs

Currently this isn't installing this init script with the `oxend` package. I *think* it should be enough to rename it to `debian/oxen-node.init` to have debhelper automatically notice and install it...

Oops, that name wasn't quite right and it needed an addition to the rules file; I pushed a commit to fix it. Can you give the resulting debs a try...

That error generally means that an oxend is already running, bound to the p2p port. I suspect it is running already here via systemd?

It's important to also think about the reason for the 3750 cap: we want it to be non-trivial to spin up a bunch of nodes onto the network controlled by...