| ▲ | lapcat 2 hours ago | |||||||||||||||||||||||||
> Perhaps you should do some reading on the matter? Perhaps you should: https://lapcatsoftware.com/articles/2026/10/2.html > Singleton’s implication was clear. Muse could have read Aten’s Messages communications only if he had enabled both settings, and if so, the columnist had only himself—and certainly not Meta—to blame. Indeed, and it looks like Aten absent-mindedly did all of this! > Meta has a long history of not respecting boundaries once something is technically possible. It's not technically possible for Muse to read the Messages db without Full Disk Access. Aten denies having given FDA to Muse. Thus, Aten is simply wrong, misremembering or something. And if he misremembers about FDA, he likely also misremembers about granting app-level permissions to Muse. Again, literally nobody has reproduced Aten's experience. Show me one other person. In fairness, Aten behaved just like many other users would, mindlessly granting permissions that an app requests. That's certainly a problem. Unfortunately, Aten stubbornly refuses to admit this, instead confusing the problem by suggesting technical impossibilities. Aten doesn't want to take any responsibility for his own actions. | ||||||||||||||||||||||||||
| ▲ | GeekyBear 2 hours ago | parent | next [-] | |||||||||||||||||||||||||
> Indeed, and it looks like Aten absent-mindedly did all of this! Since Aten has clearly said he did not grant Muse the permission to read his messages (inside Muse), I'm not accepting your version of the events. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
| ▲ | givinguflac 13 minutes ago | parent | prev [-] | |||||||||||||||||||||||||
Lmfao you tell someone to read and then post your own opinionated blog post? I would reiterate that you need to read, perhaps outside your own bubble. | ||||||||||||||||||||||||||