+139

why put the traffic limit ?? it was better as unlimited

anonymous hace 11 años actualizado por ashiq hace 5 años 14
+21

Everything is better when it is unlimited, but our budget cant handle it

+5

yeah everything is better when it is unlimited. im really greatful with 2.5gb file size limit and 100mb recharge per hour for free user..but if you can increase limit and recharges for premium user, it would be really greats :) thanks Boxopus

+4

I think we can, why not

+2
Yah amazing service, very pleased with it, want to upgrade in premium but the max file size and traffic recharge limit is little low for a premium member. If you can think about it i will definitely upgrade to premium. 
+4
Shouldn't the queue be removed for premium?
How long is it anyway?
Hi, I think that unlimited traffic will be best for your service ... It really greatful with 2.5gb file size limit and 100mb recharge per hour for free user..but if you can increase limit and recharges for premium user, it would be really greats and your budgets also will be not affected!!!! Please Exceed your traffic upto 5GB !!! Otherwise your service is best among me and my friends ...!!!!!!
+10
@Boxopus....You have now reduced the limit to 1GB its okay, but atleast increase the torrent file size limit from 512mb to 1GB, we will be grateful to you,
Please increase the file size limit to 1GB,
Regards,
Shreyank
Waited a couple of hours for a 3gb file to stop seeding at 100% file completion.  Sure is kinda slow.

Why? Use your head.
+4
I agree the traffic should be limited. However, I think 1GB is much more reasonable than 512MB. With the 20MB/h recharge rate, it would take more than 50 hours for a full recharge, which is a reasonable lock out for free users.
yeah, file size limit is too small for free user, really miss boxopus beta.
+1
Boxopus rocks! But lots to go before it can compete with zbigz.
I have used boxopus twice so far. The 1gb limit is fair and I am very pleased with the simplicity of it all.

I want to go with your opinion because I have no problem with this.

link