nd
Member of DD Central
Posts: 56
Likes: 37
|
Post by nd on Feb 13, 2017 8:08:37 GMT
Block bots from hoovering up the new loans/renewals and the SM and it will be fairer all round.
|
|
mtb9
Posts: 48
Likes: 35
|
Post by mtb9 on Feb 13, 2017 8:55:48 GMT
Over the past few weeks 3 issues have arose that MT have needed to address primarily because of the popularity of the platform. Firstly address the IT capacity issue (which seems to have been addressed in some way), secondly, set a sensible bid limit (again I believe this was addressed it the Bradford Loan) and now finally the issue of bots which Ed has said he will look into. I think that Ed has shown that where problems are highlighted he will address them, I'm sure Ed will get to the heart of the matter from yesterday and take the relevant action as I'm sure neither he nor any of us want the platform ruined by bots.
|
|
|
Post by sannytwist on Feb 13, 2017 10:08:30 GMT
I agree with this, very impressed with the MT staff in various aspects of this p2p business.
They are not the biggest platform but in my opinion the best by far.
In terms of whats important for me as an investor they are great at communication, work ethic, speed (withdrawals, deposits) , replying to customers and much more.
Keep up the good work.
|
|
elliotn
Member of DD Central
Posts: 3,063
Likes: 2,681
|
Post by elliotn on Feb 13, 2017 10:11:44 GMT
Yes to all of the above and I'll add deal flow, borrower diversity and maintained rates as some of my prerequisites.
|
|
|
Post by GSV3MIaC on Feb 13, 2017 11:13:16 GMT
I'd rather have some bid rate limit (on the SM I'm talking about) like 'no more than one every X seconds' or 'no more than £x per minute' or whatever, than have anything like the SS recaptcha nonsense, which is STILL unfair, but just unfair in a different direction. On the PM I think Ed can / has addressed this with reduced bit maxima, and a second day of limits, which may solve the problem (at least for now). If it doesn't, there is always the prefund option (which is where SS have gotten to) .. so he knows in advance what maximum is closest to the 'right answer'.
Maybe the £25 was too high, but there is probably a 'shrapnel limit' somewhere above the obvious £1, which would generate extra work tracking loan parts and thus clog up some other bit of the system. Personally I'm willing to go down to £10, but parts below that are just annoying. I am sure for some people it is parts below £1k. 8>.
|
|
am
Posts: 1,495
Likes: 601
|
Post by am on Feb 13, 2017 11:51:30 GMT
I'd rather have some bid rate limit (on the SM I'm talking about) like 'no more than one every X seconds' or 'no more than £x per minute' or whatever, than have anything like the SS recaptcha nonsense, which is STILL unfair, but just unfair in a different direction. On the PM I think Ed can / has addressed this with reduced bit maxima, and a second day of limits, which may solve the problem (at least for now). If it doesn't, there is always the prefund option (which is where SS have gotten to) .. so he knows in advance what maximum is closest to the 'right answer'. Maybe the £25 was too high, but there is probably a 'shrapnel limit' somewhere above the obvious £1, which would generate extra work tracking loan parts and thus clog up some other bit of the system. Personally I'm willing to go down to £10, but parts below that are just annoying. I am sure for some people it is parts below £1k. 8>. I don't think anyone wants Google's reCaptcha imposed across the board - but introducing it to the accounts of obvious script users like a***3, g***c ... and alike, what's not to like (for everyone except them)? What's puzzling me slightly is why a bot user is grabbing £25 parts on renewals (and making their activity obvious) - I would expect that anyone who has the time or money to invest in a bot wouldn't care about such a pittance.
|
|
|
Post by sannytwist on Feb 13, 2017 12:12:20 GMT
To compile a script which does something like this isn't hard, anyone that is in a computing science degree course can do it. Anyone without a degree should be able to with a little research. Problem is should we need to? and its explicitly stated that its against the rules to do so.
|
|
mtb9
Posts: 48
Likes: 35
|
Post by mtb9 on Feb 13, 2017 12:28:41 GMT
I think all everyone wants is parity with each other when bidding, if people are using scripts then, in my view, they should not be allowed to bid on any loans if they do not accept the warning and stop using scripts. An unfair advantage isn't parity and I'm sure MT appreciate that.
|
|
|
Post by MoneyThing on Feb 13, 2017 12:54:47 GMT
Afternoon,
I have been discussing this at length this morning with The Shuang and we are going to implement velocity checks and lock-outs on the system.
In summary, the system will monitor in real-time and compare bidding time to the previous one every time a bid is placed.
If a bid is attempted to be placed within 'X' seconds of the previous bid then an error message will pop up with something like 'high velocity bidding blocked'.
Just finishing some other development work at the moment but should have this implemented by the end of this week.
We will also implement a similar system to cater for bids placed at launch of a new loan (i.e. 'Y' seconds after 4pm on the PM), and also time difference between sale & purchase on the SM (i.e. 'Z' seconds between).
Once launched, we may need a little time to optimise what X, Y & Z is set to to get it right but this should solve some of these problems.
Kind regards,
Ed
IN EDIT: We will also maintain a log of the ones that get blocked.
|
|
nd
Member of DD Central
Posts: 56
Likes: 37
|
Post by nd on Feb 13, 2017 13:00:14 GMT
Thanks Ed. Sounds a good solution.
|
|
ali
Member of DD Central
Posts: 313
Likes: 311
|
Post by ali on Feb 13, 2017 13:01:10 GMT
Afternoon, I have been discussing this at length this morning with The Shuang and we are going to implement velocity checks and lock-outs on the system. In summary, the system will monitor in real-time and compare bidding time to the previous one every time a bid is placed. If a bid is attempted to be placed within 'X' seconds of the previous bid then an error message will pop up with something like 'high velocity bidding blocked'. Just finishing some other development work at the moment but should have this implemented by the end of this week. We will also implement a similar system to cater for bids placed at launch of a new loan (i.e. 'Y' seconds after 4pm on the PM), and also time difference between sale & purchase on the SM (i.e. 'Z' seconds between). Once launched, we may need a little time to optimise what X, Y & Z is set to to get it right but this should solve some of these problems. Kind regards, Ed IN EDIT: We will also maintain a log of the ones that get blocked. I can see that X will help, but Y and Z seem just the kind of thing that a bot would excel at getting right and humans will occasionally hit by being too fast. causing some irritation.
|
|
mtb9
Posts: 48
Likes: 35
|
Post by mtb9 on Feb 13, 2017 13:09:15 GMT
Well done Ed for taking such quick steps to try and resolve the issue. Like all other systems the testing of the planned ideas is vital in getting it right for all non-script users and im sure that MT will get it right and eliminate as far as possible those members who use scripts.
|
|
|
Post by MoneyThing on Feb 13, 2017 13:14:56 GMT
Afternoon, I have been discussing this at length this morning with The Shuang and we are going to implement velocity checks and lock-outs on the system. In summary, the system will monitor in real-time and compare bidding time to the previous one every time a bid is placed. If a bid is attempted to be placed within 'X' seconds of the previous bid then an error message will pop up with something like 'high velocity bidding blocked'. Just finishing some other development work at the moment but should have this implemented by the end of this week. We will also implement a similar system to cater for bids placed at launch of a new loan (i.e. 'Y' seconds after 4pm on the PM), and also time difference between sale & purchase on the SM (i.e. 'Z' seconds between). Once launched, we may need a little time to optimise what X, Y & Z is set to to get it right but this should solve some of these problems. Kind regards, Ed IN EDIT: We will also maintain a log of the ones that get blocked. I can see that X will help, but Y and Z seem just the kind of thing that a bot would excel at getting right and humans will occasionally hit by being too fast. causing some irritation. Acknowledged. However, we will look to set the limits to ensure non-bot users are not captured. Of course the bot users can 'learn' what X, Y & Z are and adjust their scripts accordingly, however we will still be maintaining a log to identify those users and manually intervene to block them. We are also seeking legal advice to adjust our Ts&Cs so that we can include penalties for these types of breaches. I would mention that this use of scripts have been identified from a few users who have recently joined. Regards, Ed.
|
|
star dust
Member of DD Central
Posts: 2,998
Likes: 3,531
|
Post by star dust on Feb 13, 2017 13:16:57 GMT
I'm pleased that Ed, Shaung, and MT are taking steps to level the playing field. My concern with this is once someone knows what you are doing to detect them they will write a script to vary their behaviour enough to remain undetected. So whilst it's good to know MT are making an effort to deter people with bots I would suggest varying the mechanism/s and not publicising it too much. In Edit: X posted with MoneyThing
|
|
stub8535
Member of DD Central
personal opinions only. Not qualified to advise on investment products.
Posts: 1,442
Likes: 945
|
Post by stub8535 on Feb 13, 2017 13:17:14 GMT
Afternoon, I have been discussing this at length this morning with The Shuang and we are going to implement velocity checks and lock-outs on the system. In summary, the system will monitor in real-time and compare bidding time to the previous one every time a bid is placed. If a bid is attempted to be placed within 'X' seconds of the previous bid then an error message will pop up with something like 'high velocity bidding blocked'. Just finishing some other development work at the moment but should have this implemented by the end of this week. We will also implement a similar system to cater for bids placed at launch of a new loan (i.e. 'Y' seconds after 4pm on the PM), and also time difference between sale & purchase on the SM (i.e. 'Z' seconds between). Once launched, we may need a little time to optimise what X, Y & Z is set to to get it right but this should solve some of these problems. Kind regards, Ed IN EDIT: We will also maintain a log of the ones that get blocked. Brilliant. Action taken quickly to give fairness to all. I was begining to think it would be worthwhile getting an interface written, ordering a pi and running a program every x ms to get a slice of anything, however cr''p. Maybe you could check monitoring Ed as a way of catching bots b4 bidding? Block ones you identify at the x ms repeat level for 5 minutes after go live time then tell them they were blocked.
|
|