On Extensions, Userscripts, and Archivers

#1

Post by saxamaphone69 » Fri, Jul 06, 2012, 5:02 AM UTC

On Extensions, Userscripts, and Archivers
content.4chan.org

Re: On Extensions, Userscripts, and Archivers

#2

Post by protosstype » Fri, Jul 06, 2012, 5:08 AM UTC

We must construct additional pylons.

Re: On Extensions, Userscripts, and Archivers

#3

Post by devfagfag » Fri, Jul 06, 2012, 5:24 AM UTC

i would think the answer is fairly obvious. 4chan needs an official API that allows for http connects to remain open. this way extension and 3rd party application developers have something to write software around that doesn't impede the ability to serve standard page GET requests to web users.

Re: On Extensions, Userscripts, and Archivers

#4

Post by rdl » Fri, Jul 06, 2012, 5:40 AM UTC

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. :)

Re: On Extensions, Userscripts, and Archivers

#5

Post by duskwuff » Fri, Jul 06, 2012, 5:43 AM UTC

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.

Re: On Extensions, Userscripts, and Archivers

#6

Post by nohbody » Fri, Jul 06, 2012, 5:50 AM UTC

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.

Re: On Extensions, Userscripts, and Archivers

#7

Post by [deleted] » Fri, Jul 06, 2012, 5:51 AM UTC

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. :)

[deleted]

Re: On Extensions, Userscripts, and Archivers

#8

Post by drivebyacct2 » Fri, Jul 06, 2012, 5:53 AM UTC

Use WebSockets. Use Pubsubhubbub. Outside of that and reducing the minimum poll time, there aren't a lot of ways of solving this problem.

Re: On Extensions, Userscripts, and Archivers

#9

Post by redthrowaway » Fri, Jul 06, 2012, 5:56 AM UTC

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.

Re: On Extensions, Userscripts, and Archivers

#10

Post by soup10 » Fri, Jul 06, 2012, 5:56 AM UTC

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 complexity instead of optimizing the root application.