#signal server is now officially closed source, making it de facto a worse-looking telegram.
@danielinux @mmu_man That’s just not how it works.
While I agree that this is sad, something is not closed source just because the code is not public.
@danielinux @mmu_man To be more clear : there’s nothing in the (A)GPL (or any other common FLOSS licence) that requires the code to be public.
The only thing is that the code must be shared with users that ask for it.
The problem is not just an AGPL violation here, even though the license explicitly requires to show the code if you are providing a service on top of it. According to AGPL-3, if you are using the service you are the user. Good luck anyway submitting such a request to them at this point.
The actual problem is that #signal is no longer willing to publicly share the sources of their server platform, which is what #signalapp users criticized the most about others in the past, #telegram in particular.
@danielinux @mmu_man > even though the license explicitly requires to show the code if you are providing a service on top of it.
No, the license requires that you share the code to your users that request it, not that the code is made public to everyone. Has anybody formaly requested the code to them?
I mean really presuring them to release it by threatening legal actions?
@danielinux @mmu_man Telegram e2ee is a joke, their protocol has never been audited, they don’t support encryption in groups, they store unencrypted backups, they have a shit ton of metadata on their users (Signal doesn't even know who talks to whom).