X-Git-Url: https://git.sesse.net/?p=pr0n;a=blobdiff_plain;f=files%2Ffaq.html;h=6de20eefc8ae7cfdae5653546edd2c3716325e5e;hp=7086024087f230dcc27b3ff47dd0a39ee19ac7e4;hb=1077ff24c69b1ebf86c4b96bd86ce2d9107ee3eb;hpb=3f3629cdf0838f8ee48af115918101de21c4d99c diff --git a/files/faq.html b/files/faq.html index 7086024..6de20ee 100644 --- a/files/faq.html +++ b/files/faq.html @@ -9,7 +9,7 @@

pr0n FAQ

-

Last updated July 23rd, 2006

+

Last updated November 16th, 2008

So, what is this pr0n thing anyway?

@@ -32,15 +32,18 @@

Can I download all the pictures for viewing?

Sorry, no. First of all, please don't use any "web mirroring" program to - download all the images -- of course, I can't stop you, but you're + download all the images — of course, I can't stop you, but you're putting a lot of unneccessary load on the system. There are two main reasons for not downloading all the pictures: First, there is a question of copyright; not all images here are taken by me, and I've been given permission to display them here, not to pass them on. Second, - keep in mind that some of the events contain several gigabytes of images -- + keep in mind that some of the events contain several gigabytes of images — do you really need all that? I'd advise you to crank up the thumbnail size to the maximum possible size instead; it's quite comfortable to - browse images on without having to click back and forth all the time.

+ browse images on without having to click back and forth all the time. + (Either that, or use the fullscreen feature — the most obvious + keyboard shortcuts are in place, so it should be comfortable enough for + most uses.)

I just changed thumbnail resolution, why is everything so slow?

@@ -51,49 +54,51 @@ so the next time somebody views the same images in that resolution, it will be snappy as usual.

-

Why didn't you just throw up Gallery?

+

Why didn't you just throw up Gallery? (Or use Flickr, Picasaweb, etc.)

Because it didn't fit my needs, and the same goes for all other systems I've seen. I wanted something no-nonsense that would work for my - purposes -- I don't want to click around endlessly just to watch some + purposes — I don't want to click around endlessly just to watch some pictures. Others are of course free to do as they wish, I can't impose my will on anybody :-)

What are the primary features of pr0n?

Mostly that it's no-nonsense and just works, without being in your way. - Also, it has dynamical rescaling (of good quality -- proper, + Also, it has dynamical rescaling (of good quality — proper, sharp thumbnails, no crappy nearest-neighbor scaling) of both thumbnails and images (most client-side scaling sucks quality-wise, unfortunately), an easy-to-use WebDAV-based upload - interface and in general good performance (being a set of persistent, - optimized Perl modules; I've seen it throw out over 300 hits a second, - but I won't guarantee it would withstand a Slashdot attack ;-) ). Also, - it has quite OK skinning capabilities, so it's able to adapt into - different designs quite easily.

+ interface, cache awareness and in general good performance (being a set + of persistent, optimized Perl modules; I've seen it throw out over 300 + hits a second even without the Squid in front, but I won't guarantee it + would withstand a Slashdot attack ;-) ). Also, it has quite OK skinning + capabilities, so it's able to adapt into different designs quite + easily.

What hardware/software does it run on?

-

pr0n currently runs on an Athlon 64 X2 3800+ with 2GB RAM and ordinary +

pr0n currently runs on an Intel Q9450 (quad-core 2.66GHz) with 8GB RAM and ordinary SATA disks. (The server does a lot of other stuff besides running pr0n, of course.) pr0n itself is a custom-made system by myself, tightly coupled - into Apache 2.0, mod_perl 2.0 and ImageMagick 6.x (as well as various - other Perl modules), using PostgreSQL 8.1 as the back-end - database for metadata et al. The base operating system is Debian etch (ie. “testing”).

- -

The Perl modules aren't really that big -- we're talking about only - approx. 1500 lines of code (of which ~30% is the WebDAV part; I should + into Apache 2.2, + mod_perl 2.0, + ImageMagick 6.x + (as well as various other Perl modules) and + qscale, using + PostgreSQL 8.3 as the back-end + database for metadata et al. The base operating system is + Debian lenny (ie. “testing”).

+ +

The Perl modules aren't really that big — we're talking about only + approx. 3300 lines of code (of which ~25% is the WebDAV part; I should really make that a bit cleaner once). Most of the real work is done by the software on which pr0n builds on.

How much data is there in there, anyway?

-

At the time of writing, approximately 45GB of image data (that is, over - 36000 different images), plus cache, plus metadata in the SQL database. +

At the time of writing, approximately 160GB of image data (that is, over + 69000 different images), plus cache, plus metadata in the SQL database. (These numbers are growing rather rapidly, so they could be outdated at any given time.)

@@ -104,8 +109,9 @@ custom configuring; this is not a pre-made, user friendly package for your favourite Linux distribution. There is a bzr repository at http://bzr.sesse.net/pr0n/, but - going to hold your hand configuring it. :-) (Hint: If you do not know what - bzr is, and cannot find out on your own, pr0n is not for you.)

+ I'm not going to hold your hand configuring it. :-) (Hint: If you do not + know what bzr is, and cannot find out on your own, pr0n is not for + you.)

Will you implement feature X?

@@ -135,7 +141,7 @@ on IRC as Sesse on EFnet, IRCnet, Freenode or OFTC.


- +