Note that Leavitt's words are any more enforceable though.
5,938 karma · joined December 24, 2013
Note that Leavitt's words are any more enforceable though.
The general public's opinion that it was grossly unjustified and most likely going to be rolled back does not change how clear the initial order was.
The fact that virtually every immigration attorney and firm was on the same page about it goes to show how clear it actually was.
They are more than welcome to roll back this asinine decision, but pretending that everyone else is just mis-interpreting is gaslighting.
Either way, until there is an official, in-writting announcement that can be depended on, no one should be taking the advice of an unnamed White House source.
In any situation, your best bet is to follow the direction and guidance of your own attorney.
If you are sponsoring an employee for a visa and "it's a great thing they can't quit, it's the main thing that's keeping them here!", then you are abusing the system and should be excluded anyways.
The current approach is that the content served is the same for humans and agents (ie, a site serves consistent content regardless of the client), so who a specific header is "meant for" is a moot point here.
Yes, there is a huge problem with AI content flooding the field, and being able to identify/exclude it would be nice (for a variety of purposes)
However, the issue isn't that content was "AI generated"; as long as the content is correct, and is what the user was looking for, they don't really care.
The issue is content that was generated en-masse, is largely not correct/trustworthy, and serves only to to game SEO/clicks/screentime/etc.
A system where the content you are actually trying to avoid has to opt in is doomed for failure. Is the purpose/expectation here that search/cdn companies attempt to classify, and identify, "AI content"?
Meta can make 40 of these hires (over a number of years) and still be in a better place than feeling like they have to make a single $10B acquisition (if they could even make it at that point)
Really not sure where you got that from, but even if it was true, most non-tech people will still shy away from putting a 250G file in a cloud service once they get prompted to upgrade their plan because they don't have enough space.
The issue isn’t an acquisition not working out, it’s that the founding/exec team felt it appropriate to arrange their own exits and abandon their team before even communicating that their “successful exit” wasn’t actually happening.
At least in the Scale case there seemed to be some form of payout to employees and equity holders, but this takes it a whole lot further by just throwing out all other employees.
There is supposed to be the concept that “all common stock is the same”. These fake-acquisitions completely undermine that.
They’re just not enforceable against “rank and file” employees.
It very much seems it's been an investment in getting himself to be more of a "household name in AI". That is exactly what Meta needs (or at least thinks it needs) now.
I very much believe that there is very little moat in AI (currently, and in the forseeable future short some underlying hardware/etc breakthrough), and the success (from a consumer perspective) will come down to which of the big-cos (Facebook v Amazon v Google v OpenAI v Anthropic/Claude) consumers trust more. Zuck is, to put it mildly, *not* a trustworthy name for Meta to associate to leading the product that they want consumers to trust and depend on for their entire lives.
Whether or not Wang has any more qualifications than 1) is somewhat of a recognized AI name, and 2) is okay at speaking confidently on topics someone briefed him about, I don't think really plays much into this. If he needs help/assistance/etc with any of the meta scale/politics/management/etc, zuck can buy that for him.
What Zuck can't seem to buy (for himself) is some level of trust.
The net result here seems to be a tax-induced penalty to any (software) organization < 5 years old, as compared to a (software) organization with 5 years of employee history.
How would Disney feel if the salary paid to the cast of the Avengers was no longer an expense in that year, but amortized over the entire copyright period of the film.
No portion of my initial comment should have been interpreted to mean that employers do not do their own due diligence after actually hiring someone.
I've been through this process many times, and I would always say yes and then mention with the recruiter (even if I had to explain that the process was basically "asking politely for permission at the border").
The underlying question that employers really care about is "will you be legally allowed to accept a job offer without unexpected expenses or delays". Even if you file through USCIS (and not petition at the point of entry), you can (should) have an answer in 14 days and ~2k in fees, which is 1) a drop in the bucket for any hiring budget, and 2) not impactful to a hiring timeline.
With genAI and LLMs making way into every profession, how much of an impact have you seen on the immigration law side? Have these style of tools made your job easier, or are they adding more confusion and uncertainty?
Given the rapidly changing landscape (on the immigration side; what is valid today may not be valid tomorrow, and everything seems kind of up to the best guess of the practitioner) do you see these tools (potentially) causing more harm than good (to specific individual cases)?
Of the technical, hang-out-on-HN crowd? Ya, probably not many.
Of the other 99.99% of computer users? The majority of them wouldn't even think about it, let alone care. To quote a phrase, ”the user is going to pick dancing pigs over security every time”.
Even without the non-chalent attitude towards security, the majority of the population has been so conditioned that everything they do on a computer is already being sent to 1) Apple, 2) Google, 3) Microsoft, or 4) their employer, that they're burnt-out of caring.
All that is to say that if you can make a widely-available real-time LLM assistant that appeals to non-technical users, please invite me to your private-island-celebrity-filled-yacht-parties.
And it's great that the US is (seemingly, somewhat) catching up.
I do see this being great for short utility trips (think running errands, picking something up, etc), and as a utility vehicle (would be nice to be able to have an 8ft bed).
It would be really interesting to me to see a fleet of vehicles like this that are ultra-rentable; think a Bird/Lime scooter, but a utility truck.
Ya. Not saying that it's applicable to everyone (or even most people), but really once a team gets above maybe 20+ people actively using this, they're not going to blink at $1200/month (good for you now, but you'll be leaving a ton of money on the table, and it's hard to adjust expectations later).
Maybe capping the size of a team on the "pro" plan would be an inbetween, but it's something to talk to your customers about.
Happy to chat more directly; my email's in my bio.
Okay, I'll bite. My issue w/ statements like "building something an LLM will do in the future" is a constant goal-post moving argument.
It seems to equate to "how is this getting funded when AGI is going to do it eventually anyways". That applies to literally everything. "Why bother building a social media platform, soon an LLM will be able to build an entire one in a day!", "Why bother becoming a plumber, soon an LLM will be able to control manufacturing equipment to build a robot that can do it better than any human", "Who needs architects, LLMs will soon be able to design perfect buildings for whatever use case!".
If your point is only that some companies are currently getting funded that are a weekend-project away from getting Apple-d out of existence, then I would definitely agree that some companies are like that (just like some app companies were like that 6 years ago). Some companies are just super basic wrappers around someone else's LLM, but the expectation (from investors, at least) is that there's a bigger goal and the "easy weekend project" approach is for validation and building some sort of user base now.
However, I also disagree that this is the case here. Building good UX's around LLM usage is not just "using LLMs", and figuring out the use cases people actually want is also not just "using LLMs".
I'm actually pretty impressed. A couple things though:
1. It took a _while_ to give me anything. Not sure if that's related to load, but it was ~17 files, and probably took 5+ minutes. It was not clear what was going on in that time, or what would happen if I left it. I literally left my machine to go something else before coming back.
2. I really hate saying this, but your pricing is probably way too low, especially at the "pro" level from your pricing page. When stepping into team-based config management and pre-sets, you're leaving a ton of money on the table without enterprise-style custom value-based pricing. If you were asking me, I would recommend moving the team based features (shared presets, custom access control, etc) into an "enterprise" level above pro).
I'm not going to comment on any sort of "correctness" as far as any complex UX behaviours or workflows; I'm only considering this from a mockup/design/demo-of-new-ideas perspective.
If I was to donate 9 (or 10) figures to an institution, I would want to make sure it is used to support what I want it to support (cancer research, scholarships, libraries, etc), rather than be used as a general slush fund.
It's not entirely about what the organization wants, but also what the donators/sponsors want.
> Air Mail Act of 1934: > This legislation prohibited the common ownership of airlines and aircraft manufacturers to prevent conflicts of interest and promote fair competition in the aviation industry.