2 ms·

Could you explain this further? I'm using the generic term "ranking". It seems like you're using a very specific subset of an industry's version of 'ranking', a

Could you explain this further? I'm using the generic term "ranking". It seems like you're using a very specific subset of an industry's version of 'ranking', and you're mixing it with the word "ordering". And, "as anyone who has worked with software development probably knows (definitely should know), ranking/ordering/sorting can be done in many different ways".

notacoward 6y ago
> an industry's version of 'ranking' Citation needed. "Ranking" in plain English is practically synonymous with sorting, and it's no different in computing, unless you're in some very specialized pocket where they've twisted it. The difference is that it's possible to show different posts first within the same set and IMO that's not particularly problematic. What's problematic is when Facebook selects a different set. Those posts I didn't ask for shouldn't just be at the bottom of the list; they shouldn't be on it. In an infinite-scroll world these phases do get interleaved a bit. Query, sort, show top N, repeat. Some posts might get dropped in the "show top N" part, but the point is that those posts I didn't ask for should never even have come back from the first query. In SQL terms, it's the WHERE that's broken, not the ORDER BY or LIMIT. (Yes, I know it's not SQL. I could tell you exactly what it is, but I'm still bound by a legal document that says I shouldn't.) It's really not that subtle or unusual a distinction, and I'm sure most people understood it. Why are you so invested in a weird definition?