Live data from Hacker News

Tell HN: t.co is adding a five-second delay to some domains

news.ycombinator.com

431–440 of 447 posts

Re: Tell HN: t.co is adding a five-second delay to some domains

#431
post #354
post #349

Earlier quoted context omitted.

How does this inconvenience users? It sounds like you’re saying site owners will be able to distinguish between users with a blank referer and users whose “referer” was the desktop app. Ignoring the privacy angle, isn’t that a good thing?

Other than the privacy angle a meta redirect is always a bit slower than a location header. You need to send an html page (more bytes) that the browser needs to render and then act on (more work). A location header is nearly unnoticeable, a meta refresh page gives you a flash of a blank interstitial screen. (Not that I had the same annoyance, just explaining the difference to the end user of the two approaches)

With the amount of bloat we have on the modern web, I think sending an HTML meta tag rather than a Location header should be the least of our concerns, when it comes to performance.

If the whole purpose of it is to have browsers send a Referer header, I don't think it's that bad. Even from a privacy perspective, you can configure browsers to not send that header anyway.

Re: Tell HN: t.co is adding a five-second delay to some domains

#432
post #403

Earlier quoted context omitted.

> The reason there isn't a delay the second click is because the redirect is cached locally in your browser. No, because it’s not an HTTP redirect. It’s an HTML page that redirects you using a meta tag, something that the browser doesn’t cache.

Your humble anonymous tipster notes to their skeptical audience that browsers are capable of caching all sorts of things, even something as peculiar as an HTML page.

> browsers are capable of caching all sorts of things, even something as peculiar as an HTML page.

Yes, and this is irrelevant to your previous comment: caching the HTML doesn’t cache the redirect itself.

Re: Tell HN: t.co is adding a five-second delay to some domains

#434
post #432

Earlier quoted context omitted.

Your humble anonymous tipster notes to their skeptical audience that browsers are capable of caching all sorts of things, even something as peculiar as an HTML page.

> browsers are capable of caching all sorts of things, even something as peculiar as an HTML page. Yes, and this is irrelevant to your previous comment: caching the HTML doesn’t cache the redirect itself.

You can lead a horse to water, but you can't make him drink. The delay was not on the HTML page.

Re: Tell HN: t.co is adding a five-second delay to some domains

#435
post #15

I can confirm. NYT shows a five-second redirect delay: "wget https://t.co/4fs609qwWt ". It redirects to gov.uk immediately: "wget https://t.co/iigzas6QBx "

Now do additional testing by adding and setting the http referer to t.co or twitter. Is it Twitter, or is it NYtimes doing this?

You can do that if you want; I don't take orders.

Re: Tell HN: t.co is adding a five-second delay to some domains

#436
post #288
post #26

Earlier quoted context omitted.

This forum never said they’re a free speech haven.

That's true, but it's a bit of an interesting question because "free speech" has different meanings. The thing to understand about HN is that we're trying to optimize for one thing: intellectual curiosity ( https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor... ). Given that, we're not "free speech" in the sense of "post anything about anything" - we have to moderate spam, flamewar, lame comments like "ok bo…

I personally think you guys have it mostly figured out. Kudos.

Re: Tell HN: t.co is adding a five-second delay to some domains

#437
post #269

Earlier quoted context omitted.

That's a very valid point! I simply assumed due to the subject matter (coding discussion, in depth tech industry discussions), the average HN reader would be more well read as opposed to your average X user.

Why? Why do you believe that someone familiar with coding discussion and tech industry discussions to be more likely to be well read than an average person? I am explicitly asking you to reconsider these assumptions, think about where they come from, and think if they have any real data to back them up at all

because someone familiar with coding discussion will likely have a basic grasp on logic and maths.

this alone makes them more ‘well read’ than the average X user, especially considering all the conspiracy theories (and groupthink) floating around on the site.

Re: Tell HN: t.co is adding a five-second delay to some domains

#438
post #148

Earlier quoted context omitted.

We don't have "processes" at HN. The idea makes my skin crawl. Plenty of both left- and right-wing sites are banned and/or downweighted on HN. When a site is primarily about political battle, we either ban it or downweight it. Which of the two we choose depends on how likely the site is to produce the occasional interesting article (in HN's sense of the word "interesting"). That's why The Federalist and World Workers…

What do you mean, "even" Rust programmers feel it? Rust programmers feel it the most. This site is hopelessly biased against Go programmers and towards Rust programmers!

The important thing is to read it to the tune/voice of Peter Tosh doing this bit in Legalize it -

Doctors smoke it

Nurses smoke it

Judges smoke it

Even lawyer too

Re: Tell HN: t.co is adding a five-second delay to some domains

#439
post #321

Earlier quoted context omitted.

You can refer to the full list on the github page[0] (which I find to be pretty accurate). I personally use La Contre-Voie[1] for no particular reason. nitter.net was historically a little less reliable for me due to rate limiting, which is why I initially switched. They worked around the rate limiting issue now, so that may no longer be the case. [0] https://github.com/zedeus/nitter/wiki/Instances [1] https://nitter…

Thanks. Unfortunately, not having any luck with any of them, including lacontrevoie. Nitter.net gives a nim error, the others don't find any tweets

Ahah! I see now you are correct, it was just broken after a good run of stability. Prior to this it had been working well for a month or so.

If the past is any indication, Nitter will be back again eventually, but every time Nitter breaks I drift further and further from caring about Twitter/X at all.

Re: Tell HN: t.co is adding a five-second delay to some domains

#440
post #432

Earlier quoted context omitted.

> browsers are capable of caching all sorts of things, even something as peculiar as an HTML page. Yes, and this is irrelevant to your previous comment: caching the HTML doesn’t cache the redirect itself.

You can lead a horse to water, but you can't make him drink. The delay was not on the HTML page.

> The delay was not on the HTML page.

Nobody is saying that.

Post reply on HN