Jason Rhinelander

I'm afraid that setup won't work with current Session because of how onion requests work: the request bounces through the Oxen network, then the last hop is responsible for resolving...

> supporting .onion would require all session clients to have a tor client I was thinking that it would be opt-in support: i.e. in order to access one you need...

Can someone confirm whether this works for Safari? (There are comments in the referenced link that it does, but they are also quite old comments).

At the sogs backend level itself the only sensible implementation here is C, but for higher level interfaces (e.g. in the CLI took, or Session built-in management interface) we will...

Backup for a SOGS using postgresql instead of SQLite would need a separate dump of the database via: ``` pg_dump -Fc sogs >pysogs_db_backup_$(data --iso-8601).pgdump ``` alongside the tar file from...

SOGS doesn't necessarily have (or know) the base URL you are using, e.g. you might be using `https://abc.example.org` but that might also be accessible at `http://example.org:5678`.

> It seems that the "future" part is failing, which suggests that a privilege-granting trigger that should fire when a new group is created is failing to run. That's not...

Yes, though Session doesn't yet have support for updating the newer pysogs room permissions. As a temporary measure, in pysogs you can use this query: ``` UPDATE rooms SET write...

If this is a default `sogs-standalone` deb install then the database will be at `/var/lib/session-open-group-server/sogs.db`, and the `sqlite3` command can be used interact with it (but be careful!): ``` sudo...

The permission model here is additive, not subtractive; in order for someone to be unable to join a room they need to have the read permission removed. But read itself...