App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
411–420 of 446 posts
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#412Earlier quoted context omitted.
Also, you can't migrate WhatsApp between iPhone and Android. There's a utility called BackupTrans, which follows an extremely convoluted process including a step where they install an old version of WhatsApp. It seemed to work but it trips some wire and WhatsApp put me in an hour-long timeout state, twice. Since I very much depend on WhatsApp, I dare not use it anymore.
The platform lock-in because of this is immense.
Wiping the WhatsApp chat history on the old phone before giving it to a new owner is also much more important. It often contains highly embarrassing or even incriminating details.
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#413Earlier quoted context omitted.
> Have you ever worked at a large company? yes - and I've done incredibly well during it. I also know change doesn't come for free. the sad thing is the bigger the companies the smaller the spines of the individuals working there.
How much change have you effected in all your time there that you did so well? How much power over projects you deemed immoral did you have? More or less than a random person on the street? Do you feel more responsibility for immoral projects that took place in this large company than for things going on within FB or GOOG?
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#414Earlier quoted context omitted.
The platform lock-in because of this is immense.
I've helped a lot of people to set up new phones and saving WhatsApp chat history is always low on their list of priorities. Keeping their contacts, their photos and all the saved logins for websites and apps are the top 3. Wiping the WhatsApp chat history on the old phone before giving it to a new owner is also much more important. It often contains highly embarrassing or even incriminating details.
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#415Earlier quoted context omitted.
this is a pretty simple way to absolve people of responsibility. Just because an institution has compartmentalized tasks, so that every single individual team appears to do nothing wrong, doesn't mean this actually absolves individuals, because following that logic obviously nobody would ever be responsible for anything. It's like Kierkegaard's example of the mob who collectively intimidates but every member argues t…
> this is a pretty simple way to absolve people of responsibility. Consider this menu of possible ways to be associated with a human rights violation: - Do it yourself. - Be a part of the chain of command that ordered it. - Be commanded by the chain of command that ordered it. - Be part of the same organization as the one that contains the chain of command that ordered it. - Be a member of the society that contains t…
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#416Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#417Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#418Earlier quoted context omitted.
Also, you can't migrate WhatsApp between iPhone and Android. There's a utility called BackupTrans, which follows an extremely convoluted process including a step where they install an old version of WhatsApp. It seemed to work but it trips some wire and WhatsApp put me in an hour-long timeout state, twice. Since I very much depend on WhatsApp, I dare not use it anymore.
Which direction? I and my sis did both directions quite painlessly (includign images etc) a year back.
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#419That’s twice in as many months. They may need some better QA here although to be fair it does seem mostly people with an older SDK version based on the comments. But still. I guess they need to cotton onto whatever server side change happened and roll it back. At least this time you can disable the SDK (at least one app developer has a kill switch for the SDK) unlike the last issue that happened during code initialis…
> They may need some better QA There's no such thing as QA at Facebook. Really. Developers are supposedly responsible for all testing of their own code, but all of the pressure is to "move fast" so that goes about as well as you'd expect.
If you have a team run by idiots, then you won't have QA.
If you have a team run by adults, then there is plenty of QA. I mean its total shite that this wasn't caught. I'd expect much better, especially as this is the second time in n months. But then perhaps working for a company run by a dick who can't listen is getting to people.
Re: App suddenly crashing on startup due to FBSDKRestrictiveDataFilterManager.m
#420Earlier quoted context omitted.
The unencrypted backup system is almost certainly implemented mainly to give government authorities easy access to chat history when presented with a warrant whenever possible. Since this is offered as a helpful feature, very few think twice about the part in asterisk. This way they can comply with warrants without backdooring their app while continuing to sticker label "end to end encryption" and giving people comfo…
That doesn't make much sense. There is no such legal requirement (hence the discussion). The Google backup option isn't universally used. And WhatsApp controls the key generation and management and could easily integrate any other sort of more robust backdoor. Such as their previous system, as described somewhere in this subthread, of storing the key on the server to allow recovery.
On one hand - even after end to end encryption, we continue to see WhatsApp messages quoted in prosecution including in SEC actions and prosecutors are clearly getting access to messages even pre-arrest. The ability of prosecutors to compell unlocking after arrest in US is questionable. So how are they getting access to the messages if there's truly end to end encryption? Also there are any number of Governments in the important non-US markets that would simply ban WhatsApp if they didn't have access against a warrant (eg. See BlackBerry cases from some years ago)
On the other hand, no security researcher seems to have found or at least reported a back door in the WhatsApp apps that supports MITM undetectable to physical key verification which is the obvious weakness in an end to end encryption system based on centralised key repository system.
On the gripping hand, all high profile cases trying to compell tech companies to provide evidence have been against Apple. I've not heard of one against WhatsApp.
Ergo - the most like scenario is that this feature is deliberately built keeping messages un-encrypted so that when law enforcement shows up with a warrant or a muzzled warrant, they can just hand over the archive without weakening their app. People are convinced to opt in because it's the only way to change devices while keeping your messages. To give people comfort that unencrypted messages ate safe, it is sold as as "it's in your own Google drive"