dedward

It's not just your lungs though...

You know that pain you get in your sinuses and ears and other air-pockets in your body when you swim to the bottom of the deep-end of the pool? That's from a pressure difference of like .3 bar. Now imagine something 10 times that.

30 meters is around the commonly accepted limit for recreational scuba diving.

If you are diving you can take a breath of air from your regulator at 30 meters and then, keeping your airway open, ascend to the surface on a single breath. Because you are ascending, the air in your lungs expands as you go up, and you get to the surface with a full breath of air, even though you've been blowing bubbles all the way up.

At 30 meters you limit your dive to 20 minutes... beyond that you risk decompression sickness. At 10 meters the limit is around 3 hours.

In both cases, if you were down for a couple of days, you'd need decompression. The deeper you go, of course, the more dangerous it is as there is more dissolved gas.

Time at pressure is the key, without question.

The longer you breathe at pressure, the more time there is for gas (nitrogen, mainly) to saturate your system (until you are at equilibrium, anyway).

Release the pressure, and it's like opening a can of soda... all that dissolved gas can't stay dissolved any longer.

It takes time to get out of your system as you reduce pressure, so a gradual decompression is the only safe way out once you are saturated.

In a typical submarine, air pressure is maintained at standard atmosphere, relying on structural integrity to keep all that pressure from crushing the ship. That means they can surface any time without risk.

Another neat thing when diving is that if you are down at 30 meters, you can take a breath from your regulator, spit it out, open your airway gently (say "AAAAH" quietly to yourslef basically) and then ascend, you feel like you have an endless supply of air, because that breath you took is expanding on your way up. (That's part of recreational diving.. you can ascend from 30 meters on a breath of air and not get stressed out about it)

You do..(though it's simple, you just sort of humm or go "aaaaah" to yourself, silently.. that keeps your airway open).

No innate reaction - over-inflation would require a positive pressure applied to the lungs - normally as we breathe it's at equilibrium. Your lungs aren't elastic at all - once they are at capacity, over-pressure will rupture them right quick, and you own't feel it coming (but you'll sure feel it happening)

I did a form that worked wonderfully... you entered a zip/postcode (first, before country and such).

The form would look it up in a background ajax call. It wouldn't tell you this or block your actions. If it found a match in our DB, it would populate the city, country fields, not make a mess, and leave you free to edit the form if it was wrong. Your flow would be the same either way.

I think not interrupting the users flow was a big part of it.. it didn't make people go "What? How do I change that? What happened? That's not right".. you just kept filling it out like normal... with some fields pre-filled if you were lucky.

The convention of using relatively-short service-based host portions of an FQDN pre-dates the WWW. It was common to use mail, gopher, irc, whatever for various servers from a functional point of view.

Whether it was an A record or a CNAME record was generally at the adminstrators preference. CNAMEs had their own hiccups and weirdness to deal with, and still do to a lesser degree.

It absolutely depends on the scope and features of the application... the question would hold more meaning if it were more specific?

On exit? They don't even look at my passport on exit.

Oh, if they don't know how anyone found out then that's another issue.. but if tehy are made aware that you placed this ad daily and stopped after you were ordered to not reveal that you had been subpoenad.. your intent is very clear cut as far as a judge is concerned.

You're missing the point though. The judge won't tell you not to lie. He'll tell you not to communicate a fact to people. If you already had a system to communicate that fact to people in a novel way, and you use it to do so, you have violated the judges order. It doesn't matter that you notified them by silence or whatever.

You can't reveal that you've been served. What you actually tell people is your problem, not the courts.

They judge won't have to compel you to lie. He'll simply instruct you not to communicate with your customers in any way about the warrant. If you cancel the canary and your customers find out about the warrant, the judge won't care how you dressed it up.. he told you not to communicate a fact, and you did.

You can't game your way around that.. the court will care about outcome, not method.

If they obtained it from NSA spying on facebook, yeah, that's bad...

But that seems really really unlikely. Much more likely is it was a piece of public information on facebook and she got busted.

Someone working in another country is doing work someone in the country could also be doing, depriving them of a potential job. That's why you need a visa.

Canadians don't need a visa for tourist visits to the US, and passports aren't stamped on exit. It's an incredibly BAD idea in my books, but it's still probably relatively easy for a Canadian to spend a whole lot of time in the US without getting flagged.

Ack.. that's just incredibly poor judgement. If you have to lie to the officials when entering the country, you really shouldn't expect that a closer look later on is going to get you a visa - as soon as they discover you lied about it you're done for.

I think this is a common fallacy.

To randomly pick an example - sure, automatic filesystem snapshots are a cakewalk these days, and a decade ago they were rather expensive. It seems logical to assume that things that we needed admins to do and rig up somewhat delicate systems for a decade ago are so easy now, we don't need people to focus on that...

This overlooks the fact that the baseline has just moved ahead. Sure you don't need dedicated people for stuff you used to.. but there is new stuff out there that your competitors are hiring dedicated people to work on and push the envelope. if you're okay with doing what you could have done 10 years ago, just using reduced staff, that's great - but it's not going to win you much.

Online transaction providers, like Liberty Reserve, Paypal, credit card processors, your bank's website, and so on, are really not digital currencies at all... they are transaction processors.

Bitcoin, and things resembling it are actual cryptocurrencies and something we could truly call an e-currency. It's about as trackable as cash (in that it can be tracked but it takes very significant effort, and it can be traded like cash.. it's much more than a number in some database.)

Isn't skin effect an AC thing in cabling? The reason DC power is sometimes preferred for high-voltage high-power transmission is specifically because there is no skin effect and the cables can therefore handle more power per weight.

There is a good difference between a sysadmin's workstation and/or what I'll call "management servers" - those we use for our own tools and whatnot, and those that we keep up for production use, where uptime is critical and knowing exactly what is going on is paramount.

I use emacs... all the time. It's my favorite editor, bar none.

I use vi/vim every day, because it's always there.

It's not that no file should ever be edited there, but, especially in today's clustered world, it's good practice to keep your servers as minimal as possible.

It might sound silly, but keeping to principles and controlling as strictly as you can get away with the changes that go into your production servers is a good practice that tends to keep things working.

vi is handy because it's always there. Emacs is fine - but it only REALLY shines for me when I have my custom environment set up - for a quick edit, it's just a quick edit.

This, specifically. If they want to deal with ownership do some kind of leasing agreement... otherwise, let's not have public enforcement propping up the business model.

It's a business - you don't sell stuff if there is no money in it. It made you more money being out of the store for that price than sitting in the store... whether it was through rebates from the manufacturer, some contract deal, etc is irrelevant - the business made money.

Maybe it's me, but while this is one beautiful video, and they weighted it pretty well, the motion seems really natural, it's pretty obvious what's going on.

There's absolutely nothing wrong with it in principle.

It's only that as the web grew up, and websites became less a bunch of static files and increasingly an application, or more commonly a pile of application-like messes run by many different people at the same time, involving a bunch of dependencies between files, whether organized code or haphazard things piled on things piled on things, doing staged releases comes to be the more sensible option.

At a certain level of complexity, FTP can become a liability and cost you business.

While this lets those who are going far above and beyond to gather information, the solution is for the storage numbers to be published market-wide, to take away the edge a few have - with enough market pressure this could possibly happen.

Arbitrage is valid, as is doing your research, inferring what's going on with a company and then trading on your assumption.

Insiders are barred from influencing the market with their knowledge, but outsiders who infer what they think is going on, whether it's a sure thing or not, are perfectly fine.

Well, there's a difference between things you don't want to give up, and things you can't give up because you'll get sick as a dog, and/or require hospitalization and maybe die.

How did they trick people? Genuinely curious...

While this is all true - stolen passports are a very real problem, and when I had mine stolen, and got a replacement, it clearly said on one of the first pages "This passport replaces passport #XXXXXXX reported stolen on DATE".

Yes, I lost all my visa/entry stamps.... and yes, that can be a problem - but the fact is, a nation is unlikely to hold you hostage and create a diplomatic incident because your passport has been stolen.

The same argument works for any of those systems.. not just linux.

The reality is many people try many systems and settle on one they like.

Not such a pain once you figure it out... And for any of us compiling stuff... seriously, are we pretending we don't all use remote linux slices/machines/whatever all over the place?

My laptops are just workstations to do day-to-day life stuff and a portal into my virtual computer world, where I'm working with remote displays, browser windows, command lines all over, and all that jazz. If it's anything remotely server related that needs to be on all the time, I'm likely not running it on my laptop anyway - it'll be on a linux box somewhere.

Or, if I'm on the move and it's really important to get a project done, a local VM on the little macbook.