In US you don't. It's common to dial US numbers prefixed with 1 without any international code.

Just remove top bezel and add one more LCD that you can unfold (having total resolution of 1366x1536) , and it would be perfect.
Though it would need some balancing

It doesn't really matter if it's delayed 10 or 100 years, the difference out there will be insignificant

Without Russian rockets it's not much of use. US already got launch facilities, but they don't have any rockets.

Please do track to which sites you are copying my information, and also please can I see the list.
Option to remove some information from specific site would be nice.

You can get redundancy.

We do have multiple Asterisk servers on Amazon EC2, each of them can take role of another. Amazon has availablity zones, so if there is problem, it's within single zone, so it's best to have replacement in different zone.

As for ISP - we have several, and as we can control our servers, we can just quickly reroute calls to different ISP in the same office. If all of our ISPs would give us access to switching BGP, it would be even easier.

As our business depends on phone calls heavily, our telephony carrier has granted us use of backup gateway,where they can reroute DIDs within 30 minutes.

As a VoIP engineer, I need it. In fact I need multiple phones, so I have 5 different models.

You can take it to Shipyard(r) approved waters only. It's not meant for sea or ocean. And only if You hold the steering wheel correctly.

Try querying book readers (Kindle could still count)

So they would just automatically match scenes from other recordings (and knowing which channel it was recorded helps), and keep single copy of every possible difference (ads, logo). Put all that in the nice box of interface for retrieving every individual copy and call it "compression".

I work on a telephony infrastructure (voip pbx + websites), and production releases are as often as we need it.

Even if every minute of bugs or downtime costs money in terms of disconnected customers, gain is by being able to react and fix quickly. Sometimes I do write a quick code (usually fix) on live system, of course knowing what you do and what's on the stake makes you pay attention to details, taking a look on semicolons at the end of line before hitting save.

Also having control of replicating changes to all servers is a good tool, you can do a live test on small set of users, and if there are no errors just replicate changes to all servers.

However normal "feature" releases are usually from couple of times per week to once per month, depending on the size of features.
Rollbacks are always in mind, but you can't rollback everything, new call logs and recordings are created live - so either implement some backup of raw data and be prepared to manually fix broken parts later or you may just loose something important.

You're getting redundant. How can you secure and verify HSTS origin (to transfer info about allowed CA), if you don't know with whom you established HSTS (there is no authority that has signed it).

Current CA scheme works as it is, because CA information is included in browser, and in order to replace that, there has to be other means to transfer authority information (DNSSEC could theoretically be usable)

Mod +1 Funny

I guess BBS will become popular again.

So, you could actually create signalling protocol based on ring times and pauses between them. Just install an app, and you have slow but totally free messaging service.