Mirrors/the-algorithm
2
0
Fork 0
mirror of https://github.com/twitter/the-algorithm.git synced 2024-06-02 09:18:49 +02:00
Code Issues Packages Projects Releases Wiki Activity

Compare commits

base: Mirrors:ef5f97b16c84747b7e0041a9a2cfeeb725d814fb
Branches Tags
Mirrors:main
...
compare: Mirrors:ed32592fe5be92ebbcfbc2e5c019abd07cf0a124
Branches Tags
Mirrors:main

5 Commits
ef5f97b16c ... ed32592fe5

Author SHA1 Message Date
Yuki
ed32592fe5
Merge 94ba6c0073 into fb54d8b549 2023-05-22 17:40:35 -05:00
Yuki
94ba6c0073
Merge branch 'twitter:main' into change-readme 2023-04-07 21:08:00 +09:00
Yuki
33507b2652
Updata:ReadMe 
Added link to Contributing.md at the end of ReadMe
 2023-04-01 12:48:05 +09:00
Yuki
f4d89594b0 Moved Contributing description from ReadMe.md 2023-04-01 11:00:53 +09:00
Yuki
97868d6d2d Moved Contributing description to a separate file. 2023-04-01 11:00:26 +09:00
2 changed files with 6 additions and 3 deletions
Show Stats Expand all files Collapse all files

5
Contributing.md Normal file
View File

@ -0,0 +1,5 @@
# Contributing
We invite the community to submit GitHub issues and pull requests for suggestions on improving the recommendation algorithm. We are working on tools to manage these suggestions and sync changes to our internal repository. Any security concerns or issues should be routed to our official [bug bounty program](https://hackerone.com/twitter) through HackerOne. We hope to benefit from the collective intelligence and expertise of the global community in helping us identify issues and suggest improvements, ultimately leading to a better Twitter.
Read our blog on the open source initiative [here](https://blog.twitter.com/en_us/topics/company/2023/a-new-era-of-transparency-for-twitter).

4
README.md
View File

@ -64,6 +64,4 @@ We include Bazel BUILD files for most components, but not a top-level BUILD or W
## Contributing
We invite the community to submit GitHub issues and pull requests for suggestions on improving the recommendation algorithm. We are working on tools to manage these suggestions and sync changes to our internal repository. Any security concerns or issues should be routed to our official [bug bounty program](https://hackerone.com/twitter) through HackerOne. We hope to benefit from the collective intelligence and expertise of the global community in helping us identify issues and suggest improvements, ultimately leading to a better Twitter.
Read our blog on the open source initiative [here](https://blog.twitter.com/en_us/topics/company/2023/a-new-era-of-transparency-for-twitter).
Please read [this](/Contributing.md)