Funny enough, at one point Microsoft basically merged Skype and MSN, and the text chat parts of Skype started using “MSNP24”, a couple version numbers up from the latest MSN protocol, MSNP22. I never dug in to see how much it was really like MSNP from MSN because I lost interest in Skype not long after.
Though to be clear, yeah, it didn't really fix the mobile app. It felt just as broken up to the moment I uninstalled Skype.
This isn't a fact of life, this is a flaw in the API of most popular mobile OSes. Open source comunnity maintaned operating systems have solved the problem of providing a network service for handling push notifications (local or not) multiple times now and these companies have refused to implement them because it makes it much easier to create an ecosystem around their crap.
This gives them controll and controll can be traded for money, it has aboslutely nothing to do with technology. That's just life
However, even if you allow apps to run in the background basically indefinitely as Android once did (there were IRC clients that Worked, using only the phone,) it simply is bad for battery life. Having multiple push services that are blessed to run periodically is also just not good for battery life. The proof is in the pudding; I switched to IRCCloud for IRC on the go after noticing what a terrible battery drain it was.
Now, third party push services can certainly do better than IRC, but they’re still centralized. Decentralized networks are just not power efficient. It requires always on machines to be effective.
I’m not saying I love the status quo, but it’s unclear how to do better.
(Obligatory legal line noise: these are my own opinions and not those of my employer.)
I mean, you could just run IRC in a TUI (e.g. Irssi or WeeChat) and connect to that via Mosh plus Tmux. You'd have low latency, 24/7 uptime, resuming, low resource usage... but no push notifications.
And yes, doesn't mean MSFT doesn't have access to other communication and doesn't mean other cases aren't serious leaks of information to arbitrary contractors.
>An industry source disclosed that America's supersecret National Security Agency (NSA) is offering "billions" to any firm which can offer reliable eavesdropping on Skype IM and voice traffic.
And then Snowden revelations confirmed that MS was intercepting Skype [2]:
>Microsoft has collaborated closely with US intelligence services to allow users' communications to be intercepted, including helping the National Security Agency to circumvent the company's own encryption, according to top-secret documents obtained by the Guardian.
>In July last year, nine months after Microsoft bought Skype, the NSA boasted that a new capability had tripled the amount of Skype video calls being collected through Prism;
[1] https://www.theregister.co.uk/2009/02/12/nsa_offers_billions...
[2] https://www.theguardian.com/world/2013/jul/11/microsoft-nsa-...
That was immediately before O365, and at that point BPOS/Exchange online was starting to get traction with some governments. Microsoft was also ramping their OCS/VoIP business.
Government is a huge market for O365, they were able to get ATOs and go conquer most states and federal agencies. They also bought a huge VoIP play, learned how to operationalize it, quickly spun it into a service component that serves >100M people.
Microsoft, like any company, isn’t good or evil, but will do whatever is in the company’s best interests, and they’ll act appropriately when their interests align with the government.
Skype looked like a solid investment at the time. Microsoft makes a lot of money from corporate clients so it's probably just another strategic acquisition that they did not know what to do with.
There is a difference between being compelled to spend billions on a company just to provide wiretapping for feds, and buying a company with a wildly successful product then being asked to handle wiretaps after the fact. One of those is ridiculous, the other is expected.