AllNewTypeFace@leminal.space 3 months ago
IIRC, they do forbid third-party clients from their network. You can build it from source, but you won’t be able to connect to production Signal servers.
Third-party clients would not necessarily be a bad thing. Signal has limited resources, and as such has to cut corners. I for one would love a native desktop client that’s not Electron bloatware.
Dot@feddit.org 3 months ago
There is already 2 third party forks I know of, molly and Signal-jw.
They both use and access the main production Signal servers.
Static_Rocket@lemmy.world 3 months ago
I could appreciate a client certification that is optional, like a list of approved clients on their website or something along those lines.
It should not be enforced by killing the client. I like security, but I enjoy software freedom more.
rottingleaf@lemmy.world 3 months ago
You mean running a trojan “as a mean of security”, similar to anticheats? Are you sure this is a good idea?
Or if by “program” you mean having some allowed clients as opposite to only the official one allowed, it’s a social thing, not a technical one. So it still won’t prevent anyone from connecting with another client.
Dot@feddit.org 3 months ago
I mean having a list of allowed clients.
As I said in my post, WhatsApp already enforce forbidding third party client and it seems to work well.
I don’t see why wouldn’t Signal improve the security of their users by implementing this, while upsetting the very few users who use third party clients.
rottingleaf@lemmy.world 3 months ago
How do you imagine this working?
just_another_person@lemmy.world 3 months ago
It takes resources to run and maintain such things. Probably not something they feel they can or want to take on.