### Excessive LSP `progress` Notifications During Typing

[TheAngryByrd]

Excessive LSP progress Notifications During Typing

fsautocomplete is sending an unthrottled stream of progress LSP notifications to the client (Neovim) immediately following nearly every keystroke, resulting in notification spam and poor user experience.

Steps to Reproduce

1. Open an F# file with fsautocomplete running.
2. Type rapidly in the buffer.

Actual Behavior

The editor is flooded with constant progress notifications from fsautocomplete and once they reach the current line, they cover up most of the code and hinder further typing.

Expected Behavior

The server should throttle or debounce $/progress reports to a reasonable interval (e.g., $\geq 250\text{ms}$) to prevent notification spam during continuous typing.

Current Workaround

Client-side filtering is required to silence the notifications:

return {
  "folke/noice.nvim",
  opts = {
    routes = {
      {
        -- fsautocomplete spams with notifications when editing
        filter = {
          event = "lsp",
          kind = "progress",
          cond = function(message)
            local client = vim.tbl_get(message.opts, "progress", "client")
            return client == "fsautocomplete"
          end,
        },
        opts = { skip = true },
      },
    },
  },
}

Originally posted by @brokenthorn in #1430

[brokenthorn]

Just an idea, but I don't think throttling progress notifications in the server itself is a good idea. It means that some important notifications might not be sent.

What I think should be done here is to follow other server implementations, where I think the defaults are less verbose and the user has to opt-in to such verbose notifications, and having them documented somewhere might also be a good idea.

Throttling seems more suited to the client receiving the messages, just like how filtering is (see the current workaround).