Live data from Hacker News

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

news.ycombinator.com

351–360 of 447 posts

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

#351

Earlier quoted context omitted.

Exactly, it is subjective, 0.02% is small in my opinion. Yet I'm getting downvoted and told that isn't small. ¯\_(ツ)_/¯

What's important here is the negative impact of the blacklist on communication. Probably some downvoters mean that the blacklist is big enough that the impact is important, and disagree with your supposed implication that it isn't.

Agreed, you're probably right about that.

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

#353
post #8
post #4

i mean, you can stop visiting the site, no? just leave, bro. it's not that hard. there are other means to connect to people.

You can both stop using the site as a user and still call out the awful stuff they do.

At some point though, the complaining becomes nonconstructive whining. It was already time to move on by the time it changed to X.

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

#354
post #349
post #196

Earlier quoted context omitted.

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

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)

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

#357

This is what I have come to expect from every person that calls themselves a "free speech absolutist." What they actually believe is that they should be able to say whatever they want and do whatever they want, personally, without any consequences for themselves. There is no grander principle than "my ability to do what I want and exert power over others however I want, without critique or criticism." I really wish t…

I call myself a free speech absolutist (or advocate at least, absolutist is more of a slur). False compromises belong in the past. What X is doing isn't free speech at all and they have stated that advertisers will dictate what content will be seen, there is no commitment to freedom of speech at all.

But at least I can hold them responsible for violating their own stated values. The former Twitter leadership just hid content that didn't fit theirs or third parties sensitivities and told me they are doing me a favor.

Restricting speech is always in the interests of those that have the power to shape discussions, so limiting speech is always counter productive.

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

#358
post #211

Earlier quoted context omitted.

And now add browser user-agent to the curl request and watch how slow it gets. - `time curl -A "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/81.0" -L https://t.co/4fs609qwW ` -> 4.730 total - `time curl -L https://t.co/4fs609qwWt ` -> 1.313 total Same request, the only difference is user-agent.

your URLs are different.

Only because I copied the first one incorrectly to put it here. I haven't selected full command, so there is a missing "t" at the end of first link

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

#360

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

Which people and hashtags? Trying to check it out but struggling to find relevant content. Is there a tech community somewhere? The ones I found appeared to be dead.
Post reply on HN