Live data from Hacker News

Source code for the X recommendation algorithm

github.com

131–140 of 156 posts

Re: Source code for the X recommendation algorithm

#131

Earlier quoted context omitted.

For all its flaws .. it’s still a step up from how Parag and co used to run twitter

Unfortunately, this [0] cancels out everything ten-fold. The owner of the website is boosting the content of himself and the people he supports. This did not happen in the old twitter - not even close. [0] https://github.com/twitter/the-algorithm/issues/236

[deleted]

Re: Source code for the X recommendation algorithm

#132

Earlier quoted context omitted.

The reporters should be getting down to the point and asking Elon Musk about the practical usefulness of such a heavily redacted public release.

I can think of like 3 institutions that have reporters who would ask that kind of question (The Register, Ars Technica and 404media) and I don't think Musk is going to be sitting across the table from any of them, ever.

I believe these are the last kicks of a dying horse/bird...

Why you take this so serious? The world is moving on. Nobody will trust anyone with their freedom of speech, ever. Is this so hard to see?

Any centralized solution qucikly implements censoring, starts banning users.

Re: Source code for the X recommendation algorithm

#133
post #66

Not sure if this is the right place to ask, but why does Bluesky feel so much faster to load and interact with compared to X? On the surface, both have similar interfaces and equally rich content, yet Bluesky consistently feels snappier and more responsive, even though it’s the newer platform.

Iiirc, Twitter uses some mongrel version of React Native on the web. That's why you get the 3 seconds long loading thingie whenever you open a new tab.

Re: Source code for the X recommendation algorithm

#134
post #94
post #59

Earlier quoted context omitted.

Nope, nor did that repo have the system prompts that brought is MechaHitler, nor the time earlier this year where it started injecting Trump into every completion. The Grok repo is a smokescreen for deniability (just not particularly plausible).

> Nope, nor did that repo have the system prompts that brought is MechaHitler False, you made that up. https://decrypt.co/329365/bye-bye-mechahitler-elon-musk-xai-... > The Grok repo is a smokescreen for deniability (just not particularly plausible). Completely unfounded conspiracy theory.

I would be surprised if that line in the prompt caused it without the other thing they did just before mecha Hitler: Elon created a Twitter thread asking users to submit divisive politically incorrect facts for grok training. It was full of Holocaust denial and white supremecy stuff.

https://x.com/elonmusk/status/1936493967320953090

Most likely they rolled back finetuning on that thread at the same time they adjusted the prompt.

Re: Source code for the X recommendation algorithm

#135

I browsed through it a bit and these are some details that raised questions or which I found interesting: There's multiple mentions of slop, for example: SlopsAuthorScoreFeature in HomeTweetTypePredicates. That means everyone gets a slop score between 0 and 1, which makes me wish that it was openly visible and that people with a high slop score would get a little piggy emoji next to their name. There's a CLIENT_TWEET…

I assume soft NSFW is non-hardcore content

Re: Source code for the X recommendation algorithm

#136

Earlier quoted context omitted.

Why? I've never been a twitter user

Post Musk Twitter is amazing. It lets you see how stories, opinions that you support or don’t are attacked from all sides and Community noted / @grok fact checked … a lot of UX changes too .. pre Musk, the moderation / banning was biased and arbitrary (who is watching the watchers?) .. my personal fav was to see the special tick removed from journalists ..

Grok is a lickspittle, don't ask it about facts. But the clever thing is that Grok can do meta queries for you ('give me the last 30 users from X who posted about Y using the word...').

Re: Source code for the X recommendation algorithm

#137
post #19

Earlier quoted context omitted.

It’s not. The last “algorithm” release was a random grab bag of code which existed in some of the Twitter repo that might have been tangentially related to recommendations/feed. Source: worked at Twitter in ML/recsys.

[flagged]

This is not believable. It's not syntactically valid Python.

https://github.com/twitter/the-algorithm/blob/c54bec0d4e029f...

Re: Source code for the X recommendation algorithm

#138
post #81

Earlier quoted context omitted.

Not an ML expert, but is it feasible to train the weights using the actual Twitter feed as an oracle?

It would cost a fortune in API calls, so it's not practical for anyone except internally at corporate.

well, Bluesky and Mastodon posts would suffice, but it's still useless because of how redacted the release is

Re: Source code for the X recommendation algorithm

#139
post #137

Earlier quoted context omitted.

[flagged]

This is not believable. It's not syntactically valid Python. https://github.com/twitter/the-algorithm/blob/c54bec0d4e029f...

True, but on the other hand, it's not exactly surprising if they're redacting details related to spam detection, algorithmic manipulation, foreign interference, and other such adversarial phenomena.

(I'm not necessarily saying that's what's going on. But I do seem to recall that when reddit open-sourced, they deliberately chose to redact info related to vote manipulation/spam detection/etc.)

Re: Source code for the X recommendation algorithm

#140
post #137

Earlier quoted context omitted.

This is not believable. It's not syntactically valid Python. https://github.com/twitter/the-algorithm/blob/c54bec0d4e029f...

True, but on the other hand, it's not exactly surprising if they're redacting details related to spam detection, algorithmic manipulation, foreign interference, and other such adversarial phenomena. (I'm not necessarily saying that's what's going on. But I do seem to recall that when reddit open-sourced, they deliberately chose to redact info related to vote manipulation/spam detection/etc.)

Do you also believe it plausible that aside from redacted parts, this module has not been changed in any way on production servers for over 2 years (last commit is spring 2023)?
Post reply on HN