Re:Twitter is being investigated over data collection in its...
by eli on Sunday October 14, 2018 @07:26PM
(#18216205)
I assume it’s to remove the t.co page from the browser history, which of course is not relevant or useful for curl. There’s nothing in that response that looks malicious.
[ Parent
| on HN ]
Re:Twitter is being investigated over data collection in its...
by pdkl95 on Sunday October 14, 2018 @08:20PM
(#18216456)
They already return different results based on the user agent header; they could easily be returning different results based on other HTTP headers, IP headers, etc.
Arguments that implicitly assume everyone receives the same data from a server are frighteningly common. This is extra strange when it happens on forums like HN that also regularly assume the same server might be A/B testing or providing "targeted" advertising - or prices - that is unique for most users.
Any discussion about data from an unknown server should always include some sort of checksum. Without verification everyone is receiving the same data, statements about a server's responses don't mean much.
Re:Twitter is being investigated over data collection in its...
by tdb7893 on Monday October 15, 2018 @02:14PM
(#18222144)
Couldn't any site be sending different results based on any header? I guess I don't get how "they could easily be returning different results based on other HTTP headers, IP headers, etc" doesn't apply to literally every site
Re:Twitter is being investigated over data collection in its...
by stingraycharles on Monday October 15, 2018 @02:10AM
(#18217739)
As others have pointed out, the same thing can be accomplished using a http redirect. The only purpose this kind of intermediate page has is to hide the HTTP Referer field and make it look like it was coming from t.co. This ensures that only Twitter knows which tweet someone was coming from.
Re:Twitter is being investigated over data collection in its...
by Leace on Monday October 15, 2018 @03:45AM
(#18218079)
Of course for that there is also a standard-compliant way: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Re...