The Character Limit That Changed How a Social Platform Handles Links
Archi4 min read
Contents
The Character Limit That Changed How a Social Platform Handles Links#
In early 2023, a product team at a mid-sized social platform shipped a change to its post composer. The setting was small enough to fit in a single line of a config file: a boolean that decided whether a pasted URL counted toward the post character limit. It looked like a formatting tweak. Six weeks later it had reshaped link previews, moderation queues, and the platform's relationship with publishers.
What the toggle actually did#
Before the change, every URL a user pasted was shortened to a fixed 23 characters for counting purposes, regardless of its real length. That number was inherited from an older era of link shorteners, when most URLs ran long and the platform wanted predictable limits. Users could paste a 300-character tracking URL and lose only 23 slots.
The new setting removed that rule. Links would now count at their full length in the composer. The visible limit did not change. The practical space available to anyone posting a link did.
On paper this was a one-character fix: swap 23 for the actual string length. In practice it touched every place the platform measured a post.
The preview problem#
Link previews, the cards that show a headline and thumbnail, were generated by a service that ran on its own schedule. It fetched the URL, read the metadata, and cached the result. That service had been built assuming links were always counted as 23 characters, which meant it never worried about very long URLs appearing inside a 280-character post.
When full-length counting went live, users with long tracking parameters found their posts rejected. The rejection message was generic: over the limit. Support tickets spiked. The most common complaint came from small publishers who used campaign tags on every outbound link. Their URLs routinely ran past 200 characters, and their posts stopped fitting.
The fix was not a code change. It was a product decision about how to trim and display URLs. The team added a preview shortening step that displayed a clean domain and path while counting the trimmed version. That decision, made in a two-hour meeting, is the one that stayed.
Moderation felt it first#
The moderation pipeline matched links against blocklists and reputation scores. Those matches keyed off the full URL string. Once long URLs started appearing in posts, the pipeline's queue depth jumped. Not because there was more bad content, but because more unique strings were arriving, and each unique string triggered a fresh lookup.
Queue latency went from minutes to hours over a weekend. Moderators saw reports sitting unactioned. The team added a cache keyed on the URL's host and path, ignoring query parameters. That cut lookups by roughly 70 percent overnight, according to internal numbers shared with engineering leads.
Why publishers noticed#
Publishers watch link behavior closely. When the counting rule changed, the calculus of what to share shifted. An article URL with five tracking parameters became harder to post. Some publishers dropped campaign tags on social posts and moved that tracking to redirect domains they controlled.
That had a side effect. Redirect domains obscured the final destination from previews, and a handful of users exploited it to route around blocklists. Moderation had to start resolving redirects, which added latency back into the queue. The cycle took about three months to settle, and the result was a stricter rule about redirect chains in previews.
The detail worth remembering#
The 23-character convention was never a law of nature. It was a leftover from a period when link shorteners were common and URLs were treated as opaque blobs. Removing it exposed assumptions in three separate systems: the composer, the preview fetcher, and the moderation matcher. Each system had quietly encoded the same number.
When a platform changes how it measures anything, the blast radius is rarely the surface users see. It is the services downstream that copied an old default and never revisited it. A character count is a contract between teams, even when nobody wrote it down.
What to watch next#
Link handling on social platforms is drifting toward two models. One treats every link as a card with structured metadata and counts it as a fixed unit. The other counts the raw string and pushes trimming onto users and publishers. The first is simpler to moderate. The second is simpler to build.
Whichever way a platform goes, the decision tends to arrive as a small config change with a large tail. The teams that catch it early are the ones that keep an inventory of shared constants, and know which services depend on them. The ones that do not spend a quarter cleaning up support tickets and moderation backlogs.
The character limit itself was never the story. The story was the copied number, buried in three codebases, that nobody owned.
More articles