This code essentially hasn't been updated since release and with some fairly major reworks of how twitter works it seems unlikely nothing ever changed in the last year.
Additionally when it was released the history was scrubbed and it was delayed multiple times to "clean up" the repository. If the goal was transparency keeping the entire history (maybe filter branching to censor personal details from commits which while not being ideal would still be better than what has been done) would have been the way to go as we could have verified ourselves how the algorithm may have been adapted in the past in response to internal/external events.
So this repository in the end is a snapshot that in it's current form probably never ran on twitter as is and currently very likely doesn't anymore either.
At this point it seems more like a PR stunt that was abandoned the moment it generated the positive coverage it was supposed to than an actual effort to be more transparent.
Possible Solution
Start syncing changes made since the release of this repo and in the future, essentially keeping it a mirror of the internal production repo but with the history scrubbed.
Ideally the history would be fixed but transparency about the current would be the most important thing.
Alidonis
commented
3 months ago
This code essentially hasn't been updated since release and with some fairly major reworks of how twitter works it seems unlikely nothing ever changed in the last year.
Additionally when it was released the history was scrubbed and it was delayed multiple times to "clean up" the repository. If the goal was transparency keeping the entire history (maybe filter branching to censor personal details from commits which while not being ideal would still be better than what has been done) would have been the way to go as we could have verified ourselves how the algorithm may have been adapted in the past in response to internal/external events.
So this repository in the end is a snapshot that in it's current form probably never ran on twitter as is and currently very likely doesn't anymore either.
At this point it seems more like a PR stunt that was abandoned the moment it generated the positive coverage it was supposed to than an actual effort to be more transparent.
Possible Solution
Start syncing changes made since the release of this repo and in the future, essentially keeping it a mirror of the internal production repo but with the history scrubbed.
Ideally the history would be fixed but transparency about the current would be the most important thing.