Why don't you Ajaxify HN while you're at it??
So what happened to the HN server?
71–80 of 133 posts
Re: So what happened to the HN server?
#72PG wasn't aware that PetSmart closes an hour earlier on Sundays, so he was forced to wait till opening this morning to get the additional hamsters needed to keep this place running.
Re: So what happened to the HN server?
#73Earlier quoted context omitted.
How can Joe-random-user be certain the server is down?
http://www.downforeveryoneorjustme.com/
Re: So what happened to the HN server?
#74Earlier quoted context omitted.
The superior results from my browser's back button far outweigh the inconvenience of the expired link. I click on a link from the "Ask" front page, reply to the top comment, and my comment appears in the thread. Next I click "back" on my browser and I'm back at the front page of "ask". I do that much more often than I hit an expired link.
Still, why not link to a page offset and just show what is current? Or include it with the current linking and automatically redirect? Pretty basic ux optimization.
I suspect hindering spam and vote manipulation plays a part in the architectural decisions. It also makes it possible to create different HN's for different users - e.g. the hellbanned, royals, and plebeians.
Re: So what happened to the HN server?
#75I have only one portal onto the Internet - this site. I check it first thing and last thing, and when it was down today I had a weird epiphany - I did not mind. HN is not a service, its not a startup trying to get mindshare - its a (luvvie alert) community - and one where the downtime had a known and obvious cause and did not matter - rtm would fix it, I would catch up, I knew this thread would exist and I would stil…
Re: So what happened to the HN server?
#76Saturday, I thought: "This guy (PG) is really brave, everybody is nowadays using virtualized server environments on mulit-core machines and PG just gets some bare metal and puts his app on one core and one thread. WTF, this guy is a genius, single-threaded apps on bare metal FTW, this is so great and I am doing this too." After seeing this thing down for several hours -- and Google hate downtimes, they punish you ins…
Re: So what happened to the HN server?
#77PG wasn't aware that PetSmart closes an hour earlier on Sundays, so he was forced to wait till opening this morning to get the additional hamsters needed to keep this place running.
amazing... Just amazing... Would you happen to know what breed of hamsters he is using?
Re: So what happened to the HN server?
#78Fast is one thing. BUT I'd much rather get rid of the "this link has expired" syndrome. Fast is only impressive if the results are modern.
Re: So what happened to the HN server?
#79Fast is one thing. BUT I'd much rather get rid of the "this link has expired" syndrome. Fast is only impressive if the results are modern.
The superior results from my browser's back button far outweigh the inconvenience of the expired link. I click on a link from the "Ask" front page, reply to the top comment, and my comment appears in the thread. Next I click "back" on my browser and I'm back at the front page of "ask". I do that much more often than I hit an expired link.
Here's an example. Currently if you go to the home page and then click the "More" link at the bottom to go to the next page, and wait long enough, the more link expires. That's because it's currently implemented as something like this (not sure about ARC syntax, I'll use Scheme syntax here, but you get the idea):
(define (show-list-of-posts page-number)
... display the rest of the homepage ...
(link "More" (lambda () (show-list-of-posts (+ 1 page-number)))))
This stores the closure `(lambda () (show-list-of-posts (+ 1 page-number)))` with the free variable `page-number` in a hash table on the server. The URL becomes an index into that hash table. But the only information needed to reconstruct such a closure, is the function body and the free variables. So if we defined an auxilary function: (define (foo page-number)
(show-list-of-posts (+ 1 page-number)))
then we could represent the closure as the pair ("foo",page-number). If we encode that in the URL, then instead of looking up the closure from the hash table, we can reconstruct the closure on the fly. Hence we do no longer have to store anything on the server, and no links can expire anymore.There are some challenges when you want to do this transformation automatically, but they can be overcome.
Re: So what happened to the HN server?
#80Earlier quoted context omitted.
Not trolling but just wondering. What added value does Ajaxifying the site bring to HN?
:) I'd instantly know when I get downvoted for saying something stupid ;) seeing submissions in realtime, reducing load on the HN server. Saving F5 addicts.