search

tumblr / docs

Tumblr's public platform documentation.
Apache License 2.0
109 stars 27 forks source link

Community Labels via API #110

Open PandyLegend opened 1 year ago

PandyLegend commented 1 year ago

Although it is clearly not documented, it's implied here that setting community labels is possible via the API.

I have tried passing has_community_label:true and community_label_categories:"mature" but to no avail on both legacy and NPF new posts.

Is it actually possible and, if so, how would this be achieved and can it be documented?

Thanks

nightpool commented 1 year ago

Hi Andy, two notes:

That I can tell from testing, interactability_reblog, hide_trail, has_community_label, and community_label_categories keep their values when edited via this endpoint with no values set, so omitting them is fine

  1. this doesn't necessarily imply that they can be edited from the API, all that issue is saying is that they don't get changed when the values are omitted.

  2. that bug report is about the tumblr.apiFetch helper that's part of the dashboard, which is designed for browser extensions and works on slightly different rules then the public API. Because browser extensions run in the context of the actual tumblr.com dashboard page and are installed by users with full access to tumblr.com, they can do anything that the Tumblr dashboard does, even if that feature isn't exposed in the public API. My guess is that that accounts for the discrepancy you're seeing in this case.

cyle commented 1 year ago

Hello! We are planning to publicly document the Community Labels API, it's on our todo list. I don't have an ETA right now to provide for when that'll happen, unfortunately.

grantmcconnaughey commented 8 months ago

@cyle Any updates on this? From what I can tell it is still not possible to set community labels via API, but this seems important to ensure that creators are correctly tagging their posts/content and don't get their accounts flagged. Thanks!

cyle commented 8 months ago

Hey @grantmcconnaughey , unfortunately I don't have an update here, this still hasn't reached high enough in our priority list to tackle yet. It may sometime over the next three months, though.