I don't know. This seems risky:

We recommend using this mode in production on well tested codebases where the density of memory safety bugs is known to be low, which is achieved by using the SYNC mode during testing.

And what threat are you mitigating here? Feeder is hardly something worth exploiting.

I don't know. This seems risky:

We recommend using this mode in production on well tested codebases where the density of memory safety bugs is known to be low, which is achieved by using the SYNC mode during testing.

If you have no ability to debug an app nor test it on MTE-compatible device nor offload that testing on users (I am) then it is risky. Anyway I didn't achieve any MTE error on GrapheneOS with that app for few Feeder versions.

And what threat are you mitigating here? Feeder is hardly something worth exploiting.

Well many people do not care about private messages because this "hardly something worth". Same for public media. But for some people spectrum changes, including but not limited with RSS feeds list. Theoretically it is possible to pass maliciously-crafted response for Feeder (Feeder does not have MITM protections - this is expected) and cause in-app memory exploit to, lets say, send all RSS feeds to remote server (well Feeder has access to Feeder's data storage and internet). MTE would make those theoretical (and I hope it would stay that way xD) exploits harder, that's it.

Let's just see..