IT enthusiast. TV addict. A systems admin / tinkerer, who is also curious about development, network and security fields.
I created this account on leap day 2020, but I didn’t use it nearly this much before Twitter was purchased.
#tfr #tootfinder
https://justmytoots.com/@[email protected]
https://www.topmastodonposts.com/by/@[email protected]
#GreenNuclearDeal🌿⚛️⚡🤝 @tcely
Backup account: @tcely
Accessing the keys from the server isn’t really a mystery or hidden. It’s technically possible for Apple to write software to query servers run by Google as well as any servers they created for themselves.
You don’t need implementation source code when you have open standards already.
WhatsApp actually used Signal’s development team to rollout the Signal protocol for them, but that app is still untrustworthy.
What kind of openness are you hoping for? Google has built their solution with a bunch of already open pieces.
RCS + Signal protocol + MLS
https://www.androidauthority.com/google-messages-mls-3346918/
https://www.theverge.com/2023/7/20/23801536/google-messages-app-mls-support-announce
Another good video is showing what things look like.
https://toot.jeena.net/users/jeena/statuses/110568555005254698
Lemmy & KBin & Mastodon & Misskey & Calckey & others all use the ActivityPub protocol to deliver posts to your inbox no matter which account / software created the post in the first place.
How the posts are interpreted changes a bit depending on what software was used to create and display your inbox.
This is very much like how email works in Outlook & Gmail, but how the labels or tagging changes depending on which you use.
Try this video:
There are all kinds of useful named things to learn about.
Here are the links to the documentation for these standards:
MLS - https://datatracker.ietf.org/wg/mls/documents/
Signal Protocol - https://www.signal.org/docs/
RCS - https://www.gsma.com/futurenetworks/rcs/universal-profile/ & https://www.gsma.com/futurenetworks/resources/rcs-up-2-4-uni/
@skullgiver