Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

301–310 of 447 posts

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

#301

Post by mzs »

PenguinCoder wrote: post #236

Additional details I wrangled for this rabbit hole. I don't think it's t.co doing this intentionally, but rather poor handling of 'do you have our cookies or not'. Everyone in this thread _proving things_ without taking into account the complexity of the modern web. man curl -b, --cookie (HTTP) Pass the data to the HTTP server in the Cookie header. It is supposedly the data previously received from the server in a "S…

oh boy... -b takes an option which in your examples is -A and -e, then what follows is interpreted as a URL and you throw away the warnings:

  % curl -vgsSIw'> %{time_total}\n' -b -A "curl/8.2.1" https://t.co/DzIiCFp7Ti 2>&1 | grep '^\(* WARNING: \)\|\(Could not resolve host: \)\|>' 
  * WARNING: failed to open cookie file "-A"
  * Could not resolve host: curl
  curl: (6) Could not resolve host: curl
  * WARNING: failed to open cookie file "-A"
  > HEAD /DzIiCFp7Ti HTTP/2
  > Host: t.co
  > User-Agent: curl/8.1.2
  > Accept: */*
  > 
  > 0.013309
  > 0.112494

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

#302

Post by ChrisArchitect »

ChrisArchitect wrote: post #253
PenguinCoder wrote: post #236

Additional details I wrangled for this rabbit hole. I don't think it's t.co doing this intentionally, but rather poor handling of 'do you have our cookies or not'. Everyone in this thread _proving things_ without taking into account the complexity of the modern web. man curl -b, --cookie (HTTP) Pass the data to the HTTP server in the Cookie header. It is supposedly the data previously received from the server in a "S…

Amen

Good work Penguin. I believe in you

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

#303

Post by kobalsky »

BLKNSLVR wrote: post #102

I'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."

if I had to guess: ugly synchronous code for statistics that hits a dead shard for the target domain and times out.

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

#304

Post by mzs »

PenguinCoder wrote: post #276
ender7 wrote: post #264

Earlier quoted context omitted.

I can replicate this behavior fairly easily in a browser. 1. Open incognito window in Chrome 2. Visit https://t.co/4fs609qwWt -> 5s delay 3. Open a second tab in the same window -> no delay 4. Close window, start a new incognito session 5. Visit https://t.co/4fs609qwWt -> 5s delay returns

What is that attempting to prove or replicate? Here's a simpler test I think replicates what I am indicating in GP comment, with regards to cookie handling: Not passing a cookie to the next stage; pure GET request: $ time curl -s -A "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0" -e ";auto" -L https://t.co/4fs609qwWt > nocookie.html real 0m4.916s user 0m0.016s sys 0m0.018s Using `-b` to pass…

In your second example you are passing the cookie file named ./-A then trying to GET the URL "Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0" followed by https://t.co/4fs609qwWt

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

#306

Post by miki123211 »

hdjjhhvvhga wrote: post #249
johngladtj wrote: post #246

Earlier quoted context omitted.

Censorship is not limited to who does it.

So please explain the difference between censorship and moderation.

I like Scott Alexander's definition[1]. Quoting directly:

> Moderation is the normal business activity of ensuring that your customers like using your product. If a customer doesn’t want to receive harassing messages, or to be exposed to disinformation, then a business can provide them the service of a harassment-and-disinformation-free platform.

> Censorship is the abnormal activity of ensuring that people in power approve of the information on your platform, regardless of what your customers want. If the sender wants to send a message and the receiver wants to receive it, but some third party bans the exchange of information, that’s censorship.

Censorship is somewhat subjective, something that you might find offensive and want moderated might not be considered so by others. Therefore, Alexander further argues that the simplest mechanism that turns censorship into moderation is a switch that, when enabled, lets you see the banned content, which is exactly what HN does. Alexander further argues that there are kinds of censorship that aren't necessarily bad, by this definition, disallowing pedophiles from sharing child porn with each other is censorship, but it's something that we should still do.

[1] https://astralcodexten.substack.com/p/moderation-is-differen...

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

#307

Post by mzs »

hlandau wrote: post #145

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. 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…

No, in fact now t.co even returns an empty body with it's 301 response:

  % curl -vgsSw'&1 | grep '^

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

#308

Post by warrenm »

xNeil wrote: post #269
mrguyorama wrote: post #210

Earlier quoted context omitted.

>The HN crowd is not your average layman - it's largely well read and educated people. People need to stop thinking this. There's no filter in front of the HN sign up. The community here is the same as the community anywhere else on the internet. We aren't special

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.

Being deeply informed on a handful of subjects is not the same as "more well read"

It's "more well read about those subjects" :)

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

#309

Post by RMPR »

ravetcofx wrote: post #280
graybeardhacker wrote: post #274

The solution to X (Twitter) sucking is to stop using it. It will either: get fixed or go out of business and be replaced. It seems we've become a society that rewards bad practices with attention which is all any company on the web is trying to get, your attention.

Mastodon has been a breath of fresh air and you can get a really interesting feed going when you follow the right people and hashtags

And it can handle Twitter scale now

https://blog.redplanetlabs.com/2023/08/15/how-we-reduced-the...

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

#310

Post by flutas »

mzs wrote: post #307
hlandau wrote: post #145

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. 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…

No, in fact now t.co even returns an empty body with it's 301 response: % curl -vgsSw' &1 | grep '^

Firefox:

    https://www.threads.net/@chaco_mmm_roomwindow.opener = null; location.replace("https:\/\/www.threads.net\/@chaco_mmm_room")
Post reply on HN