- cross-posted to:
- foss@beehaw.org
- cross-posted to:
- foss@beehaw.org
Hi everyone,
I’d like to share a project I’ve been working on recently, Plemmy! Plemmy allows you to interact with any Lemmy instance using Python and the LemmyHttp API.
Currently all LemmyHttp functions (POST, PUT, GET) have been implemented.
Feel free to provide feedback or contribute in any way!
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.