Posting unifies, tokens don't
One interface posts a reel to four platforms cleanly. Their OAuth token handling refused to unify at all, which is why I built all four first.

One interface posts a reel to four platforms cleanly. Their OAuth token handling refused to unify at all, which is why I built all four first.

A browser will not attach a bearer token to a page navigation. Swapping the header for a cookie the framework already understood, without weakening it.

TikTok's OAuth flow wants you to copy a code out of a web page and paste it into a terminal. What it took to give keryx a native flow instead.

When a desktop CLI posts on your behalf, the OAuth tutorial assumption of a server holding the client secret collapses. What replaces it.
