It’s funny, this is the sort of harshness and absolute certainty Jen would have come out with. Nothing is certain but my opinion given the outcome is that it definitely did not help.
Psychedelics are extremely strong experience, ayahuasca is supposed to be the strongest. If you have anything broken in your personality, it will come up. Thats why at least initially it should be screened and if OK handled by professionals who can lead, guide or stop the experience if needed.
I've seen lifelong schizophrenia triggered by nothing more than a bit of binge drinking. For some people it takes trauma to trigger bad things, some drugs, some have luck and manage to go through life with such a thing without ever experiencing it. Powerful tool, nothing more, nothing less.
It's an objective comment on your subjective opinion of an N=1 result. You are free to share your opinion (and I may even be inclined to agree with you) but it holds no scientific value.
N=1 is perfectly relevant to an individual occurrence when the N and the event in question are one and the same. If I kill myself with a hammer n=1 hammers were fatal to use in my case. I don’t see anyone asserting that this means that broadly ayahuasca is dangerous or claiming scientific relevancy.
> A full-time attacker just need to spend their day scouting for approved firmwares and re-use them
What do you mean by that? The secure boot chain (all the way from the boot ROM) must not be broken for "hardware-backed" Play Integrity to pass. How could you reuse firmware with that in mind?
Play Integrity API passes enough for most apps, including Google Pay (the only known exception is Mc Donalds) by simply reusing the "fingerprint" of another device (the "fingerprint" is basically just a version number, except it's globally unique not just model-unique). In those cases, if the system says "sorry I don't know how to do the secure boot chain verification" rather than "the secure boot chain says it is an un-certified firmware", Play Integrity API will say all is good.
Most apps aren't built to use it, especially on mobile. Think of the use case of your grocery list--you want one tap, open the list, type type type, and done. Anything else--having to tap save, sync, write a commit message, etc... anything, is a fail in my opinion. Git is great to use behind the scenes but I don't want to see it in the UI or slow down my workflow.
Indeed, this can be done, but usually isn't. And when it is done, it looks like another proprietary syncing protocol.
The thing is that you should not expect a user to explicitly host a git repo somewhere to for a grocery list app. Most apps are designed for users who are unwilling to do that, and are actually ready to pay to avoid whatever technical hurdles.
OTOH I see a niche for an app geared towards more technical users, chich would, among other things, allow you to point at a git / hg / whatever repo to use as the synchronization point.