@[email protected] No, that's not correct. It seems you have gotten some misinformation. See the following for a recent implementation:
https://tjthinakaran.blog/wp-content/uploads/2024/04/Beeper-attachment-3-28-24.pdf
@[email protected] No, that's not correct. It seems you have gotten some misinformation. See the following for a recent implementation:
https://tjthinakaran.blog/wp-content/uploads/2024/04/Beeper-attachment-3-28-24.pdf
Webapps generally rely on TLS for data in transit, but full E2EE requires data at rest encryption as well
Since whatsapp is not a part of the hardware storage at the block level it has no control over anything other than the data it presents to the OS -- which may or may not be encrypted separately.
I don't use whatsapp so I've not looked into that side of its implementation, but here's the NCC audit if that seems appealing to review: https://www.nccgroup.com/media/phzpm0qv/_ncc_group_metaplatforms_e008327_report_2023-11-14_v10.pdf
@[email protected] @[email protected] yes! I was just mentioning that in another response. love gemini, still need to setup a server. π€©
@[email protected] @[email protected] that's a great page. reminds me of a purposeful design choice from the Gemini protocol project; it's all text for similar reasons.
@X_[email protected] indeed, which is why I run those from an isolated jail. it's a slight amount of cli commands but otherwise nicely secured.
@[email protected] Brave is awesome overall, and at present their sync chain method has been nearly impervious to split-brain conflicts across multiple devices.
Otter browser is ultra minimalist approach, has almost no chrome or aesthetics to alter, which is a benefit and detriment depending on use case. I like using it for single window admin apps (iKVM, iDRAC, PiKVM, etc) due to the lower resource load.
@JackbyDev Why would that be a question at all? Buy a domain name and take care of your dns records.
that's an odd way to say that you don't own any domains. that's step one, but does it even need to be said?
@[email protected] for sure, and that is a present concern for RCS protocol, which is sorta lenient from the carrier perspective. it comes as only a minor surprise that they (cell phone / teleco) wouldn't want to get into the encrypted traffic side of the engineering -- otherwise:
telco cannot be trusted for end-user security, so the implementation of RCS (as you mentioned) really matters quite a lot. My primary annoyance with iOS in this regard is that they've refused to implement AES or TLS or anything else on top of their RCS stack, but at least in this scenario it's usable from a browser regardless.