Opened 7 years ago
Last modified 15 months ago
#4446 new defect
Twitter timelines sometimes fail to load
Reported by: | mikeperry | Owned by: | mikeperry |
---|---|---|---|
Priority: | Medium | Milestone: | |
Component: | Applications/Tor Browser | Version: | |
Severity: | Normal | Keywords: | |
Cc: | Actual Points: | ||
Parent ID: | Points: | ||
Reviewer: | Sponsor: |
Description
In #3997, we went through a long litany of tests trying to get to the bottom of some transient twitter failures. In the past couple weeks, they appear to be back. Various queries fail more frequently for Tor, timelines often don't appear on first load attempt, etc.
I have tested Tor vs non-Tor in TBB, and the issue does not happen unless Tor is used as a SOCKS proxy.
I have not yet tested SOCKS vs non-SOCKS or high-latency vs low latency.
I should probably also test authenticated vs unauthenticated in Tor, for completeness.
I'm putting this in component Company because I suspect the Tor IPs could be victim to load balancer starvation on Twitter's end... But obviously I need to do a couple more tests first.
Child Tickets
Change History (6)
comment:1 Changed 7 years ago by
comment:2 Changed 7 years ago by
Note sure if this is relevant, but; What happens if you change the Twitter page back to the old design?
comment:3 Changed 7 years ago by
Hrmm. Looks like there "was" an issue with empty timelines recently, but they "resolved" it:
http://status.twitter.com/post/11952919406/empty-timelines
I am still getting the "Loading tweets is taking a long time" failure messages, though...
comment:4 Changed 7 years ago by
Keywords: | MikePerryIterationFires20111120 removed |
---|
comment:5 Changed 4 years ago by
Component: | Company → Tor Browser |
---|
Did you forget about this ticket, Mike?
The "Company" component is now defunct.
comment:6 Changed 15 months ago by
Severity: | → Normal |
---|
Set all open tickets without a severity to "Normal"
This is a Twitter problem as it happens with many browsers both with SOCKS and without.