QUOTE(Tenboro @ Jan 20 2021, 09:07)

Like it said when you signed up, clients are expected to be online more or less 24/7. Yours had a lot of extended downtime and comparatively very little uptime, and was therefore automatically revoked. As such, you will not be able to run H@H in the future.
Oh. Fair enough I guess. I think I had at least a fairly long streak of getting good uptime, before running into issues (had to move a few times, which lead to trouble getting suitable internet, since sorted), and didn't see a mention of there being a chance of fully revoking rights to use in the Wiki.
If these were indeed mentioned in the original signup page, I guess I'd just forgotten. That's fully on me.
Not going to complain much, but I'd hope that the EHWiki's H@H pages get updated to reflect this possibility, so that others don't fall into the same trap. A warning that this is about to happen also wouldn't go amiss. I've looked over the Wiki a few times over the years, and didn't see a mention of this possibility.
Basically I was operating based on these comments:
"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."
-May be run freely for any duration of time, recommended to run it continuously for maximum rewards.
"An H@H client needs to maintain a Trust of 0, Quality of 2500, 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."
-Mentions running idle until the requirements are reached, not revoking the ability to run it.
"Do I have to run the client 24/7?
It is beneficial to have it run for as long as possible. Clients that are frequently offline will perform much worse and get less priority (which in turn leads to even worse performance)."
-Again, no mention of the possibility of getting revoked. Just "beneficial to run for as long as possible".
Based on those I didn't expect that there'd be long term repercussions for not running the client for an extended time, so this did come as a pretty big surprise.