You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The cutoff for when quotas can be used on archives is now one year after the gallery was posted (increased from 30 days), matching the cutoff for the H@H downloader.
Extra re-creation costs are no longer applied to archives for galleries posted in the last year (increased from 30 days) or archives downloaded in the last 90 days (increased from 30 days).
The way the image downloading limits work have been reworked, mainly to address various issues caused by an increase in IP address sharing due to increased use of CG-NAT and VPNs.
The old system had two modes, an account-based quota for donators and an IP-based quota for everyone else. This had a few notable quirks, like how if non-donators spent GP to reset the quota, it could be consumed by someone else sharing the same IP address.
The new system has three modes:
Donators and people with the More Pages hathperk have an account-based quota, like what donators had before.
Everyone else defaults to an IP-based quota, similar to before. However;
People who do not have an account-based quota and spend the GP to "reset" it are now assigned a dedicated quota for 24 hours, set with a cookie-based token. Meaning that if you spend GP, the resulting quota can no longer be used by anyone else.
Furthermore, the behavior when you hit the limit has changed:
If you hit the limit while browsing normally, it will no longer error out with a 509 "bandwidth exceeded" screen as long as H@H is enabled. Instead, it will force using the 1280x resampled version even if the image size settings are set higher than this.
If you hit the limit while downloading source images, it will start automatically charging GP for this in the background like before, erroring out if you don't have any. If H@H is disabled, it will also still error out with the 509 "bandwidth exceeded" screen when browsing.
In other words, unless you have the image size setting at "prefer original images" or above 1280x, or H@H is disabled, hitting the limit while browsing will have no effect. Though you could still trigger the DDoS protection if you overdo it.
For IP-based quotas, it will no longer show what the limit is. This is intentional. It will however explicitly tell you on the home screen if your IP is currently restricted from using high-resolution images.
需求 / Requirement
需要适配改版后的配额系统
网站更新日志
2024-08-26
The cutoff for when quotas can be used on archives is now one year after the gallery was posted (increased from 30 days), matching the cutoff for the H@H downloader.
Extra re-creation costs are no longer applied to archives for galleries posted in the last year (increased from 30 days) or archives downloaded in the last 90 days (increased from 30 days).
The way the image downloading limits work have been reworked, mainly to address various issues caused by an increase in IP address sharing due to increased use of CG-NAT and VPNs.
The old system had two modes, an account-based quota for donators and an IP-based quota for everyone else. This had a few notable quirks, like how if non-donators spent GP to reset the quota, it could be consumed by someone else sharing the same IP address.
The new system has three modes:
Donators and people with the More Pages hathperk have an account-based quota, like what donators had before.
Everyone else defaults to an IP-based quota, similar to before. However;
People who do not have an account-based quota and spend the GP to "reset" it are now assigned a dedicated quota for 24 hours, set with a cookie-based token. Meaning that if you spend GP, the resulting quota can no longer be used by anyone else.
Furthermore, the behavior when you hit the limit has changed:
If you hit the limit while browsing normally, it will no longer error out with a 509 "bandwidth exceeded" screen as long as H@H is enabled. Instead, it will force using the 1280x resampled version even if the image size settings are set higher than this.
If you hit the limit while downloading source images, it will start automatically charging GP for this in the background like before, erroring out if you don't have any. If H@H is disabled, it will also still error out with the 509 "bandwidth exceeded" screen when browsing.
In other words, unless you have the image size setting at "prefer original images" or above 1280x, or H@H is disabled, hitting the limit while browsing will have no effect. Though you could still trigger the DDoS protection if you overdo it.
For IP-based quotas, it will no longer show what the limit is. This is intentional. It will however explicitly tell you on the home screen if your IP is currently restricted from using high-resolution images.
原因 / Reason
目前改版后普通用户不再显示配额
建议实现 / Suggested implemention
修改配额展示文本
适配新的配额统计页面
重置配额需要适配新的
解锁配额
按钮处理解锁配额后新增的cookie
下载时处理1280x分辨率是否暂停
备注 / Addition details
No response
自查步骤 / Verify steps
The text was updated successfully, but these errors were encountered: