On Twitter, the filtering is done by you (mostly: you can’t choose what content is posted by those you follow, or the comments others post).
On HN, the filtering is done by others (mostly: you can filter by “Show HN”, “Ask HN”, new, etc.)
Twitter is like an RSS feed of specific people/companies/interests that you get to select and everyone’s is unique, where HN is a crowd curated — and dang moderated — list of links, and everyone sees the same list.
I don’t think HN is close at all to what Twitter is (for better and worse).
That's why I read HN via Serializer (disabled all other websites), because I don't really wanna curated HN homepage from certain brigades and I wanna choose what I read and what _I_ find interesting. You can also get your individual URL to share across devices, which I find very useful.
Departing employees are justifiably angry about the events of the past few weeks, but I think a desire to see Musk get his comeuppance has colored too many people's assessment of whether Twitter can stay running with a skeleton crew while they rebuild internal expertise. Working code can stay running on autopilot for an impressively long time.
(Maybe this has been my experience over the past 2 years because our team is just bad at this stuff, but when I relate it to other people working on software like this, I mostly get commiseration).
I'm not taking a position on whether Twitter needs 3000 more engineers to stand a chance of running. I think reports of the death of Twitter are also exaggerated, and I remember reading Dan Luu about bloat at Twitter long before Musk expressed an interest. I'm just saying: it's shocking that the service is running as well as it is right now. Some group of people on that team did a lot of stuff right.
Are you speaking from experience? I think just the other day people on here were wondering if you were still alive! ;)