this post was submitted on 07 Mar 2024
265 points (100.0% liked)
Technology
37735 readers
363 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
only when the service specifically requests it and agrees to Whatsapp's terms.
So I [in theory, I don't know how to start with this on a technical level] could make a third-party Signal-compatible app, but allow it to connect to Whatsapp instead of Signal? Even if I can't use my Signal account to contact Whatsapp people, that's still potentially useful. Although I imagine the terms I'd have to agree to to do so would be full of nonsense that stops this being remotely feasible.
you'd have to create a messaging service, not just a client.
I guess I'm misunderstanding here - I thought Whatsapp would be the "service" in my case, I'm just making a client to hook into their, presumably open [to people who agree to whatever their terms are] API. So it's more of a federation thing between services?
yeah, I guess you could call it that.