I’m keeping and showing how old the entry is. Additionally, I plan to notify users to update their information every half a year, since their last update. If they don’t update in one year, I plan to hide, or remove their information automatically.
Just a thought but would't creating a new file for each year make it more maintainable? I can't imagine searching a 100k line file or scrolling through it.
Yeah, that'd be a really nice thing to have! My current (and naive) approach is to just limit to the last 3 years of data. That said, it should be easy to add a date filter as a first step, and potentially have a more ingenious approach for letting the LLM reconcile contradictory statements based on the time at which they were posted.
Easy enough. Added a toggle for showing results that are <2 years old. May need to tune it a bit I guess (maybe 5 years).
Dunno if it's actually useful, we'll have to see. I'm not one to shy away from feature creep though, and a lot of people are requesting these sorts of things...
Here's a proposal. Add the ability to filter out users based on their membership date. You could theoretically use this to associate yourself with people who have been around HN as long as you have. Even setting a minimum threshold to something like 100 days or a year would definitely reduce a lot of noise in the "new" section.
One of the best parts to me is the data is already stored and it has a very high cardinality, so it would work exceptionally well as an indexed field.
That's not a bad idea because in most cases the decision is objective.
Years can go back very far (there was one from 1906 on the front page today) so it would probably have to be text entry. Not sure how to fit that into the UI.
The only thing I miss is the "Past Year" option. I find it really important for filtering out programming stuff that's too old. "Past Month" is too short. I can't understand why it's not there. I've sent the suggestion several times.
I'm slowly adding older papers as I work out the kinks in the site. Down the road when the database is more comprehensive, this should definitely be possible.
reply