x5315 | 7 years ago | on: Is Twitter causally-consistent?
x5315's comments
x5315 | 7 years ago | on: Is Twitter causally-consistent?
https://developer.twitter.com/en/docs/accounts-and-users/mut...
"If a follow or friend relationship exists it is destroyed."
x5315 | 7 years ago | on: Is Twitter causally-consistent?
This is correct.
When we process a block request from user A -> user B, we remove the follow edges between user A -> user B and user B -> user A, and then add a block edge from user A -> user B.
When we process an unblock request from user A -> user B, we remove the block edge from user A -> user B.
I imagine that the "Aleksey checked that he was following me again" was either client caching, or eventual consistency latency. There's no nightly batch job or anything doing that.
Source: I work on the social graph service at Twitter.
x5315 | 9 years ago | on: Twitter Plans Hundreds More Job Cuts as Soon as This Week
Please see my comment here: https://news.ycombinator.com/item?id=12789001
Only one third party app receives Promoted Tweets, and no third party apps are required to display them.
x5315 | 9 years ago | on: Twitter Plans Hundreds More Job Cuts as Soon as This Week
All third party apps (except a single Enterprise tool) do not receive Promoted Tweets. They're only requested and displayed within the Twitter "Owned and Operated" clients.
x5315 | 10 years ago | on: Airbnb Engineering
"Meet the Nerds"
x5315 | 11 years ago | on: Brands pay Twitter to falsely appear in your following list
I, personally, don't know. We'll have some kind of post-mortem internally to work out what happened, and how to make sure it doesn't happen again.
x5315 | 11 years ago | on: Brands pay Twitter to falsely appear in your following list
I agree. I tend to think of it like this: https://twitter.com/attaboy/status/550003457982087169
x5315 | 11 years ago | on: Brands pay Twitter to falsely appear in your following list
I don't know what comms has said publicly and where, but this is a description: https://news.ycombinator.com/item?id=8823792
x5315 | 11 years ago | on: Brands pay Twitter to falsely appear in your following list
Sorry, this is me: http://twitter.com/x5315. I'll update my bio, how's that?
The 'bug' didn't last for over a year and a half. The product has existed for that long.
The bug was in the advertiser selection process. There was an issue with the job/dataset we use to select which advertisers to choose. It should only have been people in the follow lists.
As for "a change in sort order does not normally change the contents of the lists". Due to the size of some of the lists, we don't load the entire list when we show you the first 20 or so. Therefore, we would require an insertion process.
x5315 | 11 years ago | on: Brands pay Twitter to falsely appear in your following list
This was a bug. We rectified it as soon as the issue was brought to our attention.
The original version of this product launched in March 2013. Its intention was to just "bump" brands in your follow lists to the top, not to start placing Promoted Accounts randomly in the list—what the headline suggests. That was the bug.
x5315 | 12 years ago | on: Report: 44% of Twitter Accounts Have Never Sent a Tweet
Nope.
x5315 | 12 years ago | on: Engineer's Guide to US Visas
I got my bank account with just my passport.
x5315 | 12 years ago | on: Twitter is built on open source software
Sam, you don't hold down a fort. You just hold it. Forts don't fly away. <3.
x5315 | 12 years ago | on: Virgin launches glass-bottomed plane
Isn't this post from the 1st of April?
x5315 | 13 years ago | on: WiFi Signals Caught on Camera
I'm pretty sure the speakers were still there when we left.
x5315 | 13 years ago | on: [] are like Facebook
It's the wrong typeface.
x5315 | 13 years ago | on: Twitter's mandatory link shortener, t.co, was down
What I meant was that we care about uptime, and we're working on improving that.
x5315 | 13 years ago | on: Twitter's mandatory link shortener, t.co, was down
We care. We're working on it.
x5315 | 13 years ago | on: App.net developer incentive programme
page 1
I described how the logic works above, but we're always subject to and victims of replication or cache-expiration latency. So it could have been that.