You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I'm writing to request the ability to set community labels on posts submitted via Tumblr's API.
It is important that any post submitted via Tumblr's API be properly tagged with the right community label, otherwise Tumblr cannot correctly decide who these posts should be visible to. Right now, however, I don't see any way to set a community label via Tumblr's NPF post submission (that's the API with the path POST /blog/{blog_identifier}/posts).
For reference, these are the community labels that creators should be able to set, even when using third party apps to submit posts:
The text was updated successfully, but these errors were encountered:
Thanks! We do want to open this up, but as stated in #110 , I'm not exactly sure when this'll be high enough up on our priority list to tackle. Hopefully we can get a better answer there in the next few months.
Thanks for the updating, and apologies for duplicating. 😅 I wrote this before discovering the other issue.
Let me know if you all need any testers for something like this. For context, I added Tumblr support to my startup Postpone, but the lack of community labels is a definite gap in our Tumblr scheduling/analytics support. I hope to add it someday!
Hello! I'm writing to request the ability to set community labels on posts submitted via Tumblr's API.
It is important that any post submitted via Tumblr's API be properly tagged with the right community label, otherwise Tumblr cannot correctly decide who these posts should be visible to. Right now, however, I don't see any way to set a community label via Tumblr's NPF post submission (that's the API with the path
POST /blog/{blog_identifier}/posts
).For reference, these are the community labels that creators should be able to set, even when using third party apps to submit posts:
The text was updated successfully, but these errors were encountered: