Uhh. No. That's a common misconception held by people that don't actually read their T&Cs. Your worth authorization is tied to "a" employer for the first two years. The employee is completely free to quit and enter into a contract with another employer. All you have to do is go get the name of the employer updated. It's just a formality and nothing else.

Yes, you have three months to find a new job if you're fired, but it's Europe, you most likely got at least a 3 month notice as well.

Here in Norway it's 6 months[1] for skilled workers, and if you get the same position somewhere else you don't need to reapply. If you change position you need to reapply.

[1]: https://www.udi.no/en/answer-pages/answers-skilled-worker/#l...

You are arguing about semantics of residence permit vs work authorization which is not the core of the issue. If you get fired and don’t find a new employer then you leave in 3 months.

Also, it is definitely not just a formality to change employers. For example, on a blue card the new employer must prove to the ministry that they couldn’t find anyone local or EU to fill this position aka “Labour Market Test”. The position needs to be registered in a special gov database to prove that, etc, etc.

The requirements are far from uniform, because each member state sets its own policy. For example, Finland requires the labor market test from ordinary employees but not from those with a Blue Card or those applying for a specialist permit (similar to the Blue Card).

One of the previous times this was posted, someone offered to print and ship them. I got a A2 sized canvas print. It hangs in my home office now.

Anecdata don't make facts

It’s better than nothing. If he has something better than nothing he’d present it. I doubt he does though.

I applied to one of those positions at Canonical. Their hiring process is so bad, I noped out. No wonder they have open positions all the time, since serious engineers are not going to put up with those shenanigans.

What does my high school GPA and traits have to do with my work as a senior kernel engineer? It reeks of cliques and I want nothing to do with it.

That's pretty easy with Wget. You can use `--accept-regex` to define the paths your recursion should follow.

Huh, must be new. <checks changelog>. It was only added in 2012.

Or wait, was the problem that that breaks `--page-requisites`?

It should not break `--page-requisites`. If it does please file a bug report with a reproducer

Just a heads up, but you've swapped the links and the titles.

That's a very nice summary. But you're missing one crucial point. These are GNU tools and if you use them within that ecosystem, you also often use gnulib.

Gnulib is effectively the GNU Portability Library. Your fancy, new, auto generated configure script can find all the differences, but someone still needs to account for them and write alternative code to support the various platforms. This is where gnulib comes into play. It reads all the configure checks and plugs in replacements / stubs for whatever is different. This allows you, the developer to simply target GNU/Linux in your code while gnulib handles everything else (and pretty automatically) making is portable across all the unices and even non UNIX systems.

Yea, I completely forgot to mention gnulib.

Yeah, there’s a lot of software that uses autoconf without gnulib. It’s common to include a load of default platform tests in the configure script that are used by gnulib, but without gnulib the software never uses the results of the tests. All these futile tests are an appalling waste of time and energy.

This exact thing happened to me. I maintain a fairly popular free software project. A few years ago, I received an email from a nasa.gov domain claiming that they want to use the project internally and are auditing all their suppliers. They wanted documentation on me and on how I audit my supply chain for the project. Not cool. I don't have time for these shenanigans in my personal time.

I'm sure you had the choice not to provide that documentation, right?

Well, yes. And I chose to exercise that right.

The point of the anecdote is to supplement the parent poster by stating that their hypothetical scenarios are already happening.

We should have better testing and more eyes on incoming code for projects we depend on. But my point I guess is that vetting maintainers is not an option.

That used to be a fairly common standard. You'll notice nearly all the old GNU / BSD tooling use this paradigm. It is even codified in GNU's coding principles. In fact, when you do that, you can even merge all the single character flags together. For example, I can type, `ls -lah` instead of `ls -l -a -h`. Pretty handy.

My pet peeve is commands not supporting -h for help and making me write --help. This is especially worse when the command already supports single character arguments.

Dont forget when it provides -help but not --help, and -h is is an invalid argument.

Specifically in the case of paperless-ngx, I use their export facility from a cron job. The export is plaintext and contains all the information needed to recreate the postgres db and the learned identifiers. In case of a disk failure (and I've had one with my paperless store), I just reimported the previous days backup from my offline backup of paperless' export.