New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
content_type is not ignored on incompatible servers #371
Comments
yeah I think the docs should be the behaviour we have (or, ideally: configurable at module level) "not Mainline Mastodon" support is kind of a mess and needs to be reworked, probably, but if you want to go for a fix, I'd ask you to just take the check out |
I'll aim to get a PR in today to remove the check :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the documentation:
However, in the actual logic this is enforced very strictly:
Mastodon.py/mastodon/statuses.py
Line 118 in 47aa316
Expected behaviour: when setting this flag on an incompatible instance (eg. Mastodon) it's either sent to the server (which is safe?) or silently dropped. That way, clients of the library are abstracted from the underlying Mastodon server type.
Actual behaviour: exception is raised.
I'm happy to correct either the code or the docs. It's not clear to me which is the intended behaviour.
Apologies if I've got the wrong end of the stick.
The text was updated successfully, but these errors were encountered: