x5315

Ah ok. :thumbsup:

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.

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.

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.

"Meet the Nerds"

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.

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.

Nope.

I got my bank account with just my passport.

Sam, you don't hold down a fort. You just hold it. Forts don't fly away. <3.