It is called the Tail Call Optimization for a reason. /s
Tell HN: t.co is adding a five-second delay to some domains
191–200 of 447 posts
Re: Tell HN: t.co is adding a five-second delay to some domains
#192I'd like to invoke Hanlon's razor here to at least cut down on the potential for over-the-top reactions that can be somewhat embarassing in retrospect: "Never attribute to malice that which is adequately explained by stupidity."
The best trick the devil ever played...
Re: Tell HN: t.co is adding a five-second delay to some domains
#193Re: Tell HN: t.co is adding a five-second delay to some domains
#194I think that HN itself also shadow flags submissions from a list of domains it doesn't like. Try submitting a URL from the following domains, and it will be automatically flagged (but you can't see it's flagged unless you log out): - archive.is - watcher.guru - stacker.news - zerohedge.com - freebeacon.com - thefederalist.com - breitbart.com
Well, yes, many sites are banned on HN. Others are penalized (see e.g. https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... ). None of this is secret, though we don't publish the lists themselves. Edit: about 67k sites are banned on HN. Here's a random selection of 10 of them: vodlockertv.com biggboss.org infoocode.com newyorkpersonalinjuryattorneyblog.com moringajuice.wordpress.com surrogacymumbai.com max…
I can't believe you all fell for the whataboutism.
Re: Tell HN: t.co is adding a five-second delay to some domains
#195[flagged]
>I bet rightwing sites had this issue under former management.
If Twitter's previous administration had been doing intentionally bad things as your baseless assertion implies, Musk would be posting the code or database tables and showing it everywhere to prove to the world how bad they were.
The fact that Musk is quiet here demonstrates your assertion is not simply baseless, it's provably false.
Re: Tell HN: t.co is adding a five-second delay to some domains
#196Worth 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. 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_ give you a Location header. To see…
Could you explain what the intended/expected outcome is for this? What is accomplished by doing that?
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.
If the redirects were server side (setting the Location header), a blank referrer remains blank. Client side redirects will set the referral value.
From Twitter’s POV, there’s value in more fully conveying how much traffic they send to sites, even if it minorly inconveniences users.
Re: Tell HN: t.co is adding a five-second delay to some domains
#197Earlier quoted context omitted.
Just tried this - loaded almost instantly. But that's only the link in the profile. Not shared links in tweets. Leaning towards there's something else going on deep in the DNS/ad servers/cdn/who knows. Not the first I've seen/heard of resolving delays with t.co... maybe it's even just something with legacy non-SSL links being redirected etc
You’re really twisting yourself into a buzzword cloud there aren’t you? The link you clicked in the NYT bio is not a t.co link - I assume you noticed that but still are using it as counter-proof?
On mobile, a quick test didn't even look at where the link pointed..... Because all links on twitter are t.co aren't they? Weird you think any links aren't t.co. It's how they track analytics on everything
No buzzwords there, just suspicion there's something else underlying with various technologies that are in play even on a 'simple' link click
Re: Tell HN: t.co is adding a five-second delay to some domains
#198The redirect has always been a bit annoying and I found on mobile if you click a link, see it load the t.co URL, then quickly go back and click again, it instead loads the actual linked URL. So I just instinctively do this now.
Re: Tell HN: t.co is adding a five-second delay to some domains
#199The redirect has always been a bit annoying and I found on mobile if you click a link, see it load the t.co URL, then quickly go back and click again, it instead loads the actual linked URL. So I just instinctively do this now.
The link doesn't magically change. It might be partially cached when you go back and so it seems immediately to be loading the final url but it's not. It's always going to t.co first. C'mon.
Re: Tell HN: t.co is adding a five-second delay to some domains
#200I think that HN itself also shadow flags submissions from a list of domains it doesn't like. Try submitting a URL from the following domains, and it will be automatically flagged (but you can't see it's flagged unless you log out): - archive.is - watcher.guru - stacker.news - zerohedge.com - freebeacon.com - thefederalist.com - breitbart.com
Isn't blocking Stacker.news a petty move? It's basically HN, but you can earn small tips for submissions and comments.
> It's basically HN, but you can earn small tips for submissions and comments.
Guesses it's crypto bullshit
goes to website
Yep, exactly as expected. Karma alone can mess with incentives, I cannot imagine that adding monetary incentive does anything but make it worse. Also crypto has the reverse-midas-touch from everything I've experienced first-hand or read so adding that into the mix is just another black mark.