- Feature Name: (The name of the RFC)
- Start Date: (DD/MM/YYYY)
- RFC PR: https://github.com/revoltchat/rfcs/issues/0000
- Tracking Issue: https://github.com/revoltchat/revolt/issues/0000
- Status: draft
One paragraph overview of the feature
Why is this RFC being made, what does it achieve or solve, what is the expected outcome
Explain the proposal as if it's already in Revolt and you were teaching it to new users.
- Introduce new concepts
- Explain the feature with examples
- What this fixes or adds and what users should think of the feature
- Discuss how this impacts using Revolt, how it makes it harder or easier to use
For internal oriented RFCs such as internal code changes, this should largely talk about how contributors should think about the change and give examples on the impacts.
This is the technical section of the RFC, it should go over in detail:
- Its interaction with other features
- How this will be implemented
- Corner or edge cases
This section should reference the examples in the previous section and disect them in more detail.
Why should this not be added.
- Why is this design the best
- Are there alternative ways to solve this
- Could this be done with existing features or existing solutions
This should include both good and bad outlooks on the proposal. This could include how other platforms, software and hardware solve similar issues if relevent or how any existing proposals have tried to solve the same problem.
- Are there any parts which are not yet designed or you believe need further discussion?
- Do you expect any part of this proposal to change?
- Are there any related issues which you believe are out of the scope of this RFC that could be addressed in a seperate RFC?
How does this RFC impact security - This section might not always be applicable and if you believe it is not, please write your reasoning in this section.
Are there any features or changes that this proposal could enable? How does this proposal impact the future of Revolt?