yesb

It wasn't stated that it would be funded by income taxes. There is a long list of government services that are funded mainly by usage fees.

That said, I'm not convinced of this idea either. But if you're not going to enforce antitrust laws, it seems preferable to a private monopoly.

It has the ability to decode the audio on the device and output LPCM if the playback app used supports it. The only thing you can't get is the spatial height channels from formats other than DD+ w/Atmos.

It has lossless output i.e. PCM. It does not have the license needed to pass through proprietary Dolby formats other than DD/DD+

It's only kind of accurate. It has to be 2 newspapers in the area the person is employed in. Hard to prosecute them for following the rules they are given.

The rule is the job has to be posted with the state workforce agency, 2 Sunday newspapers, and 3 other recruitment methods (mostly at the company’s discretion). PERM is basically a retention tool as h1b is temporary otherwise. Obviously they are going to choose the 3 methods least likely to produce good candidates. As with most immigration issues, it could be trivially fixed by Congress but won't be.

It's not very accurate, they need to be newspapers where the person is employed. It's the government that is behind the times with respect to how people find jobs. And it's not really "fraud," it's simply companies working in their own interest within the existing outdated rules.

Besides newspapers, they have to be posted with the relevant state workforce agency and 3 other methods. It would not be hard to require that one of those needs to be the company career site or wherever the majority of recruiting comes from.

>RAG on the other hand creates the hardest challenge for these models. It instead puts 5 ideas with the highest similarity into the context in full.

I think what you're observing is that there is more to information retrieval i.e. "retrieval" in RAG than slapping everything into a vector database and calling it a day. There's no such requirement in RAG to mindlessly load the k nearest neighbors into your context and see what happens. That's a very rudimentary implementation.

This markdown system I'd argue is RAG as well. You're just doing the retrieval in a way customized for the problem at hand. If you have a precise method of retrieving the most relevant things, obviously use that rather than a similarity metric. If I'm reading correctly, this markdown system is basically a knowledge graph which is not a new idea.

>Unpopular opinion around these parts, but there's a high correlation between the best candidates and people who take the time to review the job posting and customize their resume before submitting.

There's also a high correlation between matching the job description perfectly and the resume being AI generated and/or dishonest. Doubly so if the requirements are overly specific or contain pure nonsense as some do (saw "Must have 5 years experience with Claude Code" recently). You can filter out people who blatantly don't match the job and those who obviously just copied the job description. Never seen much correlation between the quality of resumes in the middle (ok to great) and how well they do in interviews.

Not to mention at many places "requirements" are mere suggestions or a low-effort list of technologies taken from the resume of the person who quit. Everybody has their own filtering rules and hiring managers rarely agree with each other much less the HR people usually doing the first round of filtering. The true requirements come out only at the resume filtering or interview stage.

>I doubt the "best candidate" is also the person who can't be bothered to take 10 minutes to update their resume before pressing submit.

The "best candidate" a lot of times doesn't mean the best able to do the job. It often means the ones who 1. makes the hiring manager feel good by being enthusiastic about their (statistically) average job for average pay and 2. minimizes their perceived risk of looking bad for their hiring choice.

>If a job listing asks for Python and someone submits a resume that does not list Python, it's fair to reject that candidate.

If you're not a FAANGMULA type place then sure. But also if your job posting lists something like "Python 3.14" or "7+ years Python" I know the hiring manager probably doesn't know the first thing about python. In that case I think it's fair for any decent programmer to lie because they will likely surpass the hiring managers knowledge by studying python a bit before the interview.

No but hole punching isn't really needed in that scenario. Open a port on the IPv4 side + dyanmic DNS. More than likely that is what tailscale is doing for you. Opening a port on that end w/UPnP. But can't argue with how simple it is with tailscale.

Employment green cards are sometimes obtained via consular processing too.

Doubtful. Most consular green card applications are for family based immigration. This pause is also for final interviews for visas that are basically approved already. Labor market test already happened a while ago if relevant.

Employment based green cards are mostly granted inside the U.S. via adjustment of status without state dept involvement.

SSN card + ID works for employment purposes.

Simply applying for renewal or naturalization extends the card as well.

>successive administrations ignored the intent of the law, for so long that people began to rely on assurances that the law never promised. Now that the law is getting applied properly, those people are facing the consequences.

No, there's nothing proper about it and it has nothing to do with the merits of the visas in question. There is no law saying that the state department should make travel impractical for people USCIS has already decided can live/work in the US. The reverse is much more likely. They want to push people off of legally obtained visas by causing unreasonable delays.

H1B is temporary but you can have immigrant intent. It can be extended indefinitely with an approved green card application. Your employer is going to pursue that if you're on h1b and they want to keep you around. Many if not most h1b holders are in that category and will get a green card eventually. They are simply waiting for that to be available due to quotas based on their qualifications and birthplace.

Not sure what you're trying to say regarding back-dating. I think what you're missing is that long term holders of H1Bs universally have an approved PR or at least a pending one. That's the basis for extending it past the usual temporary limit. They need to stay on the work visa (with its limitations) until the immigrant visa becomes available (different from approval).

>seeking permanent residence on a tourist visa is not allowed, under most conditions.

In the US, it's allowed under your stated conditions. Immediate relatives of US citizens can generally adjust status to PR from any status (including tourist visa/visa waiver) or no status. Although if your underlying status expires you could be temporarily detained on a discretionary basis.

That said, it's better to pursue a K1 if you plan to get married shortly after arriving. It's very unlikely you will be granted a tourist visa if you tell the truth in the interview that you're engaged to someone in the US with immediate plans to marry.

Border searches aren't arbitrary when done for the purposes of border security and applied to travelers in a non-arbitrary way. It's pretty clear that CBP agents have a wide discretion to search people at their own whims i.e. arbitrarily.

>that the government does so lawfully

There are many legal question in this case, it's not clear the government acted lawfully. If he'd have arrived in a different federal court district, the search was unlawful because precedent says they need reasonable suspicion.

Not to mention this was a pretext to gather warrantless evidence for the FBI for a domestic investigation and nothing to do with securing the border.

>Antagonising law enforcement in this situation is not a smart move

Not what he did.

Generally I think the person implementing it has a poor native scrolling experience due to poor hardware and/or software and the hijacked behavior seems better to them.