Programming

17659 readers

129 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

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 [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

GitHub - tjkessler/plemmy: A Python package for accessing the Lemmy API (github.com)

submitted 2 years ago by [email protected] to c/programming

6 comments fedilink hide all child comments

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!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 2 years ago (1 children)

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.

[–] bugsmith 1 points 2 years ago

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.