Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/transitive-bullshit/twitter-feed-algorithm
TypeScript code exploring what an open source version of Twitter's algorithmic feed might look like.
https://github.com/transitive-bullshit/twitter-feed-algorithm
open-source social-network twitter
Last synced: 14 days ago
JSON representation
TypeScript code exploring what an open source version of Twitter's algorithmic feed might look like.
- Host: GitHub
- URL: https://github.com/transitive-bullshit/twitter-feed-algorithm
- Owner: transitive-bullshit
- License: mit
- Created: 2022-04-19T21:42:14.000Z (over 2 years ago)
- Default Branch: master
- Last Pushed: 2023-01-02T22:49:00.000Z (almost 2 years ago)
- Last Synced: 2024-10-20T01:09:04.691Z (17 days ago)
- Topics: open-source, social-network, twitter
- Language: TypeScript
- Homepage:
- Size: 7.81 KB
- Stars: 43
- Watchers: 3
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
- License: license
Awesome Lists containing this project
README
# Twitter Feed Algorithm
> TypeScript code exploring what an open source version of Twitter's algorithmic feed might look like.
## Intro
This repo contains code samples for a series of articles I'm working on with the aim of exploring what “open sourcing Twitter's algorithm” might look like from a more practical perspective.
## Goals, Non-Goals, and Caveats
- We are only focused on Twitter.
- We will not consider the more general space of algorithmic recommendation engines or other social networks.
- We are only focused on the Twitter's core algorithmic feed.
- Other algorithmically-generated recommendations such as “Who to follow”, “Topics you may be interested in”, “Search”, “Trending”, etc are all out of scope for now.
- Any work towards open sourcing aspects of the Twitter’s core feed algorithm are likely to naturally extend to open sourcing these other recommendation algorithms in the future.
- We are only focused on high-level business logic and pseudocode.
- Our goal is to drive a more transparent discussion around the Twitter feed’s core business logic and data models without worrying too much about the underlying engineering complexity.
- The engineering challenges inherent in running a global, low-latency, highly reliable production system like Twitter are immensely important in practice but will be considered mostly out of scope for the purposes of this discussion.
- It’s important to keep in mind, however, that there is an incredible amount of engineering complexity hidden behind a platform like Twitter. We won’t be diving into databases, services, machine learning techniques, networking, infrastructure, devops, etc.
- We will defer to the core data models from [v2 of Twitter’s public API](https://developer.twitter.com/en/docs/twitter-api) wherever possible, including the [Tweet](https://developer.twitter.com/en/docs/twitter-api/data-dictionary/object-model/tweet) and [User](https://developer.twitter.com/en/docs/twitter-api/data-dictionary/object-model/user) objects.
- Twitter likely uses many different abstractions for these resources under the hood, but for the purposes of an open source algorithm, we should remain consistent with the resource models published by the latest version of [their public API](https://developer.twitter.com/en/products/twitter-api).
- This project uses TypeScript because it's what I'm most comfortable with, but it could easily be ported to other languages.
- Any real open source solution would need to come from Twitter itself.
- E.g., you can consider this project for education purposes only.## License
MIT © [Travis Fischer](https://transitivebullsh.it)
Support my open source work by following me on twitter