17 ms·
Ask PG: Is HN Expired Link Eventual Fix Planned?
I believe the expired link issue came from using a new lisp feature, but I'm curious if there is any plans to fix it?
It's a little annoying since I constantly pickup tabs that are a day old, and have to start from the beginning. Hopefully I'm not the only one on HN with that issue.
- btbuildem 13y agoI think it falls under "Not important enough to fix even though everyone complains about it all the time" -- luckily there exist browser extensions that fix what authors of this site couldn't. (CTRL-F for said extensions)
- 11thEarlOfMar 13y agoNo, you are not. It is annoying.
- SamReidHughes 13y agoWhat sort of data structure do you recommend they use to efficiently reconstruct older story orderings?
- baldajan 13y agoWell, I would trade off older story ordering for consistency. Or better yet, rather than return Expired Link, return the "current" story ordering.
- recursive 13y agoNo one's asking for older story orderings. I'd prefer newer story orderings.
- dsuth 13y agoMuch like every other paginated site with constantly updating content in existence. Just link to the next page with whatever the current content for that page is. People can figure out that items they're looking for get bumped from one page to another semi-frequently.
- vl 13y agoYou know, like return entire page instead of an arbitrary cut off?
- michaelmior 13y agoWhat does "entire page" mean? The front page of HN could be nearly infinite in theory if you include all stories every posted. It has to be cut off at some point.
- vl 13y agoMost likely parent complains about the fact that if you read long discussion, then it's capped at 100 comments and at the end there is continue link which expires rather quickly.
- slashnull 13y agoI was about to post about it. I would definitely like to see this one sorted out.
- makecheck 13y agoAlthough this is a significant problem, it’s probably better to use the bottom-of-page links: - “Bugs” (in this case, already seems to be known and talked about; see [1]). - “Feature Requests” for anything that isn’t a bug. [1] https://github.com/HackerNews/HN/issues/11 https://github.com/HackerNews/HN/issues/11
- pchristensen 13y agoThey are continuations stored on the server (not a Lisp-specific feature). There is a limit on the number of continuations stored, which is why older ones come up as unknown or expired. This has been there since Day 1 and will probably never be changed. See also https://news.ycombinator.com/item?id=163696 https://news.ycombinator.com/item?id=163696 https://news.ycombinator.com/item?id=2677469 https://news.ycombinator.com/item?id=2677469
- pg 13y agoClosures, not continuations.
- elwell 13y agoCould you give a quick explanation or a link that explains how that is set up? (closures stored on server) Just curious.
- wlievens 13y agoA closure is a function augmented with implicit references to the context in which it was created. In case of an upvote link it would hold references to the post you could upvote. That reference exists not in the URL but in the closure at the servers side. If you keep these objects in memory indefinitely, you'll run out of ram.
- elwell 13y agoOh, I was assuming some sort of custom implementation for doing that. If it's just hanging around in RAM, fair enough; can't see how that has scaled so well, but hey.
- wlievens 13y agoWell, a closure can't be more than a couple hundred bytes, I guess. If he wants to continue with that technique, I'd hack it like this: use reflection to crawl the closure, isolate the variables bound to the closure context, serialize those (the user id's, post id's, etc). Then the closure code, which will be one of only a few "templates", can be put into a global dictionary. The serialized state goes into the URL parameters. The closure is collected, and "reified" from the global dictionary and URL state once the user performs the action. I don't know if LISP's reflection can pull this off, but I'm pretty sure it's no biggie.
- diminoten 13y agoThis site isn't actively developed, and hasn't been, as far as I know, since it was established in 2007. This is intentional. I forget the specific rationale, however. So no, to answer your question (though I'm not pg), it likely won't be fixed.
- vezzy-fnord 13y agoI'm assuming the minimalism and hackish nature was deliberately chosen to weed out the lowest common denominator and cater only to the niche HN targets.
- supersystem 13y agoThat can't be right? Last time I heard they were all about inclusion by being a gateway.
- qbrass 13y agoThe rationale is that the value provided by fixing the problems is less than the cost of doing the work. This particular problem isn't going to cause tons of people to leave, and fixing it isn't going to cause tons of people to join. Unless someone does the work for free, or manages to get a large portion of the current users to quit over the issue, there's no reason to expect it to be changed.
- pg 13y agoActually we change things almost daily.
- umanwizard 13y agoAny recent examples? (Just curious, not trying to debate you)
- fblp 13y agoI'd guess it'd be under the hood tweaks related to building and maintaining the community (comments and stories)
- ilaksh 13y agoThey are not going to make improvements to Hacker News. They have proven that. They don't have to fix it or make any improvements. They can run a very poorly performing site with no features and a horrible appearance, because they are entrenched, and they literally own quite a large portion of their userbase. Unfortunately no matter how many people invent software that does the same thing as Hacker News but works much better and offer it up for free, nothing will be done. The owner of the site has too much invested in its technology stack (Lisp) and its particular implementation and appearance. The improvements necessary probably require going back on some of those fundamentals, which is never going to happen, because they are too proud.
- kranner 13y ago> they literally own quite a large portion of their userbase. Not literally.
- ilaksh 13y agoThat's debatable, but we are talking about a matter of degrees. Wage-based employment is a moderate improvement upon slavery by direct force. The relationship between investors and startup founders is a moderate improvement upon that, but still has quite a few similarities with traditional slavery.
- kranner 13y agoI pointed it out it because I believed it was exaggeration. To me, similarities don't cut it for 'literally'; it has to be identity.
- jasonwocky 13y agoNot anymore. "Why editors are 'literally' changing the dictionary" - http://www.bbc.co.uk/news/uk-23729570 http://www.bbc.co.uk/news/uk-23729570
- 13y ago
- thekevan 13y agoThe word "fix" assumes it is a problem. You load a page and after a certain amount of time, the next page is expired. I am not saying, "it's not a bug, it's a feature!" I'm just saying that's how it works.
- jacquesm 13y agoIt is a problem.
- vl 13y agoFor practical solution: Install "Hacker News Enhancement Suite" Chrome extension, it solves this and godzillion other problems.
- pg 13y agoIt's not a single thing. There are multiple places that use dynamically-generated links. They make the source very simple. I've gradually replaced them in the most common situations. Replacing more is not in my top 10 priorities for things to fix. The reason is that it's not really what users want. What people come here for is good stories and comments. I doubt we have ever lost a single user over expired links. Whereas stupid or uncivil comment threads have probably cost us lots of users, and indeed, some of the ones I'd least like to lose. So that's the sort of issue I spend time thinking about. Incidentally, for those of you working on startups, this is a good example of why making something people want is not a simple matter of making what they say they want.
- credo 13y ago>>The reason is that it's not really what users want. What people come here for is good stories and comments. I doubt we have ever lost a single user over expired links. Yes, you probably haven't lost any users over expired links However, I think you have inconvenienced a lot of users through the expired links. Sometimes, I think it is good to spend a little bit of effort on helping a large number of users. I'm assuming among readers (who attempt to go past page-1), an overwhelming majority has hit this problem multiple times (and lost time because of this problem)
- ghshephard 13y agoI've been a user for 5+ years, for more hours a day than I would care to admit, and have never run into an expired-link problem that couldn't be resolved with a BackButton, copy+paste. Honestly, it gives HN a bit of charm, and it's never ever really bothered me.
- SiVal 13y agoAmen. What a nuisance. You can keep clicking the next page button to see what other stories there are until you actually read one, after which the next page button will fail, and you'll have to start over again. What's the point of even having more than about three pages? The only way to reach those pages is to keep clicking next while carefully avoiding the temptation to read anything along the way, lest you get sent back to Level 1. I'm not buying the argument that if HN has good stories and comments people will keep coming back and if they come back, it means they want a next page button that fails. A doesn't imply B. If frequent expiration is to remain a feature, would it be possible to have a preference setting allowing us to put the first four pages or so on our front page? Then we could read whatever looks most interesting among the first 120 items instead of the first 30 before we get that expired next button we supposedly don't mind.
- deleted 13y ago[deleted]
- codex 13y agoVisible signs of entropy considered harmful: http://en.m.wikipedia.org/wiki/Broken_windows_theory http://en.m.wikipedia.org/wiki/Broken_windows_theory
- jijojv 13y agoFrom a UI perspective is it too much to ask that instead of showing a FU expired message, just client side redirect the user back to the homepage - should be trivial to implement. On a desktop it doesn't save much due to bookmarks bar but on mobile it saves a lot of effort on starting over.
- IvyMike 13y agoI'd just like it if the "expire links page" said "Expired link, sorry. Here is a link to a fresh top page"
- dserban 13y agoThe issue at hand never annoyed me too much. It can probably be fixed with a browser extension (I'm using HN Enhancement Suite, maybe contact the author and start a discussion?)
- DanBC 13y agoIt is a useful feature, not a bug. People need to refresh the thread before they respond to ot, especially if it is a day old. This ensures they have an uptodate version of the thread and allows them ro see if anyone has already made their point. People clicking next to read past the first page is good. Open any comment pages you want to read in new tabs, and refresh those tabs just before you comment. I strongly agree that there are other problems with HN that need fixing.
- dded 13y agoOne of the worst things about expiring links is that they punish you for taking the time to read articles and long discussions. If I'm just skimming through, there's no problem with expiring links.
- wglb 13y agoexpired link issue came from using a new lisp feature I don't think this is the case. This fix would have a low priority on my list. I would rather have work done on improving the quality of comments and unfortunate high ranking of middlebrow comments.