Replies: 1 comment
-
Added the documentation for the PURL deletion endpoint — sorry I missed that before! As for more granular controls over PURLs across the default and custom domains, I think it’s a great idea. Going to add it to the backlog! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Presently from my understanding, adding a link to a PURL adds that link to any domain pointed to it. So adding https://twitch.tv/zlyciz and selecting 'twitch' would make the custom domain and omg.lol domain set up. In this example, https://spix.url.lol/twitch and https://spix.lol/twitch .
I would like the ability for each domain to be managed, separately, not synced. It should also state the urls that it has registered from each domain, since it was not immediately evident viewing the PURLS page the custom domain I have set works, as it lists url.lol links only. That is why I made the suggestion earlier for adding it, not even knowing it exists.
Additionally if possible, I would love the ability for the API to manage being able to delete PURLS. :)
Beta Was this translation helpful? Give feedback.
All reactions