X-Git-Url: https://git.sesse.net/?a=blobdiff_plain;f=files%2Ffaq.html;h=54007cde6a9a7b75e7f86cd8d13e6143b7676259;hb=dd3b387113e206600d881da65692a61dcccea869;hp=d4d81897b32fa89d458ddfc8916a6eb9abe28351;hpb=51f6ff0e15c062f0b26d66f43e88c5937932d4c2;p=pr0n diff --git a/files/faq.html b/files/faq.html index d4d8189..54007cd 100644 --- a/files/faq.html +++ b/files/faq.html @@ -75,10 +75,10 @@ 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 + an easy-to-use HTML5 upload 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 + hits a second even without the Varnish 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.
@@ -99,14 +99,13 @@ Debian jessie.The Perl modules aren't really that big â we're talking about only - approx. 3000 lines of code (of which ~20% is the WebDAV part; I should - really make that a bit cleaner once). Most of the real work is done by + approx. 2600 lines of code. Most of the real work is done by the software on which pr0n builds on.
At the time of writing, approximately 720GB of image data (that is, over - 195000 different images), plus cache, plus metadata in the SQL database. +
At the time of writing, approximately 1014GB of image data (that is, over + 258000 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.)
@@ -130,26 +129,13 @@ the images :-) If you really have a novel or cool feature, feel free to contact me (see below). -Unfortunately, no. When and if somebody makes a sane framework for - making WebDAV servers I can use, it probably will, but ATM it's just - too much work for what I need it for. It would be a lot easier if - I only had to support WebDAV level 1, but due to silly restrictions - in Mac OS X' WebDAV client I have to support WebDAV level 2 as well, - and, well, most of that is faked. ;-) In addition, there are multiple - minor features in the system (like autorenaming files on name clashes) - that just aren't easy to adapt to WebDAV. The WebDAV service is - restricted, though, so I guess rather few people will get hurt just - because I'm not fully compliant ;-)
-Try e-mail, or reach me on IRC as Sesse on EFnet, IRCnet, Freenode or OFTC.