Hentai@Home - Revision history

Kagoraphobia at 08:25, 6 August 2026

2026-08-06T08:25:31Z

← Older revision		Revision as of 08:25, 6 August 2026
Line 51:		Line 51:
	\|Sufficient uptime		\|Sufficient uptime
	\|		\|
	*A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations\|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.		*A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations\|revoked]].
			*If a client remains offline for more than three months, it will be deleted and cannot be recovered.
	\|-		\|-
	\|Located in compatible countries		\|Located in compatible countries
Line 212:		Line 213:

	==[[Rewards]]==		==[[Rewards]]==
	Users receive 1 [[GP]] for each hit on their client ~~and~~ may compete for a position on the [[Toplists#Hentai.40Home_Toplists\|H@H toplist]]. While running [[Hentai@Home#healthy\|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].		Users receive ~1 [[GP]] for each hit on their client, adjusted for the average served file size. They may also compete for a position on the [[Toplists#Hentai.40Home_Toplists\|H@H toplist]]. While running [[Hentai@Home#healthy\|healthy]] H@H clients, users receive [[Hath]] which can be used to purchase [[Hath Perks]].

	The daily [[Hath]] earned per client is based on the following formula:		The daily [[Hath]] earned per client is based on the following formula:

Kagoraphobia: /* Obtaining Client Keys */

2026-08-06T06:04:32Z

Obtaining Client Keys

← Older revision		Revision as of 06:04, 6 August 2026
Line 63:		Line 63:
	Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.		Users wishing to sign up for their first client can apply from the [https://e-hentai.org/hentaiathome.php Hentai@Home page] in their [[My Home]] area. Applications are typically processed in less than a day.

	For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.		For any additional clients you will need to [https://forums.e-hentai.org/index.php?act=Msg&CODE=4&MID=6 PM Tenboro]. Ensure that your PM includes the following information:
			*Maximum bandwidth that will be reserved for H@H. This will be limited by your '''outgoing''' bandwidth, not the rate you can download at.
			*Disk space that will be reserved for the image cache.

			For users wishing to run more than 5 clients the average stable quality of their existing clients must be 7,000+ before more keys are assigned.

	<div id="Installation"></div>		<div id="Installation"></div>

Kagoraphobia: /* Static Ranges */

2026-08-06T05:48:47Z

Static Ranges

← Older revision		Revision as of 05:48, 6 August 2026
Line 170:		Line 170:

	Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust\|trust]], [[quality]], current/previous session runtime, or tested speed requirements.		Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust\|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

			[[Image:Point.png]] <span style="color:#ff0000">'''DO NOT reset static ranges unless your cache has been lost. Regular resets will result in the [[Hentai@Home#Revocations\|revocation]] of your client.'''</span> It should '''ONLY''' and '''ALWAYS''' be reset if the cache has been deleted or is otherwise lost, or else the client will encounter serious [[Hentai@Home#Trust\|trust]] issue.

	====Priority Levels====		====Priority Levels====

Kagoraphobia: /* Minimum Requirements For New Clients */

2026-08-05T20:53:50Z

Minimum Requirements For New Clients

← Older revision		Revision as of 20:53, 5 August 2026
Line 56:		Line 56:
	\|		\|
	*Running H@H may not be possible or easily achievable in countries that block E-Hentai.		*Running H@H may not be possible or easily achievable in countries that block E-Hentai.
			*Applications for H@H clients in Europe are currently closed due to excess capacity. Users who are currently running H@H or [[donators]] may still apply for new clients in the region.
	*It is not possible to run H@H in the United Kingdom, the Russian Federation, or any country in Africa due to undesirable network conditions.		*It is not possible to run H@H in the United Kingdom, the Russian Federation, or any country in Africa due to undesirable network conditions.
	\|}		\|}

Kagoraphobia at 09:06, 5 August 2026

2026-08-05T09:06:28Z

← Older revision		Revision as of 09:06, 5 August 2026
Line 56:		Line 56:
	\|		\|
	*Running H@H may not be possible or easily achievable in countries that block E-Hentai.		*Running H@H may not be possible or easily achievable in countries that block E-Hentai.
	*~~Due to deteriorating network conditions, it~~ is not possible to run H@H in the Russian Federation.		*It is not possible to run H@H in the United Kingdom, the Russian Federation, or any country in Africa due to undesirable network conditions.
	\|}		\|}

Line 93:		Line 93:
	Clients eligible for [[Hentai@Home#High-Capacity_Ranges\|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.		Clients eligible for [[Hentai@Home#High-Capacity_Ranges\|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

	When reduced below the committed threshold, active ranges are removed in order of P3 > P2 > HC > P1. '''P4 ranges will be completely removed if there is any reduction in the cache size.'''		When reduced below the committed threshold, active ranges are removed in order of P3 > P2 > HC > P1. '''When allowed, P4 ranges will be completely removed if there is any reduction in the cache size.'''

	If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per active static range will be reduced to 256 MiB.		If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per active static range will be reduced to 256 MiB.

Kagoraphobia: /* Minimum Requirements For New Clients */

2026-08-05T08:06:25Z

Minimum Requirements For New Clients

← Older revision		Revision as of 08:06, 5 August 2026
Line 29:		Line 29:
	\|-		\|-
	\|500 GB/month data transfer		\|500 GB/month data transfer
	\|Users may limit how much data is used per month. Note that this limit is approximate.		\|
			*Users may limit how much data is used per month. Note that this limit is approximate.
	\|-		\|-
	\|10+ GiB of '''dedicated''' hard drive space		\|10+ GiB of '''dedicated''' hard drive space
Line 45:		Line 46:
	\|-		\|-
	\|A unique IPv4 IP address		\|A unique IPv4 IP address
	\|1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).		\|
			*1 per every operational client. Ideally should be static, or needs to be relatively stable (i.e. not change constantly).
	\|-		\|-
	\|~~Uptime~~		\|Sufficient uptime
	\|A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations\|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.		\|
			*A single client should remain online for at least 90% of the time over a 6 month period. Clients that have an unacceptable level of downtime will be [[Hentai@Home#Revocations\|revoked]]. If a client remains offline for more than three months, it will be deleted and cannot be recovered.
			\|-
			\|Located in compatible countries
			\|
			*Running H@H may not be possible or easily achievable in countries that block E-Hentai.
			*Due to deteriorating network conditions, it is not possible to run H@H in the Russian Federation.
	\|}		\|}

Kagoraphobia: /* Revocations */

2026-08-05T07:47:50Z

Revocations

← Older revision		Revision as of 07:47, 5 August 2026
Line 227:		Line 227:

	==Revocations==		==Revocations==
	Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked. Revoked clients can no longer be used and will be deleted after the three month grace period.		[[Image:Point.png]] <span style="color:#ff0000">'''Clients that fail to adhere to the uptime requirements by a significant margin or have their cache/ranges regularly cleared will be revoked.'''</span> Revoked clients can no longer be used and will be deleted after the three month grace period.

	Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.		Depending on what led to the revocation, revoked clients can sometimes be reactivated. You would need a very good reason for this to happen, and this will be decided on a case by case basis. "I did not read the requirements on the signup page nor the multiple automated warnings I received" is not a good reason.

Kagoraphobia: /* Limits */

2026-08-05T07:42:52Z

Limits

← Older revision		Revision as of 07:42, 5 August 2026
Line 76:		Line 76:
	<pre<includeonly></includeonly> style="overflow: auto;{{{style\|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>		<pre<includeonly></includeonly> style="overflow: auto;{{{style\|}}}">'''Maximum connections (capped at 500)''' = 20 + max_burst_speed / 10000</pre>

	The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#~~Static_Ranges~~\|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.		The disk cache size (in GiB) must be enough to maintain active static ranges. [[Hentai@Home#Priority_Levels\|P4 (Priority 4) ranges]] are inactive and thus not counted towards this requirement.

	Clients in the primary regions (i.e., Asia, Europe, North America~~, and~~ mainland China) must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:		Clients in the primary regions (i.e., Asia, Europe, and North America) or mainland China must be able to store 10 GiB or 512 MiB per static range at any given time, whichever is higher:
	<pre<includeonly></includeonly> style="overflow: auto;{{{style\|}}}">'''~~Minimum~~ cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>		<pre<includeonly></includeonly> style="overflow: auto;{{{style\|}}}">'''Committed cache size''' = max(10, (active_static_ranges * 512 + HC_ranges * 1024) / 1024)</pre>

	Reducing cache size below the ~~minimum requirement~~, as calculated by the formula above, will result in the demotion/loss of static ranges. Clients ~~are not permitted to~~ reduce their cache size below 10 GiB.		<span style="color:#ff0000">'''Reducing cache size below the commitment, as calculated by the formula above, will result in the demotion/loss of static ranges.'''</span> Clients cannot reduce their cache size below 10 GiB.

	Clients eligible for [[Hentai@Home#High-Capacity_Ranges\|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.		Clients eligible for [[Hentai@Home#High-Capacity_Ranges\|High-Capacity (HC) ranges]] should take them into account when calculating the minimum cache size needed to avoid static range removal.

	If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per static range will be reduced to 256 MiB.		When reduced below the committed threshold, active ranges are removed in order of P3 > P2 > HC > P1. '''P4 ranges will be completely removed if there is any reduction in the cache size.'''

			If the client is located within the secondary regions (i.e., Oceania and South America), the required cache size per active static range will be reduced to 256 MiB.

	===Speed Test===		===Speed Test===

Kagoraphobia: /* Cache */

2026-08-05T07:25:59Z

Cache

← Older revision		Revision as of 07:25, 5 August 2026
Line 158:		Line 158:
	The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.		The assignment of static ranges for a particular region is based on a scoring algorithm. It generally prioritizes new clients or clients with few ranges, assuming all other factors (e.g., tested speed) are similar across clients. If a static range has only been assigned to less than the desired number of clients or a below-average number of clients, the range in question will be assigned to an available client.

	Static ranges are divided into priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.		Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust\|trust]], [[quality]], current/previous session runtime, or tested speed requirements.

			====Priority Levels====
			Static ranges are divided into four priority levels, where P1, P2 and P3 are considered "active" ranges. The network will first attempt to request a file from a P1 client, and then fall back to clients with a lower priority if the initial client(s) fail to serve the file.

	The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.		The final priority level P4 is for "dead" ranges that previously active ranges can be demoted to, for example, if the client is offline for an extended period of time. P4 ranges do not generate any traffic and are only used for a promotion bonus for ranges recently demoted to P4. They will eventually be unassigned from a client.

	To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.		To receive the most P1 ranges, the client should maintain a high tested speed and [[quality]] value, and have as high uptime as possible. Clients that experienced recent overloads will be less likely to be assigned with P1 ranges.

	~~Clients cannot be assigned more ranges if they fail the minimum [[Hentai@Home#Trust\|trust]], [[quality]], current/previous session runtime, or tested speed requirements.~~

	====High-Capacity Ranges====		====High-Capacity Ranges====

Kagoraphobia: /* Minimum Requirements For New Clients */

2026-08-05T01:06:43Z

Minimum Requirements For New Clients

← Older revision		Revision as of 01:06, 5 August 2026
Line 34:		Line 34:
	\|		\|
	*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.		*SSDs are ideal; <span title="Disabling logging can reduce I/O even further" style="border-bottom:1px dotted">write endurance is not an issue</span>.
			*Clients running on HDDs should allow at least 10% free space for proper file defragmentation.
	*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.		*At least 1 GiB for every <span title="25 KB/s " style="border-bottom:1px dotted">0.2 Mbit/s</span> is encouraged for optimal [[static range]] allocation.
	*Please ensure the client can sustain both speed and disk I/O in the long run.		*Please ensure the client can sustain both speed and disk I/O in the long run.