Skip to content
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

Expose tag blacklists for remote tag services through the API #1597

Open
roachcord3 opened this issue Sep 21, 2024 · 0 comments
Open

Expose tag blacklists for remote tag services through the API #1597

roachcord3 opened this issue Sep 21, 2024 · 0 comments

Comments

@roachcord3
Copy link

I would like to be able to get the PTR's (or any remote tag service's) tag blacklists from the API. I feel like the "most natural" way to get this would be as part of the Services Object, perhaps only adding it if the user provides an optional parameter when making an API call to /get_service or /get_services.

My use case is that I would like to be able to programmatically rewrite pending tags that would be impacted by the blacklist so that they're unnamespaced (with optional disambiguators,) rather than expect parser developers to create tons of special cases to keep up with the moving target that is the PTR's blacklist, to say nothing of non-PTR remote tag services. E.g.:

  • if substance:glue is pending, replace it with glue (default behavior of my program)
  • if substance:slime is pending, replace it with slime (substance) (behavior of my program when user specifies that substance:* tags should be given disambiguators.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant