Were those in District 11 automatically migrated to District 14? Even if you didn’t apply, were you still moved?
不知道，我的也自动迁了
那这免费的用的也太难受了，没啥用了呀， 要排队， 排到了还只能用7天， 之前说1一个月， 这不是单方面该协议吗？ 霸王条款？想改就改？
2 Likes
They kept talking about limited access for so long, but in the end it was pointless. Even after getting a limited device, I still had to queue. After finally getting in, I could only use it for 7 days, and then after 7 days, I had to queue again. So what’s the point of even using it?
How about changing things up a bit? Releasing every 7 days is a hassle, it’s pretty much like a 7-day trial card. 
看看是什么
Take a look
After all that fuss, it turns out it was just to attract traffic. Fine, attract traffic if you want, but once I signed up, it stopped working. After everything, from one month it changed to seven days, and now there’s a waitlist again. The tricks in this city really run deep.
1 Like
You can cancel the service yourself; we’re not forcing you to stay.
Also, if you prefer the resource-grabbing system, you can switch back to the old model, but after careful consideration, we decided not to use it. Below is some feedback from a user who mentioned that the resource-grabbing system could actually lead to wasted resources, which is why we made the switch.
Additionally, most users found that the resource-grabbing system made the control panel open slowly and it was hard to get CPU or bandwidth, so we kept receiving tickets and forum posts. We don’t really need to change anything for the free section, but if we don’t, those who can’t get resources will think that the service isn’t available after activating it. We’re just trying to give everyone a chance to experience it, rather than letting a few users monopolize all the resources.
It’s not that there aren’t enough machines. If we keep using the resource contention model, we could switch back to the previous approach. Below is some feedback from a user, stating that the resource contention model can actually lead to wasted resources, which is why we changed it.
In addition, because the resource contention model makes the panel slow to connect and it’s hard to snag CPU and bandwidth, most users keep submitting tickets and replying to posts. There’s really no need to adjust anything for the free tier, but if we don’t, people who can’t get resources may think they can’t use the service after activation. Our goal is simply to let everyone get a chance to try the service, rather than have just a few users occupy all the resources continuously.
If we still follow the resource competition model, we can revert to the original setup. Below is some user feedback—they pointed out that the resource competition model might actually lead to wasted resources, which is why it was changed to the current approach.
Also, most users report that connecting to the panel is slow due to the competition for resources in this system, and they can’t grab enough CPU or bandwidth, prompting them to keep submitting tickets and posting replies. We actually don’t need to adjust anything for the free tier, but if we don’t, people who can’t get access will think that activating it means they can’t use it at all. We’re just doing our best to let as many people as possible experience it, rather than letting a few users occupy all the resources continuously.
If we stick with the resource competition system, we can switch back to the original model. Below is a user’s feedback—they said the resource competition system might actually lead to wasted resources, which is why it was changed to the current system.
Additionally, because of the resource competition system, most users experience slow panel connections and can’t grab enough CPU or bandwidth. This leads to ongoing support tickets and forum posts. We actually don’t need to change anything for the free area, but if we don’t, users who can’t get resources will feel like it’s unusable after activation. The main goal is just to let everyone have a chance to experience it, instead of letting a handful of users monopolize all the resources.
排队中，
什么状态的排队 是创建排队还是满员排队 目前拓展到同时开150台了 大部分都是直接开了
Please wait for a moment; there are still 50 units whose status hasn’t synced yet. If the status remains the same after synchronization, it means you’ll need to wait for about 7 days.
好的，谢谢
容器有效期从原来的一个月缩减到7天，而且还要排队，排队时长未知，大多数人应该不会专门等着排队，即便排到了可能也懒得折腾了，这样何尝不是另一种资源浪费呢
1 Like
After reading the whole comment section, I find it a bit funny:
- Using a single user’s feedback to counter all the comments now.
- Is it really impossible to run proxy services? How exactly are the proxies being set up? I’m just using pure xray with a manually written yaml, and before disconnecting SSH, I specifically checked that the xray process was running.
- To be honest, I don’t fully understand this so-called resource preemption mechanism. Even if you manage to grab resources, isn’t it still capped at 128MB? Based on the machine specs mentioned earlier, does that mean the seized resources would exceed the original specs?
3.1. If it can exceed the specs, shouldn’t we consider not allowing that? If it can’t exceed them, why can’t everyone’s workloads be supported? Or is it just that there aren’t enough machines?
Most importantly, in the support ticket screenshot you posted, the logic doesn’t make sense to me at all:
- If, as the ticket suggests, there’s resource waste under the resource preemption mode, that means there are idle resources. If that’s the case, why can’t his proxy service run?
- If his proxy service really can’t run, that means he didn’t get the resources. And if he didn’t get the resources, why claim there’s resource waste?
免费区是为了让用户体验，200+台肯定是远远超出母鸡范围的，本身就是不够200+台同时运行的，所以叫做争抢制。
当真跑不了代理服务嘛？您可能是靠前获取的，可以登录后创建，后续用户开启后无法连接到面板也无法获取ssh已经端口转发
资源浪费指有用户一直占用，面板打不开，导致很多用户默默的认为服务无法使用就导致了资源没有给有需要的人，以及浪费在占用机器上