Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

On Extensions, Userscripts, and Archivers

content.4chan.org

Post reply on HN
Print view View original

11–20 of 41 posts

Re: On Extensions, Userscripts, and Archivers

#11

Post by unimpressive »

soup10 wrote: post #10

Meh, I'm always super unimpressed when simple text based websites have trouble scaling. Everything that's highly requested should be available in memory, and it should be trivial to spit it out instantly. I'm not a scaling wizard, but I'd guess 99/100 times the reason CRUD apps have problems scaling is because they are over-engineered, and there is a tendency to solve scaling issues by adding another layer of complex…

4chan is an image board. None of the content is there long enough to be considered "Highly requested.". And like half the posts have jpeg's and png's attached.

Besides, how does caching solve the "My bandwidth bills are killing my wallet!" issue?

Re: On Extensions, Userscripts, and Archivers

#12

Post by redthrowaway »

Image preloading and autogif are fantastic features, so getting rid of them would be a net negative. Instead, why not have them be controlled by some client side js, so that images/gifs are only preloaded for the next 20 or so posts from what the user is currently reading? If the user stops scrolling, stop preloading. Preload the final 5 or so images to cover skip-to-bottom, but the vast majority of the preloaded images will not be viewed, and so should not be loaded.

Re: On Extensions, Userscripts, and Archivers

#13

Post by ramblerman »

rdl wrote: post #4

The main problem seems to be revenue. With 4chan, you could probably do a unique form of advertising -- companies pay ~$100/cpm to NOT have their products or brand featured on any 4chan pages. :)

Lol, In all seriousness though I'm pretty sure they could still find regular customers without too much trouble.

Not to perpetuate any stereotypes but fleshlight / masculine enlargement products and so forth would be happy to advertise there.

Re: On Extensions, Userscripts, and Archivers

#14

Post by jQueryIsAwesome »

duskwuff wrote: post #5

Stack Overflow has solved a similar problem using WebSockets -- most of their pages will automatically update (e.g, to display the presence of edits, new answers, and added comments) immediately using a socket.

Yeah, totally, and some time _after_ he implements that he should micro-ban anyone making too many requests for the same pages.

Re: On Extensions, Userscripts, and Archivers

#15

Post by saxamaphone69 »

redthrowaway wrote: post #12

Image preloading and autogif are fantastic features, so getting rid of them would be a net negative. Instead, why not have them be controlled by some client side js, so that images/gifs are only preloaded for the next 20 or so posts from what the user is currently reading? If the user stops scrolling, stop preloading. Preload the final 5 or so images to cover skip-to-bottom, but the vast majority of the preloaded ima…

Most users' arguments to that are they open a thread, click preload images/expand images, walk away, and so when the thread is dead/they come back, they have all the posts, and the full resolution images (not thumbnails). And the image expanding is done through userscripts/client side.

Re: On Extensions, Userscripts, and Archivers

#16

Post by nohbody »

redthrowaway wrote: post #9
nohbody wrote: post #6

HTTP 304, Not Modified? There's no accounting for an inconsiderate user base. This has always been a big problem for 4chan. I remember several instances where the site was effectively taken offline for days by a JavaScript virus embedded in PNG images that required the user to follow directions in the image in order to spread.

That wasn't /b/tards being inconsiderate, just mind-numbingly retarded . There's been a few JS worms like that, and it's almost always complete morons spreading them.

The point being that if 4chan users are (on the whole, anyway) too stupid to not spread JS viruses, asking them to not poll the servers so much is certainly a lost cause.

Getting the extension authors on board is probably the best option, because there's only a few of them, and they are not stupid. Stupid users don't have the skills to write broken extensions for themselves.

The only alternative would be (as others have said) to add auto-refresh JS to every page and thus bypass the need for extensions entirely. If the number of people who currently use these extensions is small enough, however, this could just as easily drive their traffic up because now every user on the site gets the same functionality without doing anything.

Re: On Extensions, Userscripts, and Archivers

#18

Post by te_chris »

nohbody wrote: post #16
redthrowaway wrote: post #9

Earlier quoted context omitted.

That wasn't /b/tards being inconsiderate, just mind-numbingly retarded . There's been a few JS worms like that, and it's almost always complete morons spreading them.

The point being that if 4chan users are (on the whole, anyway) too stupid to not spread JS viruses, asking them to not poll the servers so much is certainly a lost cause. Getting the extension authors on board is probably the best option, because there's only a few of them, and they are not stupid. Stupid users don't have the skills to write broken extensions for themselves. The only alternative would be (as others h…

If moot charges by CPM that could solve his cash problem....

Re: On Extensions, Userscripts, and Archivers

#19

Post by gcb »

The key take away is: if you don't look at YOUR server logs, but relay on 3rd party solutions, you are missing the picture. By large.

That Google analytics "guess" was abysmal. Client side logging is fine to complement server side.

Post reply on HN