revoltchat / backend Goto Github PK

API reports a user's status as Invisible instead of reporting it as if the user was actually offline.

Specification is ready, now implementing.

Routes to implement:

• Create Bot
• Fetch Owned Bots
• Fetch Bot
• Edit Bot
• Delete Bot
• Fetch Public Bot
• Invite Public Bot

Allow clients to not receive the entire object.

Allow users to select a group icon and users when creating a group.
Requires API work to support icons on creation.

Have an option in the setting for non-friends to open direct messages with you.
Some users might prefer to have clean friend lists while still talking with many users from their servers.
Possibly two levels, one for friends and people from your servers and another for anyone on the platform.

To prevent users disappearing / appearing on members list, allow clients to reconnect within a set period of time and then send any buffered messages to them.

Currently this is handled by the client for channels by checking channel name.

The field should only be serialised if true, something like so:

#[skip_serializing_if = "it is false", default = "false"]
pub nsfw: boolean

Note: Prevent Web Push notifications being generated for nsfw channels, or otherwise add a server flag for this.

Provide a query parameter such as include_user

Ping packets do not get a response right now.

E: Switch to WS spec ping packets.

Give users the ability to mention all users in a server.
This will also require a separate permission for sending it.

Basically we should allow changing to the same nickname

The following two routes should be deprecated:

• GET /users/relationships
• GET /users/:id/relationship

See here for a bit of reasoning:
https://app.revolt.chat/server/01F7ZSBSFHQ8TA81725KQCSDDP/channel/01F8PZ2ZHPZFCHAEGQQWSMMF3N/01FDJVA29TSRY2NQD3R4D6FTXH

Marking as high priority so people stop bugging me about it.

Add a way to rank roles against each other.

Give users a way to react to messages with emojis.

Summary

Inside the "System Message Channels" section of server settings, you can set voice channels as a system message channel. Voice channels do not have text chats for system messages so they should not be listed.

Steps to Reproduce

1. Open the settings page for a server you have permissions to change settings of and that has at least 1 voice channel and text channel added to the server.
2. Scroll to the bottom of the "Overview" page to the section "System Message Channels"
3. Click on one of the drop-downs. Voice channels will be listed in them.

Potential Fixes

• Only list text channels in the "System Message Channels" drop-downs. Filter out voice channels.
• Add some form of system message support to voice channels that makes sense (Ex. text channels grouped with voice channels, voice notifications).

Screenshot

They should not be included in the Ready payload to avoid issues.

authifier/authifier#20

Instead of relying on environment variables, configure Revolt nodes through the database.
We should also merge the file server configuration into the database and serve it to clients.

Allow users to report a message or attachment.

but i can login with jp vpn
why is this happening?

Right now we rely on the web socket to find out what attachment objects become and do guess work on the library's part in other cases.

This change requires changes to https://gitlab.insrt.uk/revolt/api

Allow users to customise whether server members get notifications in a server or channel.

Rate limiting is now available, add it to the remaining routes.

Add a way to send messages into channels using an unauthenticated (does not require session token) HTTP request (secret key in path).

Currently the server uses is_online which only checks the local WebSocket connections.

Instead of using MongoDB to pass around events, instead use Redis's Pub/Sub.
If anyone has any alternatives to consider please list them below.

Include the server object and any channels the user has access to.

Bug in Websocket, Useless packets

Updating the user status causes to:

The above data from the websocket, UserUpdate

• Note: I've changed the user stutus only two times!

This so we can avoid this problem:

The manage roles permission gives two different abilities to users, to assign and remove roles on other users and to create, edit and delete roles.
Having those two always come together is unnecessary and may cause issues in many situations.
That is why the permission would be best split into two.

Instead of sending the Message packet to clients, we should generate the Notification object clients display instead.

Note: We also need to handle mentions in servers!

Let clients know when they're sending bad data for better debugging.

It seems that most of the API uses colour but there's one color field in the Embed metadata which is a bit inconsistent.

For example GET https://api.revolt.chat/users/relationships with no auth headers returns:

<!DOCTYPE html>
<html lang="en">

<head>
	<meta charset="utf-8">
	<title>500 Internal Server Error</title>
</head>

<body align="center">
	<div role="main" align="center">
		<h1>500: Internal Server Error</h1>
		<p>The server encountered an internal error while processing this request.</p>
		<hr />
	</div>
	<div role="contentinfo" align="center">
		<small>Rocket</small>
	</div>
</body>

</html>

This isn't specific to the listed endpoint and is happening to more endpoints (e.g. /users/:user or /channels/:channel)

We currently don't subscribe to new topics.
We could change how it works with #1

This might not be necessary, but check whether we can optimise getting guards.