Regarding how the Hong Kong free zone should operate, there are currently two different opinions. Some feel that the queue-and-rotation system is too cumbersome and want to return to the previous resource-grabbing system; others believe that the queue-and-rotation system at least guarantees availability at some point and support the current model.
Current status:
The simultaneous online container limit has been increased from 100 to 150, easing the pressure on the queue somewhat.
The two options are as follows:
Option 1: Restore the resource-grabbing system (original model)
No limit on simultaneous online users; first come, first served, with users competing for resources;
Those who manage to claim resources can use them, while those who do not may have to wait and may be unable to use the service;
No 7-day release limit and no queue;
Some users may occupy resources for a long time, causing later users to experience lag or possibly be unable to connect.
Option 2: Keep the queue-and-rotation system (new model)
A limit of 150 simultaneous online containers; those exceeding the limit must wait in the queue (the first 100 are currently being created, and the additional 50 are expected to be fully created before 11:00 on the 16th);
Each instance can run for a maximum of 7 days, after which it is released to make room for the next user;
Queued users are automatically assigned available slots, ensuring fair rotation;
Everyone gets a turn, but must accept the queue and 7-day release rules (or an adjusted duration).
Which option do you support (1 or 2/3)? The final decision will follow the wishes of the majority, with the minority respecting the majority (if the difference is small, we will not switch, as changing it is too much trouble).
This poll is open until August 18. After it closes, we will implement the result and will not make any further adjustments.
Final Survey on the Operating Model for the Hong Kong Free Zone (Choose One of Three)
Restore the resource-grabbing system (original model)
Keep the queue-and-rotation system, rotating every 7 days (new model)
Keep the queue-and-rotation system, but change the rotation period to 1 day, 14 days, or another duration; you may reply to the post to discuss it (expanded option for the new model)
This kind of monitoring is too much trouble; it’s impossible to keep checking all the time. If just one of many machines is busy, the whole system is marked as highly occupied, and you can’t pinpoint which one is the problem.
Has anyone actually shared whether the old resource competition method is still useful…? Even the container panel itself can’t stay up — what are the machines that manage to grab resources actually running…?
To take it to the extreme: with the competition method, one of the few things these small machines are actually good for is running scripts to scan other machines. They don’t even need to be continuously available; as long as a process stays alive and scans intermittently, that’s fine. If there are such cases, eventually the root node is going to get abused.
Also, since the machines are free, the platform can make its own decisions. Once a decision is made on a certain solution, at least try it for a while to see if it works, unless it really proves unworkable.
Leaving it up to user votes isn’t a long-term solution. If you bring back the competition method, you’ll probably get a flood of feedback in a few days saying it’s unusable, and the objections to the 7-day queue will probably disappear again.
It still works; making this change is similar to how you might not be able to access the panel after your subscription expires, but if you save your SSH info, you can still use it.
I’m considering what this user said, but if I do that, there will be even more opposition.
Objectively speaking, limiting the number of devices is the best solution. Whether you agree or not, this thing is free to begin with…
I’ve honestly never seen a business model where users have to fight each other for computing resources, and the platform can’t even track what exactly a VPS is using. The only way to deal with downtime is to reset the host. Isn’t this basically inviting people to mess things up?
We won’t be handling issues in the free zone anymore. Dealing with some of them still leads to other problems, so we’ll just go with the flow and let things be—this is the new policy. Yeah, we’re not changing it.
