Claudius Ellsel

Problem for me is that with the `_v1` method, I get a `429` error every time. Not sure exactly, why (I think, I already tried waiting some time and this...

@tajbowness I get the error in the console, not sure, if it's also logged. This might not be a problem of instagrapi. Not sure. Possibly, it is just that my...

While you probably found the correct workaround, this doesn't seem to be compatible with the already existing methods and setup of instagrapi. @subzeroid (or @tajbowness), as this is a rather...

I hope, you understand my points. Hardcoding values like this and not relying on existing functions is in general a bad practice (maintainability, generalizability, ...). I got it that the...

Here, you can see the current setup: https://github.com/subzeroid/instagrapi/blob/b83a00b6d5c23029d9ab22b573ef26ebc79ef262/instagrapi/mixins/public.py#L209. You can possibly also create a new function there (if needed) and then rely on that one. Please note that there is...

My main argument stands. Hard coding this like you did is not good practice. Also, there is no error handling for the request. The already existing functions provide that already....

I meant hard coding like you did. You hard coded this in the wrong place, where it can't be reused. There is no error handling, no reliance on good, already...

(You can also edit GitHub comments, no need to delete and send a new one)

Here, you can see some part of the already existing request error handling code: https://github.com/subzeroid/instagrapi/blob/b83a00b6d5c23029d9ab22b573ef26ebc79ef262/instagrapi/mixins/public.py#L190C1-L202C54 So I hope this helps you understand, why it is important to rely on existing...

Already better. But still needs some more refactoring, from my perspective. One possible problem now is this line: https://github.com/subzeroid/instagrapi/blob/b83a00b6d5c23029d9ab22b573ef26ebc79ef262/instagrapi/mixins/public.py#L130C13-L130C48 Not sure, but probably we don't want to update the internal...