|
Post by sunspot on Jan 11, 2016 2:37:23 GMT
I just took a look at the CloudFlare website. People may find the following quote interesting...
Thus, as I suspected, they are almost certainly responsible for blocking certain users who've been refreshing pages excessively.
Interestingly though, with a statement as clear as that, Saver Stream should perhaps refer the problem of bots to them, as they may already have a simple solution they can put in place, and if not, they might be willing to investigate. That said, I still believe that well-written bots would be very difficult to identify, but I suspect that some of the current generation are quite primitive, and use none of the "real-user" fakery I would build in. Therefore, any such action would be no more than a temporary patch.
|
|
|
Post by GSV3MIaC on Jan 11, 2016 7:07:17 GMT
D**E is Buddy, and we don't do "testing". Excess purchases, if any, will be flushed during normal working hours .. I.E. after 8am. I still propose an AC style allocation algorithm (although I clearly don't need it myself) ... All in favour? Or shall we continue bot wars?
|
|
james
Posts: 2,205
Likes: 955
|
Post by james on Jan 11, 2016 7:08:50 GMT
Well, the bans MUST be based on IP address. If they were account-based, users would still be able to see the site, but not log in. And if they were based on cookies, simple deletion would suffice. ... it seems that a company called CloudFlare provides the necessary hosting - they are most likely responsible for bans, not Saving Stream. A site isn't one thing, it has many component parts. Blocking of transaction-related information can be done at account level even while other content is being served by a caching service like CloudFlare. If transaction-related details like amount available are currently displayed without login there's no requirement for it to remain that way if that is what it takes to prevent issues. CloudFlare is perhaps the best known of the services that is marketed for preventing disruption from large-scale denial of service attacks. It's also useful for dealing with transient bursts of normal high traffic. You'll find it sitting in front of lots of government or other politically exposed sites that could be subject to DoS. Blocking is not normally done at only one place or level in the connection hierarchy. At a global top 100 site I did it at anything from IP address to account level and also sometimes based on content. That sometimes included things like modifying the site software to help. I just took a look at the CloudFlare website. People may find the following quote interesting... It's all old news to people who've done this sort of thing. Interestingly though, with a statement as clear as that, Saver Stream should perhaps refer the problem of bots to them, as they may already have a simple solution they can put in place, and if not, they might be willing to investigate. That said, I still believe that well-written bots would be very difficult to identify, but I suspect that some of the current generation are quite primitive, and use none of the "real-user" fakery I would build in. Therefore, any such action would be no more than a temporary patch. This stuff is easy, not hard. Your thoughts on how to circumvent blocking are completely ineffective against well designed blocks in an environment of strong identity checking for account creation. To block relies on nothing more than knowing what a bot is trying to do, which is react faster than humans, so the bot has to make more requests for the key information than a human can credibly make. So you can block bots effective by capping, rate limiting, short term banning, prohibiting purchase of more investments and on through complete account closure if the activity continues after repeated instructions to cease. Tougher cases would involve coordinated teams using multiple accounts to synthesize high rates overall with lower per-account rates. The key issues aren't the technical ones of how to do it but the decision that something should be done, followed by the decision on whether to try to do queues or other allocations systems as well as or instead of bot blocking.
|
|
adrianc
Member of DD Central
Posts: 10,003
Likes: 5,139
Member is Online
|
Post by adrianc on Jan 11, 2016 8:26:16 GMT
Well, the bans MUST be based on IP address. If they were account-based, users would still be able to see the site, but not log in. Unless, of course, the user could log in - but couldn't buy... Bit pointless, since cookies only exist within a browser - and even then can be automatically binned once the session closes - and bots are very likely to run outside the browser anyway.
|
|
adrianc
Member of DD Central
Posts: 10,003
Likes: 5,139
Member is Online
|
Post by adrianc on Jan 11, 2016 8:26:57 GMT
I still propose <actually kinda irrelevant> ... All in favour? Or shall we continue bot wars? That looks a heck of a lot like blackmail from here...
|
|
|
Post by GSV3MIaC on Jan 11, 2016 8:55:35 GMT
Nope, I'm quite happy with the status quo, so no pressure from me to change, but I'd have preferred we didn't need to do this in the first place (as I said here a week or so ago; and over on FC about 2 years ago ... but if bots are the competition, I am sure willing to compete rather than get rolled over).
|
|
|
Post by highlandtiger on Jan 11, 2016 9:05:39 GMT
D**E is Buddy, and we don't do "testing". Excess purchases, if any, will be flushed during normal working hours .. I.E. after 8am. I still propose an AC style allocation algorithm (although I clearly don't need it myself) ... All in favour? Or shall we continue bot wars? You seem to be obsessed with creating either a premium cost for secondary market sales, (well I'll think you'll find you are in a minority of one, for that daft idea), or an allocation system, (again, you won't convince many others on that one either) The answer is simple, as most answers are. All SS have to do, is place a simple sentence within their terms and conditions banning the use of automated software on their website. Anyone using such software will have their account closed and all monies returned to them and their loan parts placed back on the SM. This would immediately stop 99% of all bots, as most people would not like to take the risk of getting caught and being banned from using SS. Currently, SS is the golden goose, which those who are intent on using bots, are slowly killing off. If people struggle to purchase loan parts, or the ability to build up a decent diversified portfolio, they will go elsewhere. It seems that those people who are apparently intelligent enough to create a bot, don't have a similar dose of common sense when it comes to the looking at the results of their actions.
|
|
|
Post by Deleted on Jan 11, 2016 9:20:23 GMT
lots of secondary markets and primary markets out there without bots or with minimal bot affects. As a result I'm just focused elsewhere for my investments.
However there are a few other things coming that will possibly cause a perfect storm
Growth of Institutions in the market Growth of SIPP and ISA driven retail investing via Institutional mechanisms Rise of the Bots, used both at retail and at Institutional level
My own view is the market will be very different in 12 months time, so now is when we as punters/lenders have to make our plans and now each P2P portal has to make its position on each of these clear.
Silence is no longer an acceptable response.
|
|
|
Post by GSV3MIaC on Jan 11, 2016 9:28:49 GMT
Yep, I voted for 'banning' too if you recall .. not that that is awfully easy to legislate for, or police .. I also pointed out that the problem is lack of supply .. bots or no bots, if there isn't anything to buy then people can't get invested in any reasonable time. Bots are a symptom, not the cause.
The premium/discount point is to allow the market to get balanced, when needed - an alternative suggestion is welcome, since 'ban bots' won't improve the SM supply at all (so far today I have seen less than £1k offered in total). There's not going to be a huge glut when the next loan goes live either, assuming it's the small one currently at state2. We currently have a huge imbalance between would-be lenders and borrowers, or sellers of existing holdings.
|
|
awk
Posts: 276
Likes: 147
|
Post by awk on Jan 11, 2016 9:36:02 GMT
If you think the bots are bad now when all they can do Hoover up to their funding limit ....
.... then what do you think the world of discounts/premiums would be like if there was trading profits to be made?
Hoover @12% and sell at @10%, 9%, 8% to mere manual buyers?
I agree that something needs doing throttles/limit ?? But not discounts/premiums
|
|
|
Post by jackpease on Jan 11, 2016 9:39:24 GMT
agree and disagree! >>>>The answer is simple, as most answers are. All SS have to do, is place a simple sentence within their terms and conditions banning the use of automated software on their website. Anyone using such software will have their account closed and all monies returned to them and their loan parts placed back on the SM. This would immediately stop 99% of all bots, as most people would not like to take the risk of getting caught and being banned from using SS. Yes! Such a clear signal would put a stop to systematic bots - and any institutional bots that come in future months..... >>>It seems that those people who are apparently intelligent enough to create a bot, don't have a similar dose of common sense when it comes to the looking at the results of their actions. [/quote] But here i disagree - i think it is an entirely rational response - and indeed common sense - to work within the (flawed) rules. I don't have the wherewithal to use bots myself and i'd consider it immoral to be the first to use bots but once it's clear that there's widespread use of bots then it's unsurprising people are embracing the flawed system. Jack P
|
|
|
Post by sunspot on Jan 11, 2016 9:46:02 GMT
James Perhaps you should engage brain before posting...
I was not SUGGESTING how bans might be implemented, I was EXPLAINING how and why I do not believe Saver Stream has itself already implemented bans as some people have suggested.
I guess that's the difference between someone like me who's looking to dispel falsehoods, and someone like you who merely seeks to impress, and therefore looks for posts with which they can disagree.
If you wish to contribute to discussions, I suggest you factor in the following possibility before typing: not everyone is stupid. Follow this rule, and you should in future avoid picking pointless arguments, for they are just that, POINTLESS.
|
|
james
Posts: 2,205
Likes: 955
|
Post by james on Jan 11, 2016 10:30:15 GMT
I was not SUGGESTING how bans might be implemented, I was EXPLAINING how and why I do not believe Saver Stream has itself already implemented bans as some people have suggested. Well, the bans MUST be based on IP address. If they were account-based, users would still be able to see the site, but not log in. And if they were based on cookies, simple deletion would suffice. You were making incorrect claims about blocks and I addressed the inaccuracies in your claims based on my experience of actually doing it. I guess that's the difference between someone like me who's looking to dispel falsehood I believe that you were looking to dispel falsehood. I also believe that you were trying to explain why you thought that SavingStream hadn't done it already. But the fact is, you did not dispel falsehoods, you perpetuated them with your claims that blocks MUST be based on IP address and that account-based blocking couldn't be used, even though I believe your assertions about your intent. Sometimes intent isn't matched by results even when the attempt was done with good intent. Nothing wrong with trying.
|
|
jonno
Member of DD Central
nil satis nisi optimum
Posts: 2,806
Likes: 3,237
|
Post by jonno on Jan 11, 2016 11:10:13 GMT
Received a nice email from Tim at SS this morning regarding the use of bots. They are aware of the issue and it is on the list of tasks for their IT gurus to deal with. We wait to see what develops. Wouldn't it have been a great idea if savingstream would have posted something of that ilk here which ,if nothing else, may have curtailed this interminably boring thread for at least a while.
|
|
|
Post by sunspot on Jan 11, 2016 11:40:45 GMT
James Good grief. I did NOT say that blocking MUST be based on IP address. It's blindingly obvious, for instance, that accounts can be frozen out, etc.
Instead, I merely explained what had ALREADY happened - or tried to anyway. Specifically, Saver Stream was being blamed for bans which I believed to automated, and not even part of their software.
If you believe that explanation is WRONG, let's hear your explanation of why people where unable to access the Saver Stream website after using extensions to auto-refresh the available loans page.
Picking STUPID arguments adds nothing to the discussion, except perhaps in your mind (for obvious reasons).
|
|