My time to apply for citizenship based on my EB green card is approaching (4 years and 9 months, right?). Is it still advised for employment-based cases without children to file the N-400 without a lawyer?
Additionally - I will be getting married, to a US citizen, after filing the N-400 but likely before it will be approved or before the oath ceremony. Does that change the answer? In theory, she's not benefiting my case and not benefiting from my case, but I'm not sure if USCIS has a different opinion.
Your impending marriage doesn't change the answer and the answer is that naturalization applications are very easy and don't require the assistance of a lawyer unless there's an issue, specifically, a criminal record, a history of immigration violations/non-compliance, or extended absences (more than 6 months) from the U.S. while a green card holder.
Next.js doing that is like ASP.NET in production "in debug mode" printing stack traces, or PHP applications printing their MySQL connection errors. So sad.
I've been seeing this all over the internet, even on news websites that have already loaded their content. So Next doesn't allow me to read text that's already loaded in my browser because of some random JS error I don't care about.
If the US makes it illegal to train LLMs on copyrighted data, the US will find a solution and not just give up and wait half a decade to see what China does in the meantime.
Zillow have the MLSs network that provide them lists, a similar solution could apply if courts agree that library copies apply for this - Anthropic could sign agreements with large libraries and "check out"/"freeze" copies for a minimally-agreed-upon duration and query across all to see which has a copy of each book they need. Spotify and Apple Music sign deals en masse with labels, the same could apply here with book publishers, labels for lyrics, museums for art, etc. Or whatever other creative solution that people who will need to find, will find. Right now they took the laziest path, because it worked. They will find the next-laziest path that works.
And the easiest option: Legislation change. If it's completely decided that the current law blocks LLMs from working in the US, the industry will lobby to amend the copyright law (which is not immutable) to add a carveout for it.
You're assuming that people will just give up. People never gave up, why would they now?
> HP has some enterprise division that makes stuff I'll never see and
It's a separate company now: HPE "Hewlett Packard Enterprise". He mentions them in the blog post, but if you don't know that in 2015 HP split into two companies, you might not realize. He holds stocks in both companies, HP and HPE (in 2015, it was the same number, but since then there were some splits).
> The license entitles you to receive lifetime updates for the major version. When we release the next major version, you can optionally renew the license.
Fairly common. JetBrains started that way too. Will they one day have a major version that's using a subscription model? Perhaps. But they will likely not regret this too much.
Insert some convoluted argument about new versions being "new versions" and not updates, so one is not entitled to them ;-) , just like politicians argue things like genocide not being genocide.
I hate the subscription model but I do recognize if they continously update the software, they'd like to get paid to do so.
> I've seen most of them moving to internally signed certs
Isn't this a good default? No network access, no need for a public certificate, no need for a certificate that might be mistakenly trusted by a public (non-malicious) device, no need for a public log for the issued certificate.
Yes, but it is a lot more work to run an internal CA and distribute that CA cert to all the corporate clients. In the past getting a public wildcard cert was the path of least resistance for internal sites - no network access needed, and you aren't leaking much info into the public log. That is changing now, and like you said it is probably a change for the better.
Not everything that's easy to do on a home network is easy to do on a corporate network. The biggest problem with corporate CAs is how to emit new certificates for a new device in a secure way, a problem which simply doesn't exist on a home network where you have one or at most a handful of people needing new certs to be emitted.
I think you're being generous if you think the average "cloud native" company is joining their servers to a domain at all. They've certainly fallen out of fashion in favor of the servers being dumb and user access being mediated by an outside system.
I think folks are being facetious wanting more for 'free'. The solutions have been available for literal decades, I was deliberate in my choice.
Not the average, certainly the majority where I've worked. There are at least two well-known Clouds that enroll their hypervisors to a domain. I'll let you guess which.
My point is, the difficulty is chosen... and 'No choice is a choice'. I don't care which, that's not my concern. The domain is one of those external things you can choose. Not just some VC toy. I won't stop you.
The devices are already managed; you've deployed them to your fleet.
No need to be so generous to their feigned incompetence. Want an internal CA? Managing that's the price. Good news: they buy!
Don't complain to me about 'your' choices. Self-selected problem if I've heard one.
Aside from all of this, if your org is being hung up on enrollment... I'm not sure you're ready for key management. Or the other work being a CA actually requires.
Yes, it's more work. Such is life and adding requirements. Trends - again, for decades - show organizations are generally able to manage with something.
Adding machines to a domain is far far more common on bare-metal deployments which is why I said "cloud native." Adding a bunch of cloud VMs to a domain is not very common in my experience because they're designed to be ephemeral and thrown away and IPA being stateful isn't about that.
You're managing your machine deployments with something so
of course you just use that
that to include your cert which isn't particularly hard but there's a long-tail of annoying work when dealing with containers and vms you aren't building yourself like k8s node pools. It can be done but it's usually less effort to just get public certs for everything.
Is B Corp a real thing? It's not equivalent to non-profit and they can always stop being B Corps. Wikipedia lists Nestle Nespresso as a B Corp example, not very inspiring.
Additionally - I will be getting married, to a US citizen, after filing the N-400 but likely before it will be approved or before the oath ceremony. Does that change the answer? In theory, she's not benefiting my case and not benefiting from my case, but I'm not sure if USCIS has a different opinion.
reply