What do you want to see?

A user should be able to ban itself from a guild or entire instance even. For safety reasons, guild and instance moderators should not be able to view and/or revoke self-bans.

What do you want to see?

Hear me out, if you can't implement Matrix on your own you're free to get help from the Matrix community. Having a proper alternative to the Synapse/Element ecosystem would make Matrix a thousand times better.

Please make sure to check the following tasks before opening and submitting a PR

• [x] I understand and have followed the contribution guide
• [ ] I have tested my changes locally and they are working as intended
• [x] These changes do not have any notable side effects on other Revolt projects

dietz

I'm not sure If blacklisting [ & ] is right but I'd recommend it also It looks like we are fixing the symptom rather than the cause. One way to fix this errors is by fixing the mention system(Which is I don't know how) and make it to not parse the strings like Discord.

Please make sure to check the following tasks before opening and submitting a PR

• [X] I understand and have followed the contribution guide
• [X] I have tested my changes locally and they are working as intended
• [X] These changes do not have any notable side effects on other Revolt projects

I've created the foundation for the message reporting endpoint.

My rust skills are pretty basic so any issues please let me know.

You'll also need to add the table to the database

Please make sure to check the following tasks before opening and submitting a PR

• [x] I understand and have followed the contribution guide
• [x] I have tested my changes locally and they are working as intended
• [x] These changes do not have any notable side effects on other Revolt projects

I'm not sure If blacklisting [ & ] is right but I'd recommend it also It looks like we are fixing the symptom rather than the cause. One way to fix this errors is by fixing the mention system(Which is I don't know how) and make it to not parse the strings like Discord.

I have read the CLA Document and I hereby sign the CLA

This is how it looks like after a message has been edited.

Now, after you're hovering over the edited message it's overlapping with the time the message was sent.

A simple soulution would be moving the edit note at the end of a message. Example on Discord:

delta seem to currently require the nightly toolchain. In order to reduce the friction of adoption we could specify it explicitly.

$ cargo +stable test
 <snip>
error[E0554]: `#![feature]` may not be used on the stable release channel
 --> src/main.rs:1:1
  |
1 | #![feature(proc_macro_hygiene, decl_macro)]
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0554]: `#![feature]` may not be used on the stable release channel
 --> src/main.rs:2:1
  |
2 | #![feature(async_closure)]
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0554]: `#![feature]` may not be used on the stable release channel
 --> src/main.rs:3:1
  |
3 | #![feature(const_option)]
  | ^^^^^^^^^^^^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0554`.

After changing docker image tag from 0.5.3-alpha.6 to version 0.5.3-alpha.9.

Logs entries:

[2021-11-23T08:45:07Z` INFO  revolt] Starting REVOLT server [version 0.5.3-alpha.9].

[2021-11-23T08:45:07Z` INFO  revolt::database::migrations::scripts] Starting database migration.

[2021-11-23T08:45:07Z` INFO  revolt::database::migrations::scripts] Running migration [revision 10 / 2021-11-01]: Remove nonce values on channels and servers.

[2021-11-23T08:45:07Z` INFO  revolt::database::migrations::scripts] Running migration [revision 11 / 2021-11-14]: Add indexes to database.

thread` 'main' panicked at 'Failed to create server_members index.: Error { kind: CommandError(CommandError { code: 86, code_name: "IndexKeySpecsConflict", message: "An existing index has the same name as the requested index. When index names are not specified, they are auto generated and can cause conflicts. Please refer to our documentation. Requested index: { v: 2, key: { _id.server: 1, _id.user: 1 }, name: \"compound_id\" }, existing index: { v: 2, key: { _id.channel: 1, _id.user: 1 }, name: \"compound_id\" }", labels: [] }), labels: [] }', src/database/migrations/scripts.rs:444:10`

Hello. The bot name in question is 'Fhantom'. This issue has persisted from right after after the deletion of said bot to today (about 40 hrs or so).

I've since chosen a new name, so I won't be needing this name but I digress this seems like a bug.

This includes regular webhook support and specific github webhook support.

• [x] I understand and have followed the contribution guide
• [ ] I have tested my changes locally and they are working as intended
• [ ] These changes do not have any notable side effects on other Revolt projects

Please make sure to check the following tasks before opening and submitting a PR

• [x] I understand and have followed the contribution guide
• [ ] I have tested my changes locally and they are working as intended
• [x] These changes do not have any notable side effects on other Revolt projects

Discord server profile avatar URLs are longer than 128 characters. Raising the length limit would allow bridge bots to bridge server avatars.

What do you want to see?

Outgoing WebHooks: a listener on specified/all public channels and direct messages.

Each trigger should result in an outgoing http request to a specified endpoint. The http request should contain the message id, the message content, the author, the channel id and the channel name.

Use case: externally process the content of the message and, based on your logic, take action (eg. let a bot add a reaction to the message and send a reply message)

I would like to make life easier for Revolt maintainers by implementing Uffizzi previews. Disclaimer: I work on Uffizzi Uffizzi is a Open Source full stack previews engine and is completely free for Revolt (and all open source projects). This will provide maintainers with previews of their PRs in the cloud, allowing them iterate faster and reduce time to merge.

TODO:

• [ ] Intial POC

If the bucket has reset left_until_reset will return 0 which will be inaccurate after deduct is called. So we need to update the reset value.

Please make sure to check the following tasks before opening and submitting a PR

• [x] I understand and have followed the contribution guide
• [x] I have tested my changes locally and they are working as intended
• [x] These changes do not have any notable side effects on other Revolt projects