>>947
My fix works. It's too simple not to. What they're talking about is an unrelated issue involving DamageInc's servers.
To fix it yourself:
1) Download the current official version.
2) Unzip 4chan.v0.4.5.6.xpi (xpi=zip).
3) Go to the chrome directory, and unzip 4chan.jar (jar=zip).
4) Open chrome/content/4chan/4chanLib.js in a simple text editor, and after line 3018 (Ctrl-G in notepad I think), add the following line of code.
FullImageUrl = FullImageUrl.replace( /cb-ws\//, "" );
Notice that it is nearly identical to the preceding one, and that it matches part of the url where thumbnails are now stored. What it does is convert thumbnail urls for the work safe boards to urls for the full image.
5) Update 4chan.jar with the new 4chanLib.js. One way to do this is with the following command
zip -f 4chan.jar
6) Create a new xpi file for your fixed extension. This is just a zip file with extension .xpi containing the following:
- install.rdf
- components/
- chrome/4chan.jar
You can create it with something like:
zip -r 4chan.v0.4.5.6.MYSUPERSPECIALVERSION.xpi install.rdf components/ chrome/4chan.jar
7) In Firefox, File->Open File
and open 4chan.v0.4.5.6.MYSUPERSPECIALVERSION.xpi.
8) Install the extension as normal.
9) ???
10) Profit.