Squorli Server 0.5.3

Suspended Squorli accounts stay out, members can report accounts and servers to the operator of the directory, and the client says what the directory decided.

Before you update

• Back up first (squorli backup). This version changes the database at its first start: it adds one server setting and, per member, the date until which their Squorli account is suspended. That cannot be undone.
• No new variable, no change to the deploy files. After the backup, squorli update is enough.
• Who gets in changes, for servers that use a directory. A member whose Squorli account (@name) the operator of the directory has suspended is refused while the suspension lasts, and is disconnected if they are connected at that moment. Their membership, roles and session stay; when the suspension ends they are back without signing in again. This is on after the update. Switch it off in Administration > Server ("Refuse suspended Squorli accounts") if your server should decide alone. Server accounts (~name) are never concerned.
• A new desktop app (0.9.0) follows after this server. Older apps keep working; what is listed under "New" reaches their users only with the new app, and browser users with this update.
• Needs a current Squorli Directory (directory.squorli.com is one). With an older directory nothing of the below is offered and nobody is refused.

New

• Suspended Squorli accounts stay out. The directory tells your server when it suspends an account of one of your members. The member sees why they cannot get in and until when, instead of a lost session. Other members see nothing of it.
• Report an account or a server to the operator of the directory. "Report account" in the menu of a member or a friend reports a Squorli account, its name or its picture. "Report server" in the server rail's menu and in the server browser reports a whole server. The dialog of a reported channel message now asks "Who gets the report?": the moderators of the server as before, or the operator of the directory when the moderators do nothing or are the problem themselves. That second way sends the message along as evidence; the server's moderators do not see such a report.
• Notices about your account. A member whose Squorli account was warned, suspended or changed by the operator of the directory sees a notice in the client with the reason, also while chatting. "Understood" marks it as read.
• Servers the directory refused. The client no longer connects to a chat server the operator of the directory has refused, not by its address either. Such a server stays in the member's server rail with a red mark, its page says what happened, and "Remove from the list" takes it out of the rail on all of the member's devices. A server that is allowed again comes back by itself.
• If your own server is refused, its log and the connection check (squorli doctor, Administration > Server > "Check the connection") say who refused it and why. Members who open the client in a browser at your server's own address are not locked out by this.

Fixed

• The friends view says why the directory closed the connection instead of only "No connection to the directory".

---

Image: ghcr.io/danielklessa/squorli-server:v0.5.3 (also :latest). Update an installation made with the install script: squorli backup, then squorli update; with Compose by hand: set APP_IMAGE=ghcr.io/danielklessa/squorli-server:v0.5.3 in .env, then docker compose pull and up -d. Database migrations run by themselves at the start and cannot be undone: back up first. Guide: https://squorli.com/en/docs/install/