trypost/resources/js/composables/useXLinkDefuser.ts

28 lines
1 KiB
TypeScript
Raw Normal View History

Defuse links in X posts to avoid the link-post fee (#308) X bills a post containing a URL at a much higher rate than a plain post, and its algorithm demotes link posts. The X version of a post now rewrites every URL non-clickable (https://example.com/post becomes example(.)com/post): scheme and www. dropped, every dot of the host replaced with (.). Leaving a single dot intact would still leave a resolvable domain for X to detect, so all of them are broken. A scheme or www. proves a token is a URL on its own; a bare host only counts when its last label is a delegated TLD, which is the one thing telling acme.com apart from Node.js. That check runs against App\Support\LinkTlds, generated from the whole IANA root zone in every form a TLD can appear in a post -- ASCII, punycode and the Unicode it decodes to -- because whatever X links is what X bills, so a hand-picked subset would leave us paying for its gaps. If the regex engine bails out on pathological input the original content is returned instead of crashing the publisher. The transform lives in the Platform::X arm of ContentSanitizer, so it reaches publishing and the app/API/MCP previews from one place and cannot touch any other network. Off by default; opt in with X_DEFUSE_LINKS. The editor counts characters and renders its preview client-side and cannot ask the server on every keystroke, so the rewrite is mirrored in TypeScript. PHP stays the source of truth: a parity test fails if the two TLD sets drift, and a browser test drives the real editor so the mirror is covered rather than assumed. Without it the composer promised text the network never receives. Character limits now measure the text a reader will see: sanitized, then with markup resolved away. Measuring the raw draft blocked saving posts that publish fine and let through posts the network rejects, and counted the editor's HTML toward the limit. Measuring the sanitized form alone would have counted Telegram's escaped entities, rejecting messages Telegram accepts. Empty content is handled once inside the sanitizer instead of by a guard repeated at every call site.
2026-08-29 18:31:05 +00:00
import { usePage } from '@inertiajs/vue3';
import { computed } from 'vue';
import { contentForPlatform } from '@/lib/defuseXLinks';
/**
* X publishes links defused (`acme(.)com`), so the editor has to count characters
* and preview against that text rather than the draft.
*
* The TLD set arrives as a page prop from `App\Support\LinkTlds` instead of being
* duplicated in the bundle, and the controller sends it only when defusing is on.
* An empty set therefore means the feature is off and every platform gets its text
* back untouched without the list a bare host cannot be told from `Node.js`, so
* defusing half of them would be worse than leaving them alone.
*/
export const useXLinkDefuser = () => {
const page = usePage();
const tlds = computed<ReadonlySet<string>>(
() => new Set((page.props.xLinkTlds as string[] | undefined) ?? []),
);
const contentFor = (content: string, platform: string): string =>
contentForPlatform(content, platform, tlds.value);
return { contentFor };
};