/jp/ - Otaku Culture

>>9754492
>(Optional)
If you post something that looks like spam it may be necessary to enter it.
It will tell you after you post in Fuuka theme, or automatically spawn captcha in the other themes.

>>9577914
I can get the games to run perfectly fine too, but back then it was babby's first 2hu game and I had no idea that it went slow.

>>9577690
I didn't know, but running it slower wasn't by purpose, I was being ironic. I felt really stupid when I discovered I was playing touhou in slow motion as I tried running it on Windows.

>>9577648
He's in charge of declaring if you deserve the autism bucks.

I rather meant on Crossover.

I always play touhou games on my mac under VMWare.

The game goes a good 30% slower and I 1cc.

Web 2.0 a shit.

>>8982788
Hello

I already told Warosu that they can have our databases.

Then, I want to explain the OP post.

For premium I didn't mean "pay for use", and it's written in the post itself. For premium I meant a service that has high value and that needs lots of extra resources to work.
IF we will be out of server power or money, we'll place an ad on top of the page displaying the full image. That's completely fair and unobtrusive.

And no, at least not in a crossbrowser manner, you can't turn the default FoOlFuuka stylesheet to look exactly like Fuuka. display:inline-block is a bad beast, and it can't do magic. On Opera it causes ridiculous CPU spikes, on Chrome it breaks margins, and on Firefox it makes fields go on a new line.
Fuuka and 4chan are coded with tables, FoOlFuuka is coded with blocks. We aren't talking HTML5 here, not even CSS3.

I have an 800 Euro 10" phone and I have no female in my list, OP.

>>8072366
It does work out of the box. I thought Prinny changed something in the URLs because on the first day we couldn't get some URLs outputted right.

We're now on vanilla. Realized that few minutes after i wrote that notice. I was going to merge his changes but there were no differences.

>>8071989
I didn't try Apache, right now I am not using it on any server.
If you're being limited it's more likely to be your MySQL configuration than the CGI wrapper. I found the CGI script impressively fast.

Use this to check your MySQL configuration: https://github.com/rackerhacker/MySQLTuner-perl
Make sure your server doesn't go swapping because of MySQL. It's the performance killer.

>>8070071
With the LOCATION you can play it like we did:
use constant LOCATION_HTTP => '//archive.foolz.us';

This variable in the end doesn't matter I think, because data gets sent to the .pl from Nginx. It's used just to have the right "href"s.

If it makes absolutely no difference, try checking that you are editing the right file and that your FTP works...

>>8070012
Try replacing your fastcgi imports with the following:

fastcgi_param QUERY_STRING $query_string;
fastcgi_param REQUEST_METHOD $request_method;
fastcgi_param CONTENT_TYPE $content_type;
fastcgi_param CONTENT_LENGTH $content_length;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_param PATH_INFO $fastcgi_script_name;

fastcgi_param SCRIPT_NAME $fastcgi_script_name;
fastcgi_param REQUEST_URI $request_uri;
fastcgi_param DOCUMENT_URI $document_uri;
fastcgi_param DOCUMENT_ROOT $document_root;
fastcgi_param SERVER_PROTOCOL $server_protocol;

fastcgi_param GATEWAY_INTERFACE CGI/1.1;
fastcgi_param SERVER_SOFTWARE nginx/$nginx_version;

fastcgi_param REMOTE_ADDR $remote_addr;
fastcgi_param REMOTE_PORT $remote_port;
fastcgi_param SERVER_ADDR $server_addr;
fastcgi_param SERVER_PORT $server_port;
fastcgi_param SERVER_NAME $server_name;

fastcgi_connect_timeout 60;
fastcgi_send_timeout 180;
fastcgi_read_timeout 180;
fastcgi_buffer_size 128k;
fastcgi_buffers 4 256k;
fastcgi_busy_buffers_size 256k;
fastcgi_temp_file_write_size 256k;
fastcgi_intercept_errors on;

>>8069987
>>8069987
>>8069987
THIS.

>>8069937
Had no time to try without. Basically every tutorial tells to keep it off, so it got me worried. I know as much as that if I turn it on I will have to wait for ob to be done, big deal.

>>8069947
Could you show me a pastebin of your server{} block? You should have something like:

server {
listen 80;
server_name archive.foolz.us;
root /var/www/foolrulez/fuuka/;

[what i wrote in the past post]
}

>nginx
Needs no rewriting. Avoid rewriting.
First run the fastcgi-wrapper.pl by using sock, since it's more stable, and then use rules similar to these, change folders accordingly. Could be made simpler, but whatever.

location ~ /image_redirect/(\d*)\.(jpg|png|gif)$ {
gzip off;
include /var/www/foolrulez/nginx/fastcgi-params; #find your params somewhere
fastcgi_pass unix:/var/www/foolrulez/nginx/fastcgi-wrapper.sock;
fastcgi_param SCRIPT_FILENAME /var/www/foolrulez/fuuka/cgi-board.pl;
}

location ~(.jpg|.png|.js|.css) {}

location ~ / {
gzip off;
include /var/www/foolrulez/nginx/fastcgi-params; #find your params somewhere
fastcgi_pass unix:/var/www/foolrulez/nginx/fastcgi-wrapper.sock;
fastcgi_param SCRIPT_FILENAME /var/www/foolrulez/fuuka/cgi-board.pl;
}

Sure I hop in every thread, I am hosting the archives after all.

There's nothing wrong on what I do on /a/. I get asked for info whenever I appear, because our manga are wildly popular on that board. They also menace to hurt Nymphs all the time while asking, so I can't ignore them.

>>8065951
>Especially since Woxxy isn't renting the server ONLY for the archive.
It's a different server from our scanlation one

>a scanlation site bloated with ads
There's no ads outside the reader, and even there it's tame

>forces people to use his shitty online reader
The online reader itself provides the direct downloads.

Gtfo mangafox devs.

>>8065042
Those thumbs are actually back. Just had to merge the image folders.

>>8062642
I wanted to tell my reasons to Eks.

My team can't deal with perl, but we're really good at PHP. I don't think the real effort here is the software, as much as keeping it running. If we want to go a long way, we must turn it into something we can deal with.

For the theme: I was planning to give two interfaces, one with the old fuuka looks, and one with the enhancements. I ended up leaving it like that because I didn't yet have the time to make a switch.

I also think that better HTML could be made, better nestng, with classes and co., so also scripts can be coded for it more easily.

>>8062556
>one picture

The post saving and picture saving are two different Perl threads. It's likely the post was deleted before it could fetch it all. It's called real life.