Bitcoin Forum
April 19, 2015, 04:36:51 AM *
News: Latest stable version of Bitcoin Core: 0.10.0 [Torrent]
 
  Home Help Search Donate Login Register  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 ... 84 »
241  Economy / Speculation / Re: No correlation whatsoever with market on: October 16, 2014, 06:10:48 AM
When is BTC coupled with action in FIAT market?!
BTC prices are surprisingly decoupled from almost everything financial. Bitcoin difficulty goes to the moon, price goes nowhere. More retailers accept Bitcoin, price goes nowhere. Stock market goes up or down, Bitcoin goes in different direction.

The big events in Bitcoin price changes seem to involve people trying to get around some government restriction (China, Silk Road) or a big player failing (Mt. Gox).
242  Other / Meta / Re: Forum issue: "bitcointalk.org" rejecting some HTTP requests. on: October 16, 2014, 06:04:14 AM
Update @Newar, it is in Meta. Theymos answered too.

Yes, I see. Even before he posted this topic here, odd  Huh


It didn't answer my observation, but it's back to normal for me.
Right, this belongs in Meta. I had Meta blocked and forgot it existed, so I stuck it under "Technical Support"
243  Other / Meta / Re: Bitcointalk.org HTTP timeout problem on: October 16, 2014, 05:09:35 AM
You're not allowed to access the forum more frequently that once per second on average.

I think that each time you send a request to https://bitcointalk.org/, you also download all of the image/CSS assets. Doing this several times puts you over the burst limit. I see this sort of limit being reached by your IP in the logs.
All it takes is two requests to be blacklisted for a minute or so. This is only true for HTTP requests. You can do HTTPS requests rapidly without penalty, so it's a pointless feature. All you get from an HTTP request for this site is a redirect to the HTTPS URL, anyway. Whatever generates the redirects is doing the useless blacklisting.

"wget" won't download the image and CSS assets at all. It just fetches a file; it doesn't parse it like a browser.

The crawler program is doing this is because it's trying "bitcointalk.org" and "www.bitcointalk.org", both with HTTP and HTTPS requests, to figure out what redirects to what. It doesn't read all of the page; it just opens the URL, reads the HTTP header, and closes. Once it's done that, it reads the home page in its entirety. That fails, because of the strange blacklisting mechanism. None of this reads the CSS or images.

What's doing that? Simple Machines? Some firewall? If this is a generic problem with other sites, I'd like to know about it.
244  Other / Meta / Forum issue: "bitcointalk.org" rejecting some HTTP requests. on: October 15, 2014, 11:33:59 PM
Try doing

wget http://bitcointalk.org

three times in quick succession. The first two will succeed. The third one will stall, wget will retry, and then it will work.

This seems to be some kind of DDOS prevention thing, but failing after two tries is way too soon.  I noticed this because our web crawler at "sitetruth.com" thinks bitcointalk.org is down, or has no web site.

What's doing this?
245  Other / Meta / Bitcointalk.org HTTP timeout problem on: October 15, 2014, 09:53:13 PM
Here's an interesting bug, which may be related to some DDOS-prevention tool on "bitcointalk.org". Our SiteTruth site rating system keeps reporting that "bitcointalk.org" has no web site. This is because, if you make certain HTTP requests more than twice to "bitcointalk.org", the site blocks you for a minute. At the bottom of this post is a Python 2.7 program you can use to demonstrate this. The output of the program looks like this:


>\python27\python timeoutbugtest2.py
Try 0:
MyURLOpener opening request: http://bitcointalk.org [('Accept', '*/*'), ('User-agent', 'SiteTruth.com site rating system')]
 Opened OK.
Try 1:
MyURLOpener opening request: http://bitcointalk.org [('Accept', '*/*'), ('User-agent', 'SiteTruth.com site rating system')]
 Opened OK.
Try 2:
MyURLOpener opening request: http://bitcointalk.org [('Accept', '*/*'), ('User-agent', 'SiteTruth.com site rating system')]
 Open FAILED: ('http://bitcointalk.org', u'HTTP error - timed out.')
Waiting 60 seconds before retry.
Try 3:
MyURLOpener opening request: http://bitcointalk.org [('Accept', '*/*'), ('User-agent', 'SiteTruth.com site rating system')]
 Opened OK.
Try 4:
MyURLOpener opening request: http://bitcointalk.org [('Accept', '*/*'), ('User-agent', 'SiteTruth.com site rating system')]
 Opened OK.
Try 5:
MyURLOpener opening request: http://bitcointalk.org [('Accept', '*/*'), ('User-agent', 'SiteTruth.com site rating system')]
 Open FAILED: ('http://bitcointalk.org', u'HTTP error - timed out.')
Waiting 60 seconds before retry.
Try 6:
MyURLOpener opening request: http://bitcointalk.org [('Accept', '*/*'), ('User-agent', 'SiteTruth.com site rating system')]
 Opened OK.
Try 7:
MyURLOpener opening request: http://bitcointalk.org [('Accept', '*/*'), ('User-agent', 'SiteTruth.com site rating system')]
 Opened OK.
Try 8:
MyURLOpener opening request: http://bitcointalk.org [('Accept', '*/*'), ('User-agent', 'SiteTruth.com site rating system')]
 Open FAILED: ('http://bitcointalk.org', u'HTTP error - timed out.')
Waiting 60 seconds before retry.


This continues indefinitely - two successful opens, then a timeout, wait 1 minute, repeat.

It's not clear what sets this off.  Browsers don't seem to trigger it. Our site rating system does, though. When it starts rating a site, it makes a few requests ("example.com", "www.example.com", an HTTPS request, etc., checking for redirects and trying to find the front door to the site.) That's enough to trigger this.

Anyone associated with the site know what's going on, and what's in the path to the site? This could be some load-balancer or firewall problem.

How do you contact the people behind "bitcointalk", anyway.

The code:

#
#   Test for SiteTruth URL timeout bug.
#
import urlparse
import urllib2
import time
import encodings

kuseragent = "SiteTruth.com site rating system"    # USER-AGENT sent when crawling
kdefaultsockettimeout = 15.0        # allow this much time seconds for socket timeout

#   Class InfoException  --  used for exceptions related to a page or URL
#
#   Usage:   InfoException(url, message)
#
class InfoException(Exception) :
   "Information from external website was not as expected"
   def __init__(self, *args) :            # Initializer
      self.url = args[0]               # save troubled URL
      self.errmsg = unicode(args[1])      # save problem
      Exception.__init__(self,args)      # initialize parent

   def __unicode__(self) :               # convert to string
      msg = u'Problem with page "%s": %s.' % (self.url, self.errmsg)
      return(msg)


def open(purl) :
        try:                                        # catch only "Unicode error" in URL
            headers = { "User-agent" : kuseragent }  # set our user agent
            req = urllib2.Request(purl, None, headers)      # build request
            #    Workaround for Coyote Point load-balancer bug.
            #    If the last field is User-agent, and it ends with "m" but doesn't otherwise contain "m",
            #    a Coyote Point load balancer will drop the packet.  So we add an extra header
            #    that really isn't necessary.
            req.add_header('Accept', '*/*')         # add unnecessary header
            print("MyURLOpener opening request: %s %s" % (purl, repr(req.header_items())))   ## ***TEMP***
            result = urllib2.urlopen(req, None, kdefaultsockettimeout)        # do the open
        except UnicodeError:                        # bad domain name syntax in Unicode format
            raise socket.gaierror("Syntax error in domain name")    # treat as get-address-error error
        except urllib2.HTTPError as message :
            raise InfoException(purl, u'HTTP error - %s.' % (unicode(message.code)))
        except urllib2.URLError as message :
            message = getattr(message,'reason',message)        # use "Reason" if available"
            raise InfoException(purl, 'HTTP error - %s.' % (unicode(message)))
        return(result)                              # return result of open
       
#
#   Main program
#   
def main() :
    retrydelay = 60                                 # wait 60 seconds before retry
    for tries in range(100) :
        print("Try %d:" % (tries,))
        try :
            fd = open("http://bitcointalk.org")                  # URL causing problem
            print(" Opened OK.")
            fd.close()
        except (InfoException,EnvironmentError,) as message:
            print(" Open FAILED: %s " % (message,))
            print("Waiting %d seconds before retry." % (retrydelay,))
            time.sleep(retrydelay)
   
main()
246  Bitcoin / Mining / Re: Miner photo 'porn' on: October 13, 2014, 07:04:04 PM
Oh man... what I would do for those parts...
Ask for them in six months. They'll be worthless then.
247  Economy / Speculation / Re: Poll: Bitcoin price by end of 2014? on: October 13, 2014, 08:12:36 AM
Although I would love for it to be higher, I predict the price on January 1, 2015 will be $350.
That's reasonable. Really, since the China bubble collapsed and Mt. Gox went bust, Bitcoin has been kind of quiet. News of adoption of Bitcoin as a payment method seems to have no effect on price. The cost of mining has no effect on price. There's no particular reason for the price to go anywhere. it's more of a random walk.
248  Bitcoin / Bitcoin Discussion / Re: Blocks are still taking way too long. on: October 12, 2014, 06:31:47 PM
It is applicable if we use a centralized on line wallet.
Then you don't need Bitcoin.
249  Bitcoin / Bitcoin Discussion / Re: Blocks are still taking way too long. on: October 12, 2014, 06:27:07 AM
It would be useful to have a system where blocks were found more often but the reward was smaller. Say, one block every 30 seconds. The original worry was that miners wouldn't find out about the new blocks fast enough, and they'd waste effort building on top of orphaned blocks. But now that all useful mining is centralized, the big guys have enough connectivity to pass around their new blocks fast. As a miner, you want your new block to reach other big miners as fast as possible, and you want to hear about new blocks as fast as possible. So miners will cooperate in passing new blocks around fast, and all the big farms will send directly to each other.
250  Bitcoin / Bitcoin Discussion / Re: Blocks are still taking way too long. on: October 11, 2014, 06:21:33 PM
When we have a offchain payment system for small amounts, block times wouldn't matter.
With an offchain payment system for small amounts, Bitcoin doesn't matter.
251  Bitcoin / Bitcoin Discussion / Re: I have a Bitcoin debit card in my hands... on: October 10, 2014, 07:58:41 PM
The card is issued in Japan, and doesn't have my name on it (it says "TAYTWO POINTMEMBER").

One of these, right?
Quote
The numbers aren't raised. The back is in Japanese. Shift sent a letter with the card explaining these issues, and it's important to understand that it is a BETA PROGRAM. I'm frankly amazed that they've managed to get them out the door so quickly at all. They're working on issuing personalized card with their own design, but didn't want to hold up the Beta program. Awesome Smiley

The card costs money. I've honestly forgotten how much, but I want to say it was around $50. ...
That's not a debit card. It's a prepaid card. Presumably it's been preloaded with some amount of money. Maybe they'll refill it from your Coinbase account if you use it. Maybe not.  Here's the FAQ from the card issuer. There's a site where you can register the card, then read your balance. It may be that the people behind the Bitcoin scheme have already done that, and they're monitoring balances and refilling. Or not.

Incidentally, after one year, you'll be charged 1000 yen for that card.

Quote
Their settlement system leaves much to be desired. I have two transactions pending right now, and my Coinbase account has not yet been touched. The funds are spent from my Bitcoin account when the transaction settles 24-48 hours later. If I wanted, I could buy $500 worth of stuff then empty my Coinbase account, sticking Shift with the difference. It *is* a Beta, but this must be fixed before releasing to the public. If Shift is to survive, they must be able to effectively manage their exposure.
They may not even know when that card is used.

Quote
They ask for permission to spend unlimited funds from my Coinbase account.
What could possibly go wrong?
252  Bitcoin / Mining speculation / Re: Hash rate declining slightly in recent weeks. on: October 09, 2014, 05:36:08 PM
3  blocks to go, and it looks like the next difficulty adjustment will be about +1%.
253  Bitcoin / Mining speculation / Re: Mining no longer viable even at the industrial level on: October 08, 2014, 08:36:06 PM
It's a relatively obvious analysis. Most of the info is from "blockchain.info". There's no sign that the author has any inside information about the operation of big mining farms, or what they're paying for hardware.
254  Bitcoin / Mining speculation / Re: Next difficulty increase? on: October 08, 2014, 05:44:11 PM
We had a drop in the hash rate for about two weeks. That's why it's taking slightly longer to get the required number of blocks. Then the hash rate went way up. No idea why. Maybe one of the big mining farms was doing an equipment upgrade and shut down for the changeout.  The difficulty adjustment tomorrow will probably be 1-2%, much smaller than last time.
255  Bitcoin / Mining speculation / Re: Hash rate declining slightly in recent weeks. on: October 07, 2014, 09:35:23 PM
There was a drop that lasted for several weeks. That's not just noise from the rate at which blocks are found.

It's possible that some big hashing center was doing an upgrade, and they were shut down during the upgrade.
256  Economy / Speculation / Re: What will bring BTC price back up? on: October 07, 2014, 07:42:58 PM
Such as Chinese gov cancels the restriction to financial institutions dealing with Bitcoin.
There's discussion in China of reducing exchange controls on yuan. But if China reduces exchange controls, people with yuan in China won't need Bitcoin. The China bubble was because, for a brief period, Bitcoin was a safe, legal, remote way to convert yuan into dollars or euros. The previous legal approach was to get all your relatives to travel to Hong Kong every three months, loaded up with the legal maximum of yuan notes. This is a pain if you're not in Shenzhen.

If you have no idea what the above is about, you probably were screwed by the collapse of Bitcoin prices.
257  Bitcoin / Bitcoin Discussion / Re: A future of high transaction fees? on: October 07, 2014, 06:48:59 AM
If Bitcoin ever gets enough usage that the 7 TPS transaction rate is reached, fees will probably go up.  Miners have no incentive to adopt a larger block size, and every incentive to raise fees if they can.
258  Bitcoin / Mining speculation / Re: Hash rate declining slightly in recent weeks. on: October 07, 2014, 06:43:10 AM
Oh for god's sake, quit spamming you betting site.
Agreed.
259  Economy / Speculation / Re: For sale on Bitstamp: 13780 BTC at $300. on: October 06, 2014, 06:35:09 AM
How big was the dump six hours ago?
260  Economy / Speculation / For sale on Bitstamp: 13780 BTC at $300. on: October 06, 2014, 06:32:55 AM
Right now, there is a huge dump of 13780 bitcoins on Bitstamp, offered at $300. That's the current price.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 ... 84 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!