Live data from Hacker News

Facebook Messenger, Instagram and WhatsApp Outage

developers.facebook.com

161–170 of 252 posts

Re: Facebook Messenger, Instagram and WhatsApp Outage

#161
post #89

Earlier quoted context omitted.

Yes that was a defense. Explorer.exe and IE were intimately tied together. Remember “active desktop”? You could make your Windows desktop background a web page. Crazy times...

I wouldn't mind that, actually. I could create my own dashboard/background.

This can still be done.

Re: Facebook Messenger, Instagram and WhatsApp Outage

#163
post #48

"But senators, we can't break up these three unrelated services because they all use the same messaging infrastructure!"

I laughed at this because I thought the same thing. Conspiratorial or no, that line of argument won't fly. Saying everything is so integrated that it can't possibly be decentralized is basically proof of monopoly.

What? How is that proof for a monopoly. Doubt things are that integrated but if they were then it would be proof of incompetence.

Re: Facebook Messenger, Instagram and WhatsApp Outage

#164
post #108

Earlier quoted context omitted.

Correct, I'm referring to e2e. My personal trust model is not to trust the server.

Right, I understand. It's still encrypted, though, just not in a way that you like.

Nobody should like just SSL.

Re: Facebook Messenger, Instagram and WhatsApp Outage

#165
post #138

Earlier quoted context omitted.

I think the arguments will be - FTC Approved these as as legitimate acquisitions - Facebook has direct competitors that can overtake them in just a few years - Instagram was made by a few python coders in months. This shows how easy it is to make a product that competes with Facebook

Parts of IG in the early days involved filters on iOS, which at the time there was no library for. My understanding. The web version was Django, yes.

By web version I'm guessing you mean server side?

Server side was a few python components with lots of tricks in Postgres for scaling purposes. You didn't have any real choices for what language you used in iOS

Re: Facebook Messenger, Instagram and WhatsApp Outage

#166

Earlier quoted context omitted.

nope. proper and full implementation of BCP38, MANRS, full RPKI validation of all IP ranges and such is a long distance away. within trusted groups of ISPs where the admins all know each other, in certain specific geographic regions, it's better than others.. I would say that the number of ISPs I could call "fully compliant" with current best practices, in the Portland-Seattle-Vancouver area, is higher than in many o…

As someone interested in the internal workings of the internet, do you have any further reading on current best practices?

ARIN, RIPE and APNIC publish a great deal of useful documentation on how to set up BGP stuff properly in the modern era. And information for how to fully implement dual stack with ipv6.

As for other current best practices there's really a very great variety of disciplines involved in ISP operations, depending on what type of ISP it is. What's relevant for a GPON FTTH last mile provider might not be as relevant for a colocation/dedicated server ISP. Or for a WISP. My recommendation on that would be to pick the subject to research and make inquiries in the special interest groups dedicated to that (for instance, two way satellite, or automated billing/provisioning systems for hosting companies, or CRM systems, or whatever).

Re: Facebook Messenger, Instagram and WhatsApp Outage

#167

Earlier quoted context omitted.

> Saying everything is so integrated that it can't possibly be decentralized is basically proof of monopoly. That doesn't make any sense to me. I would expect different applications from the same company to share the same underlying infrastructure. Whether or not they are a monopoly is orthogonal to the issue of integration.

> Whether or not they are a monopoly is orthogonal to the issue of integration. So, I get you here and what you're saying. But companies at this scale argue they're "independently managed" or whatever. With that context, for Facebook , there's really no way of saying that these 3 different brands are independent when it comes down to it. It'd be much like Procter & Gamble saying their 100s of brands were all really d…

At the far end of this reasoning three separate companies that all use AWS share the same underlying infrastructure and all go down when AWS does. It doesn't mean they're not independently managed.

Re: Facebook Messenger, Instagram and WhatsApp Outage

#168
post #167

Earlier quoted context omitted.

> Whether or not they are a monopoly is orthogonal to the issue of integration. So, I get you here and what you're saying. But companies at this scale argue they're "independently managed" or whatever. With that context, for Facebook , there's really no way of saying that these 3 different brands are independent when it comes down to it. It'd be much like Procter & Gamble saying their 100s of brands were all really d…

At the far end of this reasoning three separate companies that all use AWS share the same underlying infrastructure and all go down when AWS does. It doesn't mean they're not independently managed.

But there aren't 3 different Amazon marketplaces--owned by Amazon--built on that infra. And AWS is available standalone.

Here we have core infrastructure that isn't sold to anyone else and powering 3 supposedly different social messaging services.

The key isn't the backend, it's the supposed independence of the frontends.

Re: Facebook Messenger, Instagram and WhatsApp Outage

#169
post #89

Earlier quoted context omitted.

I wouldn't mind that, actually. I could create my own dashboard/background.

Well as always, that can easily be done on Linux. There is even a widget on KDE that lets you do precisely that.

Please say more!

Re: Facebook Messenger, Instagram and WhatsApp Outage

#170

Earlier quoted context omitted.

In the same way that FB, Whatsapp, and pretty much every other app works. I doubt there are any chat apps that don't encrypt between the client and server.

To be fair, when Telegram launched WhatsApp was still unencrypted. It was a big part of Telegram's marketing at the time.

Exactly. Sadly they didn't hold their promises
Post reply on HN