Yamboy1 Posted on Jan 8, 2019 What is a "Classic" DEV Post? #meta I am curious as to what makes these posts "Classic", as opposed to anything else. (Also, this is my first post, please don't judge) Top comments (2) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand rhymes rhymes rhymes Follow Such software as dreams are made on. I mostly rant about performance, unnecessary complexity, privacy and data collection. Joined Feb 2, 2017 • Jan 8 '19 • Edited on Jan 10 • Edited Dropdown menu Copy link Hide Hi Yamboy1, welcome to dev.to :-) Thanks to your post I learned something new about dev.to's source code. According to this file a post becomes a potential classic if: has a random tag, chosen by a specific set of tags which apparently changes by user is published and featured (not sure how the latter works) has at least 45 positive reactions is at least 10 months old It can also be just a random high quality article (min 75 positive reactions). Then from the list of the candidates, one post gets chosen at random and put in a cache for 90 minutes. I probably missed something but at least now we both know it's a combination of popularity, user input and randomness :) Collapse Expand Ben Halpern Ben Halpern Ben Halpern Follow A Canadian software developer who thinks he’s funny. Email ben@forem.com Location NY Education Mount Allison University Pronouns He/him Work Co-founder at Forem Joined Dec 27, 2015 • Jan 8 '19 Dropdown menu Copy link Hide Nailed it 😅 (Featured is a manual trigger by admins, basically for this purpose. We’d want to unfeature anything that is now out of date even if it was popular.) Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse
Top comments (2)
Hi Yamboy1, welcome to dev.to :-)
Thanks to your post I learned something new about dev.to's source code.
According to this file a post becomes a potential classic if:
It can also be just a random high quality article (min 75 positive reactions).
Then from the list of the candidates, one post gets chosen at random and put in a cache for 90 minutes.
I probably missed something but at least now we both know it's a combination of popularity, user input and randomness :)
Nailed it 😅
(Featured is a manual trigger by admins, basically for this purpose. We’d want to unfeature anything that is now out of date even if it was popular.)