Quote:
Originally Posted by Brokenstars
What about things that are in your browser like what I linked earlier in the thread?
Well itÂ’s actually a lot more simple than that, those generally run Java or have embedded apis that connect to name.server that send and receive requests. ItÂ’s very easy for acr to blacklist these sites so if you receive those requests youÂ’ll be subject to a review.
For example,
The pure gto alpha bot or whatever itÂ’s called uses a server file on your desktop that opens a TeamViewer type port. This port is a TCP port, this port has to be also open on your router and whitelisted.
ACR needs to scan a routers open ports (like poker stars) , they they need to have in their terms and conditions that they are allowed to pen test any open ports to look for screen sharing(quite easy to identify).
Say port 7111 is open on the router, port 7111 has incoming and outgoing packets and is steady state. Say users ip is 192.167.1.1 but their IP that is known to the poker site is 10.1.3.2 , the poker site can simply open up TCP. Viewer
Type
Ip :10.1.3.2
Port 7111
This will very likely bring up a remote version of a screen which is very likely being read by another pc.
How to fix these problems from a player point of view.
Start min bet donking OOP when you have a hand that needs to check call or check raise. This will be interpreted from the RTA point of view as a donk bet and will screw up their game tree.
How to fix these problems from an operators point of view.
Have a bomb pot type randomizser where a player from IP or OOP will min donk at a point in the hand, this literally stops both players from using a screen based RTA.
The most insane thing about this is that the rta companies that sell these rta bot programs are actually contracted to various poker sites and have had deals with them for the past 4 years.
You use an rta, you donÂ’t know it but your cards are being shared with not only a bunch of Russians but also poker sites themselvesÂ….