Skip to main content

Google Hangouts vs Skype vs iMessage

iMessage and iPhone, iPad, or OSX device are the gold standard for getting all of your devices to ring when there is an incoming call or text message. The actually implementation is a bit harder to realize but it goes something like this.

  • If both parties are an iMessage user then the message is sent through the internet proper to the Apple servers and then directed at the configured devices. (blue send buttons and bubbles)
  • If one party is not iMessage capable then the messages are sent through the traditional SMS network. (green button and bubbles) But if the receiver is an iDevice then the message is redirected back into the Apple message network and is redisplayed on all the subscribed iDevices.

Of course regular phone calls land on the phone and then are simultaneously networked to local subscribed iDevices. This seems to be a variation on the tethering theme only in reverse.

Recently Google Hangouts and Google Voice started to merge.  Hangouts has become my defacto analog phone and desktop SMS. Getting everything working well together was pretty easy but not for the uninitiated. In this sense Google seems to be a bit of a jalopy. The missing element is that it helps to have a google voice account. That allows you to tie all of the comms together across all your subscribed desktops and devices. Transitioning to google voice can be a challenge because it is a new phone number and so you never know who has what.

Google Voice is a topic for another day.

Skype was acquired by Microsoft a few years ago. It was a good buy for them as they needed to capture some technology as well as the "eyeballs". In recent months MS has been collapsing many of their tools into Skype. For example I understand that Lync and Skype are merging in some way. This is a good idea since there is some overlap and it will introduce more new people to the services. The challenge for Skype is (a) their quality is lacking and that may be a function of a less than ideal environment. (b) they invade my address book (c) the abuse that is out there (d) and advertising when I'm a paying subscriber.

The quality issue could be any number of issues, however, it has not improved from the days prior to the acquisition. I think that the Skype team designed a system based on ideal conditions instead of the reality. WiFi conditions vary widely, device capacity to codec demands, local and remote ISP, the networking model (switching only vs switching and media).

Neither Skype or iMessage have a ChromeOS version. But I do not know if I care because hangouts works everywhere I do.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…