In the first version of iOS, I don't think we'll be supporting iMessage. Texts runs on your device and not our servers (this is how E2EE is properly supported for example), this comes with some limitations.
We are working on solutions though, it's in the roadmap to support all popular platforms, on all devices.
We'll try to make the FAQ more clear ^^
Isn’t this pretty much impossible as things stand? There is no public API for reading iMessage information and all third-party apps are sandboxed on iOS.
Are you counting on some kind of policy change from Apple?
The minute that changes / the minute further sandboxes come in to prevent reading of the unencrypted chat at rest, these are at risk.
It does seem like even automattic is counting on putting more people into a common address-space before that happens so they can continue to build out their network and support protocols that are platform and device independent.
> "Just as an engineer, I can’t ethically support" the cloud-first model, Mullenweg says.
Beeper includes a web service as part of the deal, so if you're good with that then yeah it'd be better, especially since it's ready now and it the faq you linked says they don't store your chats via the service.