Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

Everyone in this thread seems to assume that people will have to front the cash. Wouldn't it be more likely that they'd get a loan?

But yeah, $100k does seem a bit steep. That's almost the price of a college education, and a substantial fraction of the price of a good house. And in this economy, a lot of people are already having trouble paying both of those off; adding $100k on top of that for immigration would put this out of the reach of many people that I think that we do want to encourage to move here.

As a natural born citizen of the US who has many foreign friends, I am appalled at what they have to go through to get citizenship here. Some of them have managed to pull it off; some have given up and moved back home, or to other countries in which it's easier to get a work visa. And these are Ivy-league educated folks with masters degrees and PhDs in business and technical fields. I cannot believe that we are making it so difficult for such people to come to the US.


(From experience:) You need to show where all money came from that you use towards meeting immigration requirements. For most uses you can't use the proceeds of a loan to count towards it.

$100k's pretty cheap for a professional - there's enough of a salary differential between the US and most other places in the world (especially once factoring taxes in - eg. pay is high in Switzerland but so are taxes) that it would not take more than a few years to make back the $100k.

Agree that it's shocking how difficult it is for smart, educated individuals to immigrate at a time when the country needs to be attracting global talent to maintain it's lead.


> Wouldn't it be more likely that they'd get a loan?

I'd love to see the terms on this kind of loan: people coming to US from the abroad do not have any credit history whatsoever. Now, if this will be some government-sponsored loan, I could only imagine the amount of bureaucracy involved and timelines for that.

If one were to look for better way for immigration problem resolution - Canada and Australia have decent processes of getting people they need in.


So, you would trust something named 'googleserver.com' but not something named '1e100.net'? What if someone malicious registered 'googleserver.com'? There's nothing stopping them from registering that or any number of other names that sound legitimate. If you really want to be sure you can trust it, you need to check further anyhow.

And 1e100.net is a lot shorter than googleserver.com, which can make a fairly significant bandwidth saving for pages which contain a lot of URLs. Have you ever noticed that Facebook used fbcdn.net and Yahoo uses yimg.com for their CDNs? There are several reasons for using separate domains for their CDNs (security, to ensure that cross domain policies apply, bandwidth, to ensure that you don't send cookies to something that will just be serving up static images), but using a separate domain does mean that your URLs are longer, which on a high traffic, highly optimized page, can be a fairly substantial portion of the page content.

Finding a good, short, and descriptive alternate domain can be hard. 1e100.net is really not much worse than yimg.com or fbcdn.net.


I don't think I would have foreseen this circumstance either, but googleserver.com would have been much better than 1e100.net for the reasons I just mentioned in another comment:

http://news.ycombinator.com/item?id=3341017

1e100 has a lot of characters than can easily be misread.


Criminal charges are incredibly unlikely. This was a freak accident, in which they took plenty of safety precautions, but somehow managed to have an accident anyhow. They didn't actually hurt anybody. There are no real criminal charges that could be brought against them.

And it will only be lawsuit city of Discovery Channel doesn't offer an appropriate settlement. I'm sure that Discovery Channel has plenty good insurance, and plenty of cash on hand, and will over to cover the costs of the damages to those involved, plus a little extra to keep them happy. There will only be lawsuits if they don't offer a reasonable settlement, which I would find unlikely.


Also, the great firewall of China, and their Internet Content Provider license (which can only be obtained by Chinese companies) make it nearly impossible for foreign companies to compete in the Chinese market. Even foreign sites which aren't blocked in China are frequently a lot flakier due to the firewall, and they can't put servers inside the firewall without an ICP license. The usual way around this is to partner with a Chinese company, but frequently the Chinese company will wind up cloning your service and becoming a competitor.

The Chinese market is stacked against foreign competition; I don't think that the Indian market is likewise restricted.


I recommend Firefox to some people, depending on what they are looking for. Firefox has had addons for much longer, and they are much more fundamental, than on Chrome or Safari. For example, while Safari and Chrome both have an AdBlock, Firefox's works much better (no flashes of ads, blocks more video ads, etc).

And modern versions of Firefox are doing a lot better again. It is much faster these days. They now have a much better release cycle, and their updater is smoother encouraging people to keep on the upgrade treadmill.

I wouldn't write Firefox off. The recent increase in competition in the browser space has done great things for all of the browsers; they have all improved dramatically over the past couple of years.


Legally that may be what domain squatting is. However, colloquially, domain squatting means registering domains that you don't use just so you can sell them again for profit. While there may be no legal recourse against such domain squatters, most people would still consider it domain squatting and ethically dubious.


"colloquially, domain squatting means registering domains that you don't use just so you can sell them again for profit."

I agree that you are right with that statement. I don't agree that people are well informed about this enough to know that that the statement is wrong.

That belief is something that comes from the days of a few bad actors (panavision and mtv domains come to mind and some others) that made the practice which is now called cybersquatting what it is instead of what it should be based on. And by the way even the current definition was shaped by Intellectual property lawyers as a totally one sided law brought about to protect the interests of a certain class of owners. (As was UDRP process for that matter).

But yes that is the uninformed view of most people. Just like many ordinary people associate the word "hacker" with "bad" and not "good".

As has been pointed in another reply, people buy things all the time with the intent to profit from the sale of which they do not use. Since the beginning of time this has not been a bad thing. And why should it be? (Not to mention the fact that there are alternative TLD's it just happens to be that .com is the ubiquitous one.)


It is generally considered a bad thing to buy things that you don't intend to use, add no value, and sell them at a markup merely due to the fact that they are scarce (artificially, because you bought so many and are controlling the market).

It is considered to be good to buy things that you don't intend to use to resell them if you are adding some kind of value in the reselling; for instance, people who have a local retail store, who are adding the value of being close and convenient, rather than having to go all the way to the producer.

Domain squatters are adding no value. If you just buy a whole ton of domains speculatively, and then sell them off at high markup because so many domains are gone that it's impossible to find good ones, you are adding no value, you are only taking advantage of an artificial scarcity for your own profit.

We have plenty of other negative words for this kind of behavior in other domains. Ever heard of a scalper? There is really no significant difference between a domain squatter and a scalper; they are just people who induce artificial scarcity and use that to run a profit without actually adding any real value.


i fail to see the ethical dubiousness, though. people who can afford to buy land they don't build on are (in most cases) not doing anything unethical. for lots of arbitrary reasons domains are a limited resource. that could change but as it is, domains are like NYC cab medallions. there could be a very legitimate argument that they shouldn't be so scarce, but they are, and owning one is a good, somewhat risky investment. i don't see the difference between owning any of these limited resources with the goal being future sale and profit.


Most types of investments are either beneficial somehow to the market or economy - investing in the stock market is said to promote liquidity - or at least neutral. Domain squatting benefits only ICANN, and on the other hand is actively harmful to people trying to do interesting things with domain names.


Site appears to be down, and Google doesn't have it cached. Anyone have a copy? Also, the title implies that I should know what Path (V2) is; can anyone explain or link to that?


Path released a dramatically new version of their app on Tuesday: http://blog.path.com/post/13533662902/introducing-path-2-the...


Cmd-F (if it searched for the highlighted text) requires two: Cmd-F, return. Cmd-E requires two: Cmd-E, Cmd-G. You only need to press Cmd-F if you need to change search options, which the vast majority of the time, you do not.


It's interesting that you apparently actually checked a validator to get the error count, and yet the two things you cite as errors are not errors, have never been errors, and are not listed in the errors returned by the validator. Both opening and closing tags for the html, body, and head elements are optional, in all versions of HTML that I am aware of (outside of XHTML, which has never been seriously used on the open web as it isn't supported by IE pre-9). There is a tag reported unclosed by the validator, but that's the center tag.

Anyhow, one downside to having syntax errors might be that parsers which aren't as clever as those in web browsers, and which haven't caught up with the HTML5 parser standard, might choke on your page. This means that crawlers and other software that might try to extract semantic information (like microformat/microdata parsers) might not be able to parse your page. Google probably doesn't need to worry about this too much; there's no real benefit they get from having anyone crawl or extract information from their home page, and there is significant benefit from reducing the number of bytes as much as possible while still remaining compatible with all common web browsers.

I really wish that HTML5 would stop calling many of these problems "errors." They are really more like warnings in any other compiler. There is well-defined, sensible behavior for them specified in the standard. There is no real guesswork being made on the part of the parser, in which the user's intentions are unclear and the parser just needs to make an arbitrary choice and keep going (except for the unclosed center tag, because unclosed tags for anything but the few valid ones can indicate that someone made a mistake in authoring). Many of the "errors" are stylistic warnings, saying that you should use CSS instead of the older presentational attributes, but all of the presentational attributes are still defined and still will be indefinitely, as no one can remove support for them without breaking the web.


Well, .local would be reserved if the mDNS draft, http://tools.ietf.org/html/draft-cheshire-dnsext-multicastdn... , ever progressed to an actual RFC. It is already a de-facto standard, with several implementations.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: