If you threw strong consistency out the window and kept low latency you're still getting the "make profile private" event well before the user has navigated to the post page and composed a tweet.
The problem is ensuring that event has been propagated all around the world so you aren’t displaying now-private tweets. That’s why we need strong consistency.
I have spent much of my time at this company on this exact problem.
Still linearizable under the insane assumption that the db is always “low latency” which implies it never goes down. The write either happened or it didn’t.
