I feel kinda silly just having spent the long weekend writing a threaded 4chan scraper. This is a super welcome change though. Even if you don't visit 4chan regularly you can't ignore the VAST amount of content people upload there. I imagine some interesting statistics will come of this ( I know I plan to).
Even if you don't visit 4chan regularly you can't ignore the VAST amount of content people upload there. I imagine some interesting statistics will come of this.
That was my reaction too. Beyond statistics, this will make it easier to develop all sorts of user-facing and machine-to-machine applications -- for sharing, grouping, ranking, and linking items, and even for 'overlaying' the content on top of other social networks.
I'd expect the API to be grow and mature over time, and am curious to see what comes out of this experiment.
Came to post this. The only redeemable value in 4chan, in my opinion, is that the fact that posts aren't archived makes for a very interesting social experiment. An API firehose pretty much puts an end to that.
I'm a new graduate student in an American university. As part of my Data Mining/NLP project, I'm wondering if I can do something cool with this fresh API. Any ideas?
Could someone explain to me how this could be leveraged (or if it could be) to gather a sort of stream of messages, a la the Twitter streaming API or reddit.com/r/all/comments.json?
I'd be interested in doing some language statistics and comparing them to the aforementioned networks.
Sadly read-only, though it's not much work parsing the HTML and faking a submit through a Post request. Good luck submitting a 4chan app to Apple's app store though :)
Forgive me if this is a noob question, but does 4chan restrict embedding of images.4chan.org images from external urls? I was just playing around with the API and it seems all the images are rendered as the placeholder image that says "4chan.org".
If this is true, I don't know how to utilize this API to make something valuable since all I can do is get the url or text. Somebody please enlighten me. Thanks!
This sort of protection is usually done by checking the referrer header, which is trivial to set when retrieving something programmatically or when using standard tools like wget. The API seems focused on reducing the processing costs of browser extensions that let the user view the page, but add extra features to the page, anyway. Those would probably still seem like a normal browser view of the image to the site by default even if browser plugins can't perform the trivial client sent header change (not sure if the browser plugin API exposes it).
Why would you hotlink to 4chan-pictures? These get deleted with their thread once the thread hits page 10, anyway, which can happen in under 5 minutes (on the more active boards like /b/)
There are already mobile clients for android and, IIRC there were clients for iOS but were banned from the app store due to some kind of infringement (I think it was adult content)
So I don't think a lot of stuff is going to change, excluding the diminishing server load that happened with old clients/extensions.
I'm sure this is about trying to improve site performance, and charging for it would inevitably cause everyone to continue scraping the HTML, thus defeating the point.
[+] [-] afhof|13 years ago|reply
[+] [-] cs702|13 years ago|reply
That was my reaction too. Beyond statistics, this will make it easier to develop all sorts of user-facing and machine-to-machine applications -- for sharing, grouping, ranking, and linking items, and even for 'overlaying' the content on top of other social networks.
I'd expect the API to be grow and mature over time, and am curious to see what comes out of this experiment.
[+] [-] phogster|13 years ago|reply
[+] [-] calinet6|13 years ago|reply
[+] [-] 54mf|13 years ago|reply
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] Jagat|13 years ago|reply
[+] [-] nyan_sandwich|13 years ago|reply
track usages of phrases over time. (thinking of the recent evolution of "rustled my jimmies" derivatives)
See what topics are trending
Fuck maybe I should build some of this...
[+] [-] bootload|13 years ago|reply
And who. The API just made a group of intelligence hackers very happy indeed.
[+] [-] xefer|13 years ago|reply
[+] [-] moot|13 years ago|reply
[+] [-] tarice|13 years ago|reply
"Everything that could be done with this API has already been done using HTML parsing. This development will simply make those applications faster."
Truth?
[+] [-] lnanek2|13 years ago|reply
[+] [-] andyzweb|13 years ago|reply
[+] [-] ddod|13 years ago|reply
I'd be interested in doing some language statistics and comparing them to the aforementioned networks.
[+] [-] zevyoura|13 years ago|reply
[+] [-] terhechte|13 years ago|reply
[+] [-] Lockyy|13 years ago|reply
[+] [-] volaski|13 years ago|reply
If this is true, I don't know how to utilize this API to make something valuable since all I can do is get the url or text. Somebody please enlighten me. Thanks!
[+] [-] lnanek2|13 years ago|reply
[+] [-] a_bonobo|13 years ago|reply
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] astrojams|13 years ago|reply
[+] [-] unkoman|13 years ago|reply
[+] [-] JD557|13 years ago|reply
So I don't think a lot of stuff is going to change, excluding the diminishing server load that happened with old clients/extensions.
[+] [-] kineticflow|13 years ago|reply
[+] [-] 3143|13 years ago|reply
[+] [-] jonny_eh|13 years ago|reply
[+] [-] evolve2k|13 years ago|reply
[+] [-] joethompson|13 years ago|reply
[+] [-] jasimq|13 years ago|reply
[+] [-] angersock|13 years ago|reply
Because, you know, we need more 4chan in the house.
(EDIT: brief skimming of the comments indicates it may be semi-offensive, so be warmed. We're skimming /b/, after all.)