Adio minute pe Hitleap cu VPS

[ZeroDoi]

Azi am primit un email de la ei care ne anunta ca din 25 august nu o sa mai putem folosi vps-uri pentru a castiga minute pe hitleap, asa ca strangeti minute cat mai puteti, la mine deja au inceput sa imi blocheze Ip-urile.

Sincer nu prea ii inteleg, si nu stiu cat de mult au de castigat de pe urma acestei decizii, eu unu am la ei vro 4 conturi premium si la fiecare cont am cumparat extra slot-uri, adica 15euro x 4 conturi = 60 euro lunar care o sa ii piarda de la mine,

This IP belongs to a hosting provider or datacenter.

Starting from August 25, we will no longer allow such IPs to participate in the Traffic Exchange.

This rule will help increase the overall quality of the service.

If you have any questions about this rule, please contact us: Support.

Click

As part of HitLeap's goal to always increase the quality of its service, we are enforcing stricter rules for members participating in the Traffic Exchange system.

Starting from August 25, it will no longer be possible to participate in the Traffic Exchange (by running the HitLeap Viewer) using an IP that belongs to a hosting provider, datacenter, cloud service, etc... If you are running a Traffic Exchange session with such an IP, you will currently see a warning next to the IP. Starting August 25, such sessions will be blocked.

This rule is part of an ongoing effort to increase the visibility of websites promoted through HitLeap and to increase the overall quality of the traffic.

If you have any questions about this rule, please contact us through our Support area.

Edited July 23, 2015 by ZeroDoi

[Byte-ul]

Ce treaba are asta cu securitatea? :\

[ZeroDoi]

scz am vrut sa il postez la Off-topic, sa il mute cineva daca poate.

[Kay97]

Dupa ce ca sunt tigani si au pus limita de 2 sesiuni pe cont ca sa te faca sa bagi bani ampulea, acum mai scot si faza cu vps-urile...

[mrreboot]

Depinde si de calitatea VPS.

Au trimis mail cu niste schimbari, nu blocheaza toate vps-urile.

We received lots of feedback and many questions from our members regarding our decision to block IPs belonging to hosting providers from participating in the Traffic Exchange. Read below for further explanations and about a change we are introducing to the rule.

We are perfectly aware that the change would cause inconvenience to some of our members, so let us further explain why we made the decision in the first place. As mentioned in our previous e-mail, the aim was to improve the overall traffic quality provided by the HitLeap service. How would blocking hosting provider IPs help?

It's quite simple actually. A lot of HitLeap Viewer instances running on hosting provider machines are running in low resource conditions. This prevents the HitLeap Viewer from fully loading all websites, resulting in reduced traffic quality for all members. On the other hand, home users would not be banned as part of the new rule and home computers are usually powerful enough to properly run the application without any problems.

After listening to the feedback and opinions of our members, we realized that this decision would cause unnecessary damage to many honest members - those who run the HitLeap Viewer on reasonably powerful servers or even home users running their internet connection through an IP belonging to hosting providers (e.g. VPNs). We figured we could do better and offer a solution that worked for everyone.

Hosting provider IPs will no longer be blocked. Instead, we are introducing Session Slots. Similar to Website Slots, you need 1 Session Slot for every instance of HitLeap Viewer. Regular members get 2 Session Slots and Premium members get 5 Session Slots. This will cover the large majority of home users. If you wish to start more instances, you can always purchase more Session Slots at very reasonable prices. This, along with much stricter quality controls we will be introducing, will incentivize people to contribute quality traffic to the HitLeap network, removing the need to apply a very broad ban by simply blocking hosting provider IPs.

We believe this change to be the most flexible solution, while still allowing us to improve traffic quality going forward.

For anyone reading this far, here's a small extra bonus for you: a teaser of a Linux version of HitLeap Viewer we have been working on: see here

[kesyda]

Puteti sa folositi Proxychains + ssh tunnel cu ip de om de rand