Earlier quoted context omitted.
Surely that 5 megabytes will break every computer out there.. While we are at it, why not just strip out libc as well? It’s just bloat, right?
It's not a disk space thing.
[deleted]
Twitter's Recommendation Algorithm
871–880 of 1001 posts
Re: Twitter's Recommendation Algorithm
#872Earlier quoted context omitted.
Then what?
In general, I think it's good to limit how much stuff you depend on. Not in an extreme minimalist "write everything from scratch" sort of way, but in a "don't just needlessly add billions of lines of dependency code for the hell of it" sort of way. If you've decided to write a program in Java or another JVM language, you already have some JVM as a dependency, so you might as well use a build system written in it, but…
I think the problem is that there is no good cross-platform build tool and as a project grows it almost always depends on some other runtime/language.
I don't want to manage Cargo.toml or requirements.txt or pyproject.toml or package.json or whatever. It's all the same stuff - just a dag of dependencies, each has it's own type and output and build pipeline and defaults and env vars etc.
Bazem, from what I've heard, is the best. Maybe that is the reason for the lack of adoption - it's very good but not good enough?
PS. I never used Bazel
Re: Twitter's Recommendation Algorithm
#873Earlier quoted context omitted.
If engagement on the tweets of that user goes down after a change has been implemented, you can roll back the change to prevent that user from being negatively impacted.
What if engagements around that user naturally declined, perhaps due to that user going off the deep end. Wouldn’t this just serve to bias the algorithm toward propping up the exposure of that user? Do they even care about the control so long as that user’s engagement is up and to the right?
You do an A/B test so even for the same tweet or same time period, you’re just comparing the new, “treatment” group against the old “control group.”
Re: Twitter's Recommendation Algorithm
#874Great! But nothing is going to change until people realize that the problem is the feedback loop . It's not the recommendation engine itself, it's the fact that there's no way "out" of the feed that the engine produces. It recommends you stuff, you have little choice but to engage with it, and then it trains on that information . This is the problem with most of social media today. It is a very well known problem in…
So , all we need to do is to open source humans?
Re: Twitter's Recommendation Algorithm
#875It's disappointing the comments are so obsessed with the political angle to this that there's a total lack of appreciation (or discussion) of opening up the most influential social media platform in the world.
[flagged]
It has indeed felt a bit like r/LateStageCapitalism or r/antiwork in here, with so many low quality comments that all read exactly the same. I figured it was just because of the tech layoffs that that sort of sentiment has been gaining traction though.
Re: Twitter's Recommendation Algorithm
#876Great pull request here which improves the algorithm: https://github.com/twitter/the-algorithm/pull/17
That would be great (unweighting bluechecks) but they actually plan to go in the other direction: Starting April 15th non-bluechecks won't show up in the "For you" section (the algorithm timeline) at all. Unpaid users are being written completely out of the algo. https://twitter.com/elonmusk/status/1640502698549075972
Followed users will still show
But i agree it is a bad idea. The worst actors have money to buy the blue marks of an army of accounts.
This is basically making it easier for authoritarian governments to abuse it
Re: Twitter's Recommendation Algorithm
#877Earlier quoted context omitted.
They did add an off switch to the for you feed. There's a tab for following, albeit not sorted by time.
But it's not sticky and it's easy to miss when it forces you back to For You. Less of a problem on desktop because you can write a trivial extension to force Following, but not an option on mobile, unfortunately. Following IS sorted by time, though.
Hm it Is sticky for me. On Twitter.com
Re: Twitter's Recommendation Algorithm
#878Earlier quoted context omitted.
Elon is addressing this in the Twitter Space right now. "It definitely shouldn't be dividing people into Republican and Democrats; that makes no sense[...] you've identified something we should be getting rid of right away."
Does it make sense to divide people into Elon and not Elon?
Crazies vs the rest
Re: Twitter's Recommendation Algorithm
#879Earlier quoted context omitted.
Then what?
In general, I think it's good to limit how much stuff you depend on. Not in an extreme minimalist "write everything from scratch" sort of way, but in a "don't just needlessly add billions of lines of dependency code for the hell of it" sort of way. If you've decided to write a program in Java or another JVM language, you already have some JVM as a dependency, so you might as well use a build system written in it, but…
For anything that doesn’t run in “humanly instant” timeframe the startup speed won’t matter - and build tools are definitely in this category.
The fear for Oracle is also completely irrational, Java is probably the safest bet ever — it is not tied to processor architecture, has a specification both on the language and the JVM level (both are uncommon in other platforms), has multiple completely independent implementation and the majority of fortune 500 companies definitely have business critical infrastructure running on top of it, so even if Oracle would do something those can single handedly support the platform indefinitely.
Especially that Oracle has been a surprisingly good steward of the language, and they were the ones that finished open sourcing everything.
Re: Twitter's Recommendation Algorithm
#880Earlier quoted context omitted.
Twitter has this now. The home page is split into two tabs: "For you", the algorithmic feed, and "Following", the reverse chronological feed of just who you follow.
Twitter has always had "chronological timeline" behind a confusing "sparkle" button (except for a brief period a few months back where they removed it, or always defaulted to back to algo timeline? and then restored it a week later) They called it "Latest Tweets" https://web.archive.org/web/20200205092104/https://help.twit...
It would randomly revert back. I like the new layout because sometimes i like a quick peek at the recommendations