this post was submitted on 21 Jun 2023
27 points (100.0% liked)
Programming
423 readers
10 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Just checked it out. Big fan of the simplicity you've kept with this. Do you think it would be worth adding in some kind of rate limiting functionality?
I believe rate limits (messages, images, sign-ups etc.) can be defined for a site 1.) on creation using the create_site function and 2.) editing a site using the edit_site function.
I think that is if you are setting the rate limit for a new instance (which I suppose could only be useful when automating instance setup? Otherwise, I don't see a purpose for those endpoints).
What I meant was rate limiting functionality client side. So you can respect the rate limit of whatever instance you are interacting with. Either some kind of token bucket or exponential backoff.