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

I wonder how much of this was driven by public/media interest in the H-1B program rather than technical policy concerns.

For instance, there is still no action taken about the L-1B visa classification, which is a lot more open to abuse than H-1B is. It has no cap on how many visas can be issued every year. It also has no obligation to pay the employee a prevailing wage, no requirement for a bachelor's degree to qualify, and it cannot be transferred to a different employer (which means employees are stuck with their sponsor until they qualify for a green card).


$100k fee is a good start. Trump doesn't know L-1B exists.


I’m not entirely sure what it is, but my Alexa devices hit subdomains within it very frequently based on my local DNS history. That’s probably why it made the top of the list.


Just apply for jobs, and the immigration attorneys hired by your prospective employer will figure it out. U.S. immigration by employment is sadly almost entirely based on petitions filed by your employer. The choice of which visa pathway to pursue is not up to you.

If you're curious: the vast majority of Europeans currently moving to the U.S. for tech jobs typically do so on L-1A or L-1B visas. To qualify, you must work for at least 12 months at the European subsidiary of a U.S. company before being transferred to a U.S. office. There are the occasional O-1 cases but you need significant work experience and recognition to qualify. Lawyers will definitely ask you questions to determine whether you are a good candidate for it.

In the past, H-1B was a way more common route, especially when there was no lottery or at least when selection odds were higher. However, with current lottery odds at just 10-15%, many companies now prefer hiring you abroad and then going for an L-1. As long as you satisfy the foreign work requirement, you are more or less guaranteed approval for an L-1 and there is no uncertainty.

Companies also love transferring employees on L-1 because unlike H-1B it is an employer-tied visa. This means you cannot switch to a different employer, effectively locking you in for the duration of your employment until you obtain a green card, if and when that happens. Keep that in mind if you are offered an L-1: you should carefully consider the green card pathways offered by your employer before you move.


There are no newspaper ads involved in the H-1B program. There is a separate process (LCA) to ensure the H-1B worker is paid the prevailing wage in the location where they're hired. It relies on the Department of Labor making such determination.

Newspaper ad is required for PERM, which is part of the green card process.


> an H-1B holder is legally bound to the hiring company and can't seek work elsewhere

That's not really the case. An H-1B visa holder is not strictly bound to their employer, and is allowed to transfer to a new employer. Unlike visas such as the L-1, which are employer-tied, the H-1B allows for this flexibility. Transferring does require the new employer to file a new H-1B petition, but that process is straightforward and any big tech company will gladly complete that as part of the hiring process.

The main exception arises only when the H-1B holder has just started pursuing a green card. The first step of the green card process, known as PERM, typically takes 1–2 years to complete. During this time, the worker may feel more committed to their current employer because switching jobs would restart the PERM process, potentially delaying their green card timeline.


Yes, the data does include petitions filed for renewals:

> The H-1B Employer Data Hub has data on the first decisions USCIS makes on petitions for initial *and continuing* employment


They're probably referring to the certificate verification that happens when you open any notarized application. Unless something changed recently, the system phones home to ensure its certificate wasn't revoked.


It doesn't do that on every app launch; there's a cache. It does it on the first launch of a binary from a new team.

(So multiple binaries with the same team don't check either.)

And I'd expect all logging is disabled on the CDN.


It does kind of suck if the binary is frequently updated, big and you have a slow internet connection. So some program which normally takes seconds to open can take 20 or more seconds to open after an update. Or if you don't use that program frequently, you always get a very slow start of a program.


I have no reason to expect that it is.


Tailscale runs its own local DNS resolver on your computer at 100.100.100.100, if you have enabled that in settings. Your DNS queries don't go to any Tailscale servers. By default, the client simply forwards all queries to the system DNS resolver, providing some added conveniences like automatic DNS over HTTPS upgrade when available. Also, you don't really have to use Tailscale for DNS if you're comfortable reaching your devices using their 100.x.y.z IP address. See https://tailscale.com/kb/1081/magicdns for more details.

And yes, Tailscale keeps a connection open to its servers to allow other devices to reach you when you're behind a firewall and direct connections can't be established.


L-1A also requires the employee to have worked at the foreign subsidiary of the US company for at least 12 consecutive months.


> most frustratingly I can’t send an SMS to any contact it believes to be on iMessage

You can long press on a sent iMessage blue bubble to reveal a 'Send as Text Message' menu item. It's quite hidden but it's there.


Only if the message didn’t go out to Apple’s servers. That doesn’t help me when I know the recipient won’t be able to receive it (e.g. because they are on roaming or out of mobile data).


If you know you want to send an SMS you can tap it right after you press send, there’s a small grace period. I just did it.


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

Search: