Skip to content

Add SAFERATE spec #556

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add SAFERATE spec #556

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions extensions/saferate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
---
title: SAFERATE ISUPPORT token
layout: spec
work-in-progress: true
copyrights:
-
name: "delthas"
period: "2024"
---

## Introduction

This is a work-in-progress specification.

This specification offers a way for servers to advertise that clients will not
be disconnected due to server rate-limiting / anti-flood, and so that the client
can send messages without doing its own conservative rate-limiting.

## The `SAFERATE` ISUPPORT token

This specification introduces the `SAFERATE` ISUPPORT token.

When advertised, the server ensures that a client will not be disconnected due
to server rate-limiting.

The token MUST NOT be advertised with a value.

## Implementation considerations

In order to support this specification, a server can use fakelag to delay
processing new messages rather than disconnect a client. The queue of incoming
messages to process should be bounded.

A client can disable its internal rate limiting when receiving this token.