Skip to content

Proposal: throttle #37

Description

@Martin-Pitt

I think the throttles should be covered in the definitions. They are a penalty like energy or sleep which are also defined.

For example:

llDamage:
    throttle: ≤10 calls / 30 seconds / recipient
llHTTPRequest:
    throttle:
    - 25 requests / 20 seconds / object
    - 1000 requests / 20 seconds / owner
    - 5 HTTP errors (500 or higher) / 60 seconds / script
llTriggerSound:
    throttle: 22 sounds / second / object

So probably either a simple string or list of strings for multiple throttles.

RegionSayTo seems trickier since it depends on public channel / channel zero and the "thereafter" throttle that is activated after the first, so not sure how to convey that across.

llRegionSayTo:
    throttle: "Applies to Public Channel: 200 messages / 10 seconds / destination THEN 100 messages / 300 seconds / object"

There are also some cases where there are hidden throttles. In that case perhaps some safe guideline could be mentioned with a specifier it is a guideline.


This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #37 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @Martin-Pitt (replace 20 with the amount, and @Martin-Pitt with the user to tip).

📖 If you want to learn more, check out our documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions