zbanks

"Free for open source" means that they are offering their product for free (eg, without cost) to projects that are open source.

They are not publishing their own source.

If you're running a small, open source project, this seems like an easy way to manage deployments. Kudos to them for a free plan.

This also detects the file encoding & delimiters.

Chartio actually will accept TSV files because it will detect most of these settings. It'll detect the delimiter, the presence of a header line, file encoding, and newline character(s).

I agree TSV is a lot nicer, and has the bonus that Excel will open a TSV file with an .xls extension without any problems (great for sharing!).

Once your CSV (or TSV) files start having quoted fields, they become very tricky to parse using standard multi-purpose tools like sort, awk, & uniq.

It's hard enough when you have delimiters in quoted fields, but dealing with quoted newlines starts to become unreasonable, especially for line-based tools.

CSV files, as you say, are absolutely wonderful to create. Problems come up when you try to parse files other people write. Not everyone follows RFC 4180.

Doesn't the library just have to perform a simple search-and-replace on the entire page's HTML for the blacklisted characters to remove them?

Normally blacklisting is bad, but we're only targeting the few text-direction-changing characters that exist.

This is supposed to be paired with the alternative viewpoint:

Are You Guilty If Pirates Use Your Internet? Lawyer Says YES

http://torrentfreak.com/are-you-guilty-if-pirates-use-your-i...

It seems like a reasonable assumption for a user to know the two-letter abbreviation of the state they live in.

If you suggest otherwise, how do we know that they can spell their street correctly?

I noticed that Google+ allowed something similar when sending bug reports. Do they use a similar method?

The title is a bit misleading at first glance: each company is setting records against previous quarters of the company itself, not compared to every other company in the US.

Honestly, this doesn't seem like big news: each company is undergoing growth and it makes sense that they're spending more on a lot of things: including lobbying.

On paper, universities disallow helping others cheat. In reality, it doesn't seem to be enforced.

If the helper student has already passed the class, the professor can't take disciplinary action against them without making a major case about it. It's easy to simply fail the cheating student or give them a zero on the assignment without making a record.

Additionally, if it is brought to a committee, it'd be much harder to prove.

So although it's officially not allowed, there's not much universities are doing to combat the providers.

His current implementation runs out of memory on a board less than half that size.

Good luck ;-P

Fox News is owned by News Corp.

I had issues with their domain management & DNS settings. Godaddy's was actually better.

This implementation claims to take SUM(argv) ticks, whereas the original sleepsort took MAX(argv) seconds.

Is this an error, or is something done fundamentally different?

There's no active consensus, but a defacto standard emerges.

If I want to talk about Google+, I'm more likely to use a hashtag, such as #googleplus, I've seen before. I could be a rebel and use #gplus, but it makes more sense to use already-established tags.

If we just experimented with hashtags on HN for a day or two, I'm sure they'd be hard to drop. (Although currently, I believe # is not allowed in titles)

They already have this, but it's a bit hidden.

They're replacing the @ with +, which really ties the whole service together quite nicely (while integrating +1's as well).

Your example would use +ProductFoo, for example. If you are writing a G+ post, if you type +, it will prompt for suggestions, much like Facebook does with @.

I'm surprised it's not highlighted by Google, but they do mention it, buried in the help (which is very nicely laid out, if not hidden).

http://www.google.com/support/profiles/bin/static.py?page=gu...

It's still nesting callbacks, just not inline.

Also, for the second example, this might be a cleaner solution:

    var fs = require('fs');

    function writeFile(filename){
      return function(err){
        if (err) throw err;
        console.log('Wrote ' + filename);
      }
    }

    function writeHello(){
      return fs.writeFile('./hello.txt', 'Hello!', writeFile("hello.txt"));
    }

    function writeWorld(){
      return fs.writeFile('./world.txt', 'World!', writeFile("world.txt"));
    }

    writeHello();
    writeWorld();

If you can't create an account after the first invite, get another. Then it will let you in.

I've invited a few people below who haven't confirmed their success :-)

Very nice!

It'd be cool if you could select a bunch of "Me too" options when you first sign up without it reloading the right sidebar. On Chrome at least, it slows down, gets choppy, and makes it hard to click on other options & scroll until its fully loaded.

Once you've made some initial overlaps, you should be fine. Starting off it just is a bit tricky.

Besides this, it's a cool idea. Good luck!

Buzz includes shared items/notes in Reader. You can always export (& import) your subscriptions: http://www.google.com/reader/subscriptions/export?hl=en .

Also, although there isn't any manifest or timeline file, each .html file for Buzz has a last modified date that corresponds to when it was created. In addition, in the file itself, it has a timestamp.

This seems more than reasonable. Sure an XML/JSON timeline might be nice, but it wouldn't be human-readable either.

Your code has a bug on line 2.

@file_get_contents('http://.long2ip(ip2long($argv[1])+$c)

Since $c is the IP address itself, adding the starting IP again will check a completely different IP.

Besides that, you have a point. I feel like the code would be so much cleaner if they just added a 4th line to declare ip2long($argv[1]) as a variable.

Phew, thought it was about Bitcoin.

Although I understand your perspective, and I agree that they have to do something to "make things right," I'm still inclined to accept the rollback.

As much as I hate to use analogies, its the best way I can think to explain my reasoning. If someone (a hacker) robs a bank (user on MtGox), and they throw the money on the ground as they fleeing the scene of the crime, only for it to be picked up by bystanders (profiting users), what do you do?

To me, simply returning the money (rollback) seems to be the simplest effective solution. Maybe I'm being too utilitarian, but it seems too complex to add additional funds into the system, especially when we're talking about nearly 10% of the entire value of BTC. Additionally, it establishes a strange and dangerous precedent: hackers can get away with upsetting the market. And who can make sure the hackers & profiteers aren't working together?

I don't think there's really much you can do to repair faith in the exchange in the immediate future. More importantly, people will keep money as BTC the exchange if it is value is stable (or deflating). Even now, I'd be more worried about the market than hackers.

I'd love to see an insurance company spring up. It'd require major capital, but it'd really help strengthen the value of BTC by providing security and resolving nearly all of these issues. (Things I'd do with $1M...)

Although I can completely understand why this guy (the sumbitter?) disagrees with MtGox's solution, I thought it seemed perfectly reasonable.

Even though MtGox never stated they'd interfere, being hacked is unexpected enough to allow some leeway with follow-up. If the flashcrash happened organically, I doubt MtGox would revert the trades.

Is there a demo available?

The HN link title is more descriptive than the page itself...

There's no reason to publicly describe the attack. Even if you weren't planning on being evil, it would be incredibly easy to abuse.

Its tough separating the wheat from the chaff. Presumably, Silk Road merchants aren't the first to ship drugs: it's pretty tough to detect without slowing everything down.

Not being too familiar with the Tor network, how hard will it be for the government to shut this site down?

I mean, it will have to be problematic if they can't even get an IP, right?

And they obviously can't get Bitcoins directly...

To download it, you (basically) are also sharing the file.

It's as illegal as mirroring wikileaks.

At the same time, this is an incredibly direct source. It's not a long-winded blog post that editorializes.

Hopefully someone here can enlighten us, though.