feat: add proposal for a separate delete rules endpoint

[iShibi]

Proposal to introduce a separate endpoint for deleting currently active filtered stream rules as a counterpart of POST /2/tweets/search/stream/rules

[github-actions[bot]]

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. We ask that you agree to the Twitter Developer Agreement and Policy before we can accept your proposal. You can agree by posting a comment with the following text:

---

I have read and agree to the Twitter Developer Agreement and Policy

---

1 out of 2 committers have signed the CLA.
:white_check_mark: @iShibi
:x: @macmerritt90
_{You can retrigger this bot by commenting recheck in this Pull Request}

[iShibi]

I have read and agree to the Twitter Developer Agreement and Policy

[iShibi]

recheck

[bhalsey]

Thank you for your contribution! Our team is reviewing your proposal and will provide feedback in a couple weeks.

[macmerritt90]

Hi @iShiibi. Thank you for your submission. We are grateful for taking the time to author this proposal and for being part of the open evolution of the Twitter API. Sadly, after our review, we decided to reject this proposal as it is with the feedback you’ll read below.

The detailed design proposed sending a request body along with a DELETE request. While RFC 7231 leaves the semantic validity of this design up to interpretation, API platforms have largely converged towards not accepting a request body for DELETE requests. Given the above circumstance, an alternative would be to pass the rule to be deleted as a path or query parameter in a DELETE request. While this could scale fairly well for rule IDs, it makes deletion by rule value particularly cumbersome for the user, and may effectively limit or impair the ability to delete multiple rules by value when the rules are particularly lengthy. We appreciate the proposal of an endpoint to delete all rules, and we can look into ways of enabling this behavior for Filtered stream.

Just because this proposal is being rejected, it doesn’t mean we are going to discard the good parts of it. We feel this proposal contains valuable input for the overall design of POST/DELETE routes. We encourage you to create a broader proposal that takes into consideration the POST/DELETE design of the platform as whole (for example, Manage follows, Manage mutes, Manage blocks, or Manage lists), so we can model these semantics in a coherent way across all current and future endpoints.

[CLAassistant]

All committers have signed the CLA.

[macmerritt90]

recheck