Are there going to be more force pushes to the Twitter's "the-algorithm" repository in 2023
14
270Ṁ6262
resolved Jan 2
Resolved
NO

On 2023-03-31 twitter has releases some source code to public in the repo https://github.com/twitter/the-algorithm

The first commit was https://github.com/twitter/the-algorithm/commit/7f90d0c , but later they decied to 'rewrite' the history and has started with the new commit that was "forced pushed" to the repo https://github.com/twitter/the-algorithm/commit/ef4c5eb (Their idea was to delete the first attempt, but because of how github works the first commit is still visible)

In the new commit therer is a commit message:

Please note we have force-pushed a new initial commit in order to remove some publicly-available Twitter user information. Note that this process may be required in the future.

This market is about are there going to be more "force pushes" to the main branch of the https://github.com/twitter/the-algorithm in 2023.

I will resolve this market as 'YES' as soon as I get the info that the force commit has happened. If there is no more force commits in 2023 I will resolve this market as "NO" after it is closed.

Get
Ṁ1,000
to start trading!

🏅 Top traders

#NameTotal profit
1Ṁ47
2Ṁ31
3Ṁ21
4Ṁ20
5Ṁ15
Sort by:

Resolving this as NO

The latest commit is:

commit 72eda9a24f815f6d566818cbf8518138e29d83e9

Author: twitter-team <>

Date: Fri Jul 7 14:01:54 2023 -0700

[opensource] Update home mixer with latest changes

This commit is in the same history line as commit ef4c5eb — the diff shows difference between 2 commits: https://github.com/twitter/the-algorithm/compare/ef4c5eb65e6e04fac4f0e1fa8bbeff56b75c1f98...72eda9a24f815f6d566818cbf8518138e29d83e9 And this means there were no more force pushes.

For reference, here is how it looks when comparing first commit that later was rewritten with force push — https://github.com/twitter/the-algorithm/compare/7f90d0ca342b928b479b512ec51ac2c3821f5922...72eda9a24f815f6d566818cbf8518138e29d83e9 GitHub say:

There isn’t anything to compare.
7f90d0ca342b928b479b512ec51ac2c3821f5922 and 72eda9a24f815f6d566818cbf8518138e29d83e9 are entirely different commit histories.

https://github.com/twitter/the-algorithm/commit/ef4c5eb is still there, so this should resolve NO.

Just to be clear — only force pushes to the main branch will lead to YES resolution. If there are force pushes to some other branches this does not count.

© Manifold Markets, Inc.Terms + Mana-only TermsPrivacyRules