Author

Topic: You are searching too quickly. Reduce search 90 seconds limit? (Read 255 times)

newbie
Activity: 3
Merit: 0
You need to rank up in order to get things working faster. This is typical restriction no only on searching but also PM and reporting.
see here > https://bitcointalksearch.org/topic/newbies-read-before-posting-1689727

Ok. I will not use the data from bitcointalk then. If really I realize I need those information, I will just scrap the website and use my own local search engine.
Just use Google. They already do that.

Code:
site:bitcointalk.org your query here

It will search stuff only on Bitcointalk.org

Thanks for the tips, but like I said google is not suitable in this case as I need metadata (author and date) related to keywords.

But never mind, I will do that with another tools like https://scrapy.org. Anyway the built-in search was not the best way to do it.
legendary
Activity: 2758
Merit: 6830
Would buying a copper membership work for him?
The Copper Membership has the same limit as he is stating on his post (90 seconds). But he’s only a Newbie so I don’t know what he’s talking about (AFAIK Newbies have much bigger delays). Maybe that’s his alt.
legendary
Activity: 2296
Merit: 2262
BTC or BUST
OP Tell me what you are researching and why and maybe I will help you fix your problem..

Would buying a copper membership work for him?
legendary
Activity: 2758
Merit: 6830
You need to rank up in order to get things working faster. This is typical restriction no only on searching but also PM and reporting.
see here > https://bitcointalksearch.org/topic/newbies-read-before-posting-1689727

Ok. I will not use the data from bitcointalk then. If really I realize I need those information, I will just scrap the website and use my own local search engine.
Just use Google. They already do that.

Code:
site:bitcointalk.org your query here

It will search stuff only on Bitcointalk.org
newbie
Activity: 3
Merit: 0
You need to rank up in order to get things working faster. This is typical restriction no only on searching but also PM and reporting.
see here > https://bitcointalksearch.org/topic/newbies-read-before-posting-1689727

Ok. I will not use the data from bitcointalk then. If really I realize I need those information, I will just scrap the website and use my own local search engine.
hero member
Activity: 1246
Merit: 588
I still remember that days hmm, tho I completely understood that one of the main reason that it was implemented aside from the reason that there was an attack before is that the idea of being a new accounts should be involved more into reading than an interaction.

The logic behind this for me is that since you are still newbie, saying too much  or having the too much functions that you don't actually need is completely nonsense.

Consider yourself as a newborn child when you enter this forum and as a part of growing you will slowly understand features
legendary
Activity: 1288
Merit: 1043
:^)
Hi,

The forum do not let you search faster than one search every 90 seconds. I understand this is to save server resources and there is Google’s search as a fallback.

This is the error message you get:
Quote
You are searching too quickly. Wait 90 seconds. (There is a Google-based search engine on the search page that does not have this limit.)

Yet I wanted to do some research about the volume of post using certain kind of wording. Google is not suitable for that (I need tho be able to copy the date from a table to put it in excel so I can run some stat). You can imagine that having to wait 90 seconds not only for each research (I can live with that) but also to browse the result (going to the next page research also have the 90 seconds limit) is a pain.

It's possible to change this limit to something a bit more acceptable like 5 seconds? The best would be to have a limit that growth with each succeeding research (i.e. 0.5 and then exponentially growth the limit for each research)  and reset every 60 seconds but I understand this is a bit overkill to implement.
its not so much as to save server resources as is to prevent new accounts from being used to ddos the servers, which has happened before. just be happy its only 90 seconds, it used to be 6 minutes between a search / report / post / pm action for newbies not too long ago. im guessing that limit has been changed in the time ive been off the forum.
copper member
Activity: 2114
Merit: 1814
฿itcoin for all, All for ฿itcoin.
Not a good idea at all for lower ranked accounts.
Somethings are better left untouched.

Reducing the limit could lead to abuse and overloading servers and in turn this would make searches to load much longer or even search errors due to servers taking forever to response.
Imagine how much worse and painful that could be.
legendary
Activity: 2240
Merit: 3150
₿uy / $ell ..oeleo ;(
You need to rank up in order to get things working faster. This is typical restriction no only on searching but also PM and reporting.
see here > https://bitcointalksearch.org/topic/newbies-read-before-posting-1689727
newbie
Activity: 3
Merit: 0
Hi,

The forum do not let you search faster than one search every 90 seconds. I understand this is to save server resources and there is Google’s search as a fallback.

This is the error message you get:
Quote
You are searching too quickly. Wait 90 seconds. (There is a Google-based search engine on the search page that does not have this limit.)

Yet I wanted to do some research about the volume of post using certain kind of wording. Google is not suitable for that (I need tho be able to copy the date from a table to put it in excel so I can run some stat). You can imagine that having to wait 90 seconds not only for each research (I can live with that) but also to browse the result (going to the next page research also have the 90 seconds limit) is a pain.

It's possible to change this limit to something a bit more acceptable like 5 seconds? The best would be to have a limit that growth with each succeeding research (i.e. 0.5 and then exponentially growth the limit for each research)  and reset every 60 seconds but I understand this is a bit overkill to implement.
Jump to: