- 1 General Information
- 2 Signing Up
- 3 Installation Guides
- 4 Limits
- 5 Activity
- 6 Scheduler
- 7 Software
- 8 Cache
- 9 Trust
- 10 Quality
- 11 Rewards
- 12 See also
- 13 Forum Links
All participating users run a small Java-based client that downloads files from the main E-Hentai servers to their computer and passes those files on to people who browse the E-Hentai Galleries. This allows E-Hentai to serve many more images using less server 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.
|Java Runtime Environment||
|100 MB/hour bandwidth||Users may limit how much bandwidth is used per hour.|
|10+ GB of hard drive space||SSDs are ideal; write endurance is not an issue.|
|An open TCP port||
|A unique IPv4 IP address||1 per every operational client.|
Obtaining Client Keys
Users signing up for their first client simply go to the Hentai@Home page in their My Home area. A flash interface will appear where users may fill in their qualifications. Applications typically take a few days to process.
For any additional clients please PM Tenboro. For users wishing to run more than 5 clients the average quality of their existing clients must be stable 7,000+ before more keys are assigned.
- FreeBSD with Jails
- Rented Server
- Python Client
A client's 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
- The maximum disk cache size (in GBs).
Cache Size = max_burst_speed / 10
- Having static ranges assigned allows a client to exceed this maximum.
When the H@H client starts it contacts one of the H@H control servers which tests the connection of the client 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 is possible for the measured upload speed to be significantly lower than real upload speed of the Internet connection. In such a case the H@H client will be underused and its owner can request a speed test override from Tenboro by sending proof (e.g. a screenshot of their SpeedTest's results).
An H@H client needs to maintain a Trust of 0, Quality of 2,500, a cache of 2 GB, and max tested speed of 80 KB/s. Failure to reach any of these requirements will make it idle on the network and wait until the requirements are reached.
Each client can be scheduled to use less than its maximum burst speed and bandwidth. These can be based on particular days but are limited to using precise times (every hour on the hour). Schedules are read and cached at the start of each hour so changes won't apply until the start of next hour.
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 prevents the client from using more upload speed than the value of the "Maximum Burst Speed" parameter. The H@H dispatcher will still respect the "Maximum Burst Speed" parameter so that the mean upload speed of the client won't exceed that value. However the client might use as much upload speed as its connection provides in order to send 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 client's upload speed (and might trigger false overload notifications). In such cases it is better to disable the bandwidth monitor in order for the client to give better performances.
- (Can also be requested from the client's settings page)
- Disables the archive download speed limit.
- (Can also be set from the client's settings page)
- Disables the opening, creation, and writing to the log_out file. Enabling this switch might increase the performance of the application by reducing its I/O usage.
- Flushes the log to disk for every written line. This will increase I/O; mostly recommended for when the log is written to a ramdisk.
- 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, 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 too high 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!
- Overrides the port set in the client's settings. This allows running H@H on port 80 on Linux as a non-priviledged user. This can be achieved by adding the following rules to iptables:
iptables -A INPUT -p tcp --dport 80 -j ACCEPT iptables -A INPUT -p tcp --dport 7777 -j ACCEPT iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 7777
- Checks the cache for errors.
- 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).
- (Can also be requested from the client's settings page)
- Forces a check of the entire cache. This is the same as --rescan-cache with the addition that the SHA-1 hash of each file is also checked; this can take a long time.
- Limits the use of memory to mem (in MB).
These arguments allow for changes to the locations of these directories. Quotes are required if there are spaces in the path. H@H will attempt to create the directory if it does not exist. Only log and temp may share a directory.
Windows: --download-dir="c:\some download dir with spaces" Linux: --cache-dir=/some/cache/location --temp-dir=/dev/shm/hath --log-dir=/dev/shm/hath
The system fills a client's cache exclusively with static ranges of files. Users should not tamper with any of these files; this will cause major trust and cache database issues for the client. Corrupted files will be deleted and replaced if requested.
Static ranges are ~175 MB each or 1/65536th of the site's "active" content. The server will always assume that the client is able to serve files from that range without tracking the files individually. If a ranged file isn't currently cached the client will proxy-request it from the image servers on-demand and store it for later use. The ranged files will stay in the client's cache for 90 days after they were last requested. A client may have up to 5,000 ranges total.
Clients that have started for the first time are assigned 5 ranges. From there up to 48 new ranges can be assigned every day (assuming good performance and available capacity).
Trust indicates how well the client is performing according to other clients. Trust gradually rises by 1-4 per minute 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, calculated by comparing the client's average failure rate with its average hit rate. It prioritizes clients for file requests (along with raw speed and proximity factors).
- Maximum value is 10,000.
- New clients and clients that have been unused for several days will start out with 0 quality and may take several days to stabilize to a baseline value.
- What constitutes a decent quality rating varies between geographical regions.
- Clients that perform below 5,000 will have their static range factor for hath calculation reduced.
The currency known as Hath is also be generated (internally calculated roughly every minute), which can be used to purchase Hath Perks. The minimum speed required to earn hath is 40 KB/s. The amount that can be earned per day per client is based on average hit/minute (calculated over a week) and static ranges.
Any H@H can be used to download archives (instead of via HTTP).
- Resolution options include 780x, 980x, 1280x, 1600x, 2400x, or original (availability may differ).
- Once queued there is no way to prevent the client from downloading the gallery.
- This generates a galleryinfo.txt when completed unlike normal archive downloading.
- These downloads still cost GP/credits (see below for exceptions).
Any client that runs for >24 hours and has a hitrate of 1+ earns a quota of 1 GB/day in free archive downloads. An additional +10 MB/day is earned per adjusted average hit.
- This quota is measured over a 7-day sliding window.
- Recreated archives do not qualify.
- The amount a user has earned can be found in their H@H client list page at the bottom of the "Your Active Clients" section.
- The quota is disabled when a client is suspended or shut down for up to 4 hours, and is re-enabled when a client comes back online.
H@H Image Proxy
This feature only works pre-1.3.0. 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.
|E-Hentai Galleries Navigation|
|Finding||Gallery Searching • Bounty System • Favorites • Making Requests|
|Directory||Anthologies • Artist Recommendations|
|Uploading||Making Galleries • Gallery Categories • Gallery Manager • Gallery Descriptions|
|Downloading||Doggie Bag • Hentai@Home • EHTracker • Gallery Readers|
|User Actions||Tagging||Fetish Listing • Know The Difference • 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||FAQ • My Home • API • Technical Issues • Bans|