105
this post was submitted on 06 May 2025
105 points (100.0% liked)
Technology
38618 readers
216 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The problem here is not the fork itself tho, and it rarely is. The very obvious and openly communicated issue is the complete undermining of E2EE and sending everything to a single entity. Of course, very niche forks may have too few eyes on them to detect malicious changes, but that just isn't at all the current situation with the Signal fork.
I’d argue security through obscurity was gone by 2000, for anything that can be pinged.