{"id":40369,"date":"2023-08-16T15:00:08","date_gmt":"2023-08-16T19:00:08","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=40369"},"modified":"2023-08-16T15:00:08","modified_gmt":"2023-08-16T19:00:08","slug":"twitter-delays-urls-for-certain-sites","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2023\/08\/16\/twitter-delays-urls-for-certain-sites\/","title":{"rendered":"Twitter Delays URLs for Certain Sites"},"content":{"rendered":"

Jeremy B. Merrill and Drew Harwell<\/a>:<\/p>\n

\n

The company formerly known as Twitter has been slowing the speed with which users could access links to the New York Times, Facebook and other news organizations and online competitors, a move that appeared targeted at companies that have drawn the ire of owner Elon Musk.<\/p>\n

Users who clicked a link on Musk’s website, now called X, for one of the targeted websites were made to wait about five seconds before seeing the page, according to tests conducted Tuesday by The Washington Post.\nThe delayed websites included X’s online rivals Facebook, Instagram, Bluesky and Substack, as well as the Reuters wire service and the Times.<\/p>\n<\/blockquote>\n\n

Via John Gruber<\/a> (Hacker News<\/a>):<\/p>\n

\n

Purposeful spite and inadvertent bug strike me as equally likely here, and the list of domain that suffer this delay really does look like Musk’s shitlist. But regardless of the cause, the effect is undeniably bad for users: click or tap a link to these popular sites from Twitter, and it takes about 5 seconds for the URL to resolve.<\/p>\n<\/blockquote>\n\n

Nitter, which had been restored, seems to be broken again. The “temporary emergency measure” of requiring logging in shows every sign of being permanent.<\/p>\n\n

hlandau<\/a>:<\/p>\n

Worth pointing out that t.co has always been an instance of an annoying and seemingly unjustified practice I named “nonsemantic redirect”. Rather than legitimately redirecting using an HTTP Location header, it instead is an HTML page with a META refresh tag on it.<\/p>

You don’t see this with curl\/wget because they use user agent sniffing. If they don’t think you’re a browser they will<\/em> give you a Location header.<\/p><\/blockquote>\n\n

yahelc<\/a>:<\/p>\n

The purpose is so that Twitter is seen as the source of the traffic. A lot of Twitter-sourced traffic comes from native apps, so when people click links from tweets, they usually don’t send referrer information.<\/p>

If the redirects were server side (setting the Location header), a blank referrer remains blank. Client side redirects will set the referral value.<\/p>

From Twitter’s POV, there’s value in more fully conveying how much traffic they send to sites, even if it minorly inconveniences users.<\/p><\/blockquote>\n\n

John Gruber<\/a>:<\/p>\n

\n

As I speculated last week<\/a>, nothing you do on Twitter is private. Not your DMs, not your “deleted” DMs, not your searches, not your location (if you’re foolish enough to grant Twitter\/X access to it), not your draft posts.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n