3 ms·
>The hard part in doing twitter is scaling up your poor clone which works well enough in a single instance for some hundred users, to an architecture of multipl
by bryanrasmussen 6y ago
>The hard part in doing twitter is scaling up your poor clone which works well enough in a single instance for some hundred users, to an architecture of multiple instance serving million users.
That's twitter the server right there.
twitter the client is sending in your tweets, and showing you a list of tweets from other people you are subscribed to in some order - probably chronological.
The twitter client does not need to keep any data (between sessions) but should be usable with just sending off requests for data from twitter's public APIs and posting your tweets to same. (assuming of course as I said that twitter APIs give access to this which I am not sure of)