Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment Re:Benefits (Score 1) 158

These tend to be very highly qualified interns, though. Landing an internship that pays this well requires a grueling interview process. And most applicants have advanced degrees (typically PhD's from the more well-known universities). It is generally a good way to enter the work force. In fact, without any other job experience to show for, this is often the only way to enter the work force. And at the end of the internship, most interns will be offered a full time position.

So, if you think of the type of internship you did in highschool, when you helped restock the shelves in your local supermarket, then you are thoroughly misunderstanding the scope of these positions. A more accurate view would be that this is an extended job interview. The candidate already passed all the other requirements (i.e. great resume, multiple phone screens, multiple in-house interviews, ...), but the company isn't quite ready to extend an offer, or the candidate has stated that they still need to go back to school for another year before finally graduating.

Comment Re:In my experience (Score 1) 158

While transitioning from a J1 internship visa to an H1B employment visa is not entirely unusual, it also isn't a particularly useful strategy for the particular example that you are citing. J1 visas are limited to at most 18 months. They are only available for recent graduates or for students who are still in school. For many countries (including India), the visa holder must return to their home country for at least one year after the end of their internship program. Even if this restriction doesn't apply, transitioning to an H1B visa is difficult as there are about four times as many applicants as available visas. And there is only a single day each year, when H1B visas can be applied for. So, in the majority of cases, a J1 visa holder would need to return to their home countries after only a year or at most a year and a half. Also, requirements for H1B visas are somewhat strict. Lots of companies/employees don't even qualify.

Having said that, switching from a J1 to an H1B is an officially sanctioned and intended path to bring highly qualified graduates into the US. It just isn't a particularly easy route these days. And it is quite competitive in those cases, where the paperwork can be worked out. Employers don't get cheap labor this way. They'll have to pay a premium (including thousands of dollars in legal fees) for these qualified employees. Nobody in their right mind would do this, if they can just as easily much more cheaply hire from the local work force.

So, while your posting sounds quite inflammatory, I don't think you are fully aware of the actual facts.

Comment Who cares (Score 0, Troll) 146

Honestly, who still cares about what Consumer Reports has to say? They are certainly still entertaining, but their reviews have been so flawed for at least the last ten years as to be entirely worthless.

I don't know anything about the Tesla. So, it's conceivable that by sheer luck CR hit on some useful bits of data. But in most likelihood, it's just like all their other publications. Any time I read one of their tests for a product that I'm familiar with, they test some obscure and irrelevant detail and base their entire test on this result. Not surprisingly, good and innovative products tend to fail, and mediocre mass market products get all the praise.

It's been a recurring pattern for way too long

Comment Re:Perhaps (Score 1) 598

I know that you are joking. But an often overlooked aspect of the international system (aka metric), is the relationship between different units. It's not just the ability to easily scale a single unit up and down by adding a common prefix such as milli or mega.

For instance, 1g of water is exactly 1ml. And even complicated units like N (Newton, a measure of force) can be constructed from basic units. In this case, that would be kg*m/s^2. Note that there is no correction factor needed. You simply multiply the units. That makes physics and engineering a lot easier and less error prone.

Comment Re:Legacy service on a private LAN (Score 1) 136

You don't need a separate domain for internal services. Use your external domain and create sub domains. All your internal machines could be on dhcp.public.com and all your containers on vm.public.com. Neither one needs to use publicly routable IP addresses, and in fact you can continue using dnsmasq (or an exquisitely DHCP server) to manage this part of your internal network.

You then operate the Let's Encrypt ACME client in DNS mode to get globally trusted SSL certificates. But nobody other than your internal machines will ever get to interact with those certificates.

Comment Re:Let's Encrypt definitely helped... (Score 1) 136

There are several other clients apart from CertBot. Take a look. They are all linked from the letsencrypt.org website. You might find something that is a better fit for you.

I think, there are a couple of ACME clients that also act as HTTPS reverse proxies. That could be a really easy option to solve your problem

Comment Re:Not Your Recipe Site Specifically, No (Score 1) 136

With Let's Encrypt, it is pretty easy to automate all of the necessary steps. When they launched about a year ago, there were a couple of device manufacturers that wanted to know how to integrate Let's Encrypt into their wireless access points.

Each owner of an access point would automatically be assigned a (sub)domain administered by the device manufacturer. I haven't seen any devices for sale that do this yet, but as SSL becomes more prevalent I'd expect routers to create hostnames such as windos123.wifi567.netgear-secure.com, and to automatically make a certificate available.

Comment Re:Needless bullshit (Score 1) 136

You'll need to own at least one domain name (e.g. "example.com"). But it is OK if your internal service is hosted on a sub domain (e.g. "videos.example.com"). So you only need to pay for a single domain name.

The internal host name does not need to be accessible from the internet, just from your LAN. But you need to be able to control DNS for your entire domain. You can then use DNS validation to prove to Let's Encrypt that you control all of "example.com", and they'll issue you a certificate for "videos.example.com", which you can then copy (e.g. with "scp") onto your NAS.

If you don't already have an"always-on" computer, this is well within reach of a cheap raspberry pi

Comment Re:Needless bullshit (Score 1) 136

If you have hundred domains, you should look at using either a hosting service or a content delivery network. Thanks to Let's Encrypt, almost all of the big players allow you to turn on HTTPS support with a single check box. You do that once and you're all set.

As a nice she effect, your site will get much faster, as it can now use HTTP/2, which has huge performance improvements.

And Google's index will rank you higher.

Also, future browser versions won't show warning messages when they access your site (that hasn't rolled out yet, but all the major browser vendors are working on it).

Finally, you get to use new HTML5 features. A lot of the newer features are only available to encrypted sites

Comment Re:And with StartCom dead... (Score 1) 136

If anything, ACME is a vast improvement over what we had before.

You might not mind 1) obtaining a new client certificate, 2) installing it in the browser, 3) generating and uploading a CSR, 4) proving that you have control over the domain, 5) downloading the new certificate, 6) installing it the server, 7) restarting the server with minimal downtime.

It used to take about 30min of work once a year for each of my domains. It also was a little tedious to schedule, as StartCom only gave a relatively small time window to do so. I think it was only about two weeks or so. But everything considered, for a private site with only one or two domains, it just about bearable.

With Let's Encrypt, things are a lot easier. You set things up once, and certificates will continue renewing automatically in perpetuity. Very little if any maintenance is required, and you can do it on your own schedule. Also, Let's Encrypt is much saner with regards to "subject alternate names". That solves a lot of problems that I used to have with StartCom.

Finally, there is a plethora of different ACME clients to chose from with lots of different feature sets and designs. I don't have first-hand experience with how things look on Mac or Windows, but on most traditional UNIX systems (including Linux), there really is no excuse for not setting up ACME. Also, most of the clients support both HTTP and DNS as way to verify control of the domain. That's huge! It solve a lot of the problems of dealing with complicated firewalls and legacy server software.

Slashdot Top Deals

The use of money is all the advantage there is to having money. -- B. Franklin

Working...