projects
/
pr0n
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
17d4719
)
Update the FAQ.
author
Steinar H. Gunderson
<sesse@debian.org>
Sun, 23 Jul 2006 18:10:38 +0000
(20:10 +0200)
committer
Steinar H. Gunderson
<sesse@debian.org>
Sun, 23 Jul 2006 18:10:38 +0000
(20:10 +0200)
faq.html
patch
|
blob
|
history
diff --git
a/faq.html
b/faq.html
index 3ad0efe287f781a12118073fc7ee545186e13189..677b47689e118b9c611f6f8f32f99665ab2d5d86 100644
(file)
--- a/
faq.html
+++ b/
faq.html
@@
-9,7
+9,7
@@
</head>
<body>
<h1>pr0n FAQ</h1>
</head>
<body>
<h1>pr0n FAQ</h1>
- <p>Last updated July
16th
, 2006</p>
+ <p>Last updated July
23rd
, 2006</p>
<h2>So, what is this pr0n thing anyway?</h2>
<h2>So, what is this pr0n thing anyway?</h2>
@@
-37,7
+37,7
@@
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,
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
over 2GB
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.</p>
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.</p>
@@
-92,15
+92,15
@@
<h2>How much data is there in there, anyway?</h2>
<h2>How much data is there in there, anyway?</h2>
- <p>At the time of writing, approximately 4
4
GB of image data (that is, over
- 3
5
000 different images), plus cache, plus metadata in the SQL database.
+ <p>At the time of writing, approximately 4
5
GB of image data (that is, over
+ 3
6
000 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.)</p>
<h2>Can I get the source?</h2>
<p>Probably, but are you sure you can get it to work? It's
(These numbers are growing rather rapidly, so they could be outdated at
any given time.)</p>
<h2>Can I get the source?</h2>
<p>Probably, but are you sure you can get it to work? It's
- non-trivial to set up, as it depends on
pre-release software
and a lot of
+ non-trivial to set up, as it depends on
lots of odd modules
and a lot of
custom configuring; this is not a pre-made, user friendly package for your
favourite Linux distribution. You can probably get a tarball, but I'm not
going to hold your hand configuring it. :-) If you really want to try,
custom configuring; this is not a pre-made, user friendly package for your
favourite Linux distribution. You can probably get a tarball, but I'm not
going to hold your hand configuring it. :-) If you really want to try,