srobertson

Another solution: assuming as the article claims that GHash grew to it's current size because it had 0% fees. Other pools can respond by lowering their fees or introduce negative ones. I.e. they pay miners to join the pool. Or have fees but introduce a lottery system that randomly overpays members.

Unless all the automation is owned by a monopoly.

Setting an end of life for Python 2 would be the forcing function needed to ensure Python 3 is reliable and the migration path is clear. Knowing the end is coming would drive us (the community) together to discuss and resolve these issues.

I for one never even considered that C extensions would be a serious road block. Which is obvious now that you mention it. And my main point, I've never bothered to research moving to Python 3 because there's no sense of urgency.

If Guido set a date, say Jan 1st 2015, it would remove allot of the apathy we're currently seeing.

I have problems with the way this is worded as well. I don't think Python 3.x was a mistake. I think the mistake is continuing to develop it in parallel with 2.x with no definitive end of life for 2.x is the mistake.

very cool, probably need a few 100 more lines of code to stop XSS but awesome none the less.

No, nor do they take equity.. They do provide a ton of "goodies". Credits to hosting providers, lawyers etc... And the mentoring is priceless.

Well, sure like Google 2005 they don't have to make sure every idea is a multi-billion dollar enterprise.

The main intent of the search is to retrieve a list of urls that the site crawled for a given subdomain, domain or tld. So for now you can do that using reversed url notation. Which I admit is not very intuitive.

We're toying with the idea of implementing some sort of wild card that way we can present the urls in natural order. Something like *.google.com to retrieve all urls under google. But we wanted to judge the level of interest first. After all "done" is better than "perfect".

good suggestion

I think it's just that the site converts unicode urls for display purposes. If you click on one of the links with "@" in it, you'll see the real url in url encoded format

http://%2E%2E%[email protected]/Ajax/get.comments/oid/4612 176.34.181.212 20120516214328 text/html 912

s3://aws-publicdatasets/common-crawl/projects/url-index/url-index.1356128792

That would be great. Out of curiosity, mind describing what you'd use such a list for?

Let me double check that for you. Were you using a valid aws-id and secret?

Anyone have a cache copy?