Hentai@Home (H@H) is a Peer-2-Peer gallery distribution system which reduces the load of the E-Hentai Galleries.
All participating members run a small Java-based client that downloads files from the main E-Hentai server to their computer and passes the files on to people who browse E-Hentai.org and the E-Hentai User Galleries. This allows E-Hentai to serve many more files without using vast amounts of costly bandwidth.
The client may be run freely for any duration of time but it is recommended to run it continuously for as long as possible for maximum rewards.
(See the H@H FAQ topic).
- Java Runtime Environment 6 (the Java SDK 6 is also usable). This should be kept up to date but not on the 7+ series.
- 3 Mbit/s burst upload speed or higher. Users may make limits on how much bandwidth is used per hour if they have a bandwidth cap (100 MB/hour minimum). This requirement varies from region to region.
- 2 GB of hard drive space or higher.
- An open port (cannot be lower than port 80).
- An additional IP address for each additional client.
Obtaining Client Keys
Users who are signing up for their first client simply go to the Hentai@Home page in their My Home area. A flash interface will appear where one may fill in their qualifications. Once submitted, simply wait a few days for approval.
To sign up for any additional clients, please PM Tenboro.
- Ports that can be used for H@H: 80 and any port between 1024 and 65534, except the following: 2049, 3659, 4045, 6000, 6665, 6666, 6667, 6668, 6669.
Maximum burst speed will determine:
- The maximum number of connections that can be had simultaneously (up to 500).
Maximum Connections = 20 + max_burst_speed / 10000
- Maximum disk cache size (in GBs).
Cache Size = max_burst_speed / 10
When the H@H client starts, it contacts one of the H@H main servers which tests the Internet connection on which the client runs in order to check if it can upload data at the configured maximum burst speed. If it cannot the maximum burst speed is reduced (internally) to the measured upload speed in order to prevent the connection from being overloaded.
It might happen that the measured upload speed is significantly lower than real upload speed of the Internet connection, especially if that connection isn't located on the European continent (where the H@H main servers are located). In such a case the H@H client will be underused, and its owner can request a speed test override from Tenboro by sending him proof that the Internet connection the H@H client runs on can upload at a higher speed than the measured speed (by providing a screenshot of SpeedTest's results for instance).
A few command line switches may be given to the H@H application in order to change some of its behaviors:
- Disables the bandwidth monitor which is the part that makes sure the H@H application does not use more upload speed than the value of the "Maximum Burst Speed" parameter. When the bandwidth monitor is disabled, the H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the mean upload speed of the H@H application won't exceed the value of that parameter. However, the H@H application might use as much upload speed as the Internet connection on which it runs can provide in order to send image files, which generally results in upload peaks.
- In some cases, the bandwidth monitor is unable to use the whole maximum upload speed that has been set, which can result in an under-utilization of the H@H application upload speed (and might trigger false overload notifications). In such cases, it is better to disable the bandwidth monitor in order for the H@H application to give better performances.
- Disables the writing of log entries in the log_out file. Enabling this switch might increase the performance of the application by reducing its I/O usage.
- Forces a check of the database for errors (as if the database was dirty).
- Sets the maximum number of connections the application can handle to conn. The default maximum number of connections depends on the max burst speed parameter, and is computed as detailed above. In some rare circumstances the default value is too low and the maximum number of connections needs to be increased slightly in order to avoid triggering false overload notifications. Setting this value to a too high limit might have severe consequences on a client's performance, and impact the whole H@H network badly. DO NOT CHANGE THIS VALUE UNLESS YOU ABSOLUTELY KNOW WHAT YOU ARE DOING!
- Starts the UI in minimized mode (tray icon).
- Disables the free space check so that the application won't err if the space left on the partition that contains the cache folder is less than the configured parameter (or 100MB if that parameter is set to a value less than 100MB).
- Allows the application to use more memory in order to increase its performances (by reducing the number of I/O operations). More specifically, the application will use more memory when building the cached files list, sending the file's content, and it will use a memory cache in order to reduce the number of times the files' access timestamps are updated in the database.
- Forces a check of the entire cache. This is the same as --force_dirty, except that the content of each file in the cache is also checked (which can take a lot of time).
The system will fill the cache will recently in-demand files and will delete least recently used files once it fills up to the set capacity. It is important for users not to manually tamper with any files in the cache as this will cause major trust and cache database issues for the client.
Trust merely indicates how well the client is performing according to other clients. Trust slowly goes up if the client is behaving normally, even if it is not serving files. Negative trust often occurs from improper shutdowns or bad connections. Trust caps at +1000.
Quality measures the long-term overall stability and reliability of a client. It's used together with raw speed and proximity to prioritize clients for file requests.
- Quality varies between 0 and 10000
- New clients and clients that haven't been used for the last couple of days will start out with 0 quality, and it will take several days for it to stabilize at the baseline value
- What constitutes a decent quality rating could vary between parts of the world
The currency known as Hath is also be generated (calculated roughly every minute), which can be used to purchase Hath Perks. The maximum amount that can be earned per day per client is 20 hath (this requires a rate of 300+ hits per minute).
H@H Image Proxy
To use H@H as a proxy for the galleries, users simply need to enable it through their My Settings page. This enables any images viewed in galleries to be loaded through the H@H client. As such, these images are added to the user's H@H cache, making them instantly (re)viewable as long as they remain cached.
Users can utilize the H@H client to download entire galleries as a alternative to the Doggie Bag Archiver or EHTracker. Doing this does not cost any credits or GP. Multiple galleries can be downloaded automatically over time.
- Make sure that a H@H client has been running properly for at least 1 hour (add 15 minutes if coming out of a suspend) and has positive trust.
- In the desired gallery click the "Hentai@Home Downloader" link on the right-side column.
- Save the ".hathdl" file in the "hathdl" subdirectory found under the H@H directory.
As the gallery is being downloaded it will be saved in the "downloaded" subdirectory. When it is finished a file named "galleryinfo.txt" will be placed in the folder with the most current information for the gallery. The client will attempt to download from other H@H clients first but if this fails for 3 attempts it will pull the images from E-Hentai's image servers.
- The speed at which H@H downloads files varies based on the time the client has been online and the rate at which it has served files.
- Only the down-sampled pictures available from the E-Hentai server are downloaded, not the high quality images available from the other downloading options.
- Downloaded files do count against a user's daily image viewing limit. If the limit is hit the client will request extensions in blocks of 100 images costing the user 100 GP each time this occurs.
- This does not match the effect of the H@H Image Proxy in the long-term. Files in the "downloaded" folder are not utilized when viewing galleries on the site but they are likely to be loaded from the "cache" folder since the client also copies them there during the downloading process.
|E-Hentai Galleries Navigation|
|Finding||Gallery Searching • Bounty System • Favorites • Making Requests|
|Directory||Anthologies|| A-Comic J • Comic K-Comic O • Comic P-Comic Z • D-Z |
Retired Anthologies (Pre-2010 • Post-2010) • Non-Dated Anthologies
|Uploading||Making Galleries • Rules of Engagement • Gallery Categories • Gallery Manager • Gallery Descriptions|
|Downloading||Doggie Bag • Hentai@Home • EHTracker • Gallery Readers|
|User Actions||Tagging||Fetish Listing • Mechanics (Namespaces)|
|Other||Mod Power • Renaming • Expunging • Rating • Commenting • Reporting|
|Rewards||Gallery Points • Credits • Hath Perks • Toplists|
|Viewing||Lo-Fi • Multi-Page Viewer • Classic E-Hentai Galleries|
|System||My Home • Technical Issues|