News for hackers. Stuff that matters.
Re:Keep your phone number private with Signal usernames by smt88 on Tuesday February 20, 2024 @02:23PM (#39445669)
Is Signal considered to be (or attempting to be) an open ecosystem?

My understanding is that Signal (the app) is private, not anonymous, centralized, and closed.

The underlying protocol is open and could be used for an open ecosystem, but I didn't think Signal aspired to do that.

Re:Keep your phone number private with Signal usernames by lima on Tuesday February 20, 2024 @02:37PM (#39445857)
The apps and most of the backend are open source too, not just the protocol.

The important distinction is that it's not decentralized like XMPP or email, which is a conscious decision: it would become very difficult to change it to add new features and they'd be left behind by closed-source competitors (see: XMPP).

Re:Keep your phone number private with Signal usernames by ezst on Tuesday February 20, 2024 @05:08PM (#39447647)
I see that it is a ton of wishful thinking and FUD on the side of Signal to claim that: XMPP is alive and kicking, has all the features one needs, runs everywhere, at scale, offers the same or better crypto, better privacy, better resilience and is more sustainable. When Signal will inevitably fail/turn against its users/enshittify itself or get acquired, all federated and P2P protocols will keep on going. For decades. That's the kind of communications systems we should be demanding in the present era, nothing less.
Re:Keep your phone number private with Signal usernames by kiwijamo on Tuesday February 20, 2024 @05:18PM (#39447745)
Yet I'd wager most HN readers have a grand total of zero XMPP contacts. Myself included. Proving the GPs point.
Re:Keep your phone number private with Signal usernames by AJ007 on Tuesday February 20, 2024 @07:40PM (#39448856)
Because of what Google did with Google Talk. https://ploum.net/2023-06-23-how-to-kill-decentralised-netwo...

XMPP is underrated. A lot of people are imagining Pidgen in 2011, but the protocol has been extended, the actively developed clients are good, and it avoids the heavier parts of Matrix (both client and server side.) I wouldn't be surprised if Slack's replacement when Salesforce inevitably fucks it up will be XMPP based rather than Matrix.

Re:Keep your phone number private with Signal usernames by smt88 on Tuesday February 20, 2024 @09:59PM (#39449670)
Slack's replacement is going to be Teams. No corporation chooses internal chat clients based on interoperability or openness of source code.
Re:Keep your phone number private with Signal usernames by hot_gril on Wednesday February 21, 2024 @11:12AM (#39455635)
"The protocol has been extended" has been XMPP's theme for decades, and also its problem. Name your favorite client, it probably won't have several extensions, and a lot of useful things require support on both ends plus the server. Lots of things that should be ubiquitous are not, including s2s auth. There needed to be more structure, like AIM back then or Signal now.

Even if Google Talk kept XMPP, they weren't going to save it, cause nobody used Google Talk. Facebook was by far the biggest XMPP-supported platform (though it wasn't federated), and they stopped probably cause they didn't see enough clients. Even Slack supported XMPP for a while, did you use that?

Re:Keep your phone number private with Signal usernames by freeAgent on Wednesday February 21, 2024 @04:29PM (#39459814)
My entire friend/acquaintance group used Google Talk in the late-‘00s.
Re:Keep your phone number private with Signal usernames by zaik on Wednesday February 21, 2024 @12:09AM (#39450363)
I kicked out all the walled-garden apps like Signal and went standard XMPP only. I have a lot of XMPP contacts now. You just need to commit to it.
Re:Keep your phone number private with Signal usernames by cortesoft on Wednesday February 21, 2024 @12:13AM (#39450388)
And have friends who are all willing to commit to it, too
Re:Keep your phone number private with Signal usernames by zaik on Wednesday February 21, 2024 @12:17AM (#39450413)
Not really, my friends are still using proprietary apps besides their XMPP client.
Re:Keep your phone number private with Signal usernames by WhyNotHugo on Wednesday February 21, 2024 @06:57AM (#39452753)
Did you set up bridges for contacts on legacy networks?
Re:Keep your phone number private with Signal usernames by zaik on Wednesday February 21, 2024 @01:52PM (#39457855)
Only Biboumi for IRC.
Re:Keep your phone number private with Signal usernames by hot_gril on Wednesday February 21, 2024 @11:22AM (#39455772)
Is it really a wish if it's already come true? I can't name a single person who uses XMPP. If a federated chat protocol ever wins, it'll probably be something more modern like Matrix. At least there's email too.
Re:Keep your phone number private with Signal usernames by Vinnl on Tuesday February 20, 2024 @02:58PM (#39446111)
They've described what they're attempting to be here: https://signal.org/blog/the-ecosystem-is-moving/
Re:Keep your phone number private with Signal usernames by greyface- on Tuesday February 20, 2024 @04:21PM (#39447075)
The author is no longer CEO, though, and there are a lot of "I" statements in the post. Is it still accurate? Has the current CEO made any comment on it?
Re:Keep your phone number private with Signal usernames by sdenton4 on Tuesday February 20, 2024 @05:03PM (#39447581)
It's a great encapsulation of why Signal is not federated, and, unless you find the current CEO stating otherwise, is unlikely to change. Changes like the one detailed in the link simply wouldn't be possible to roll out efficiently in a federated ecosystem.

Signal has consistently focused on helping /most/ users do what they want with the app without sacrificing security. This change - away from requiring phone numbers - helps plug one of the biggest criticisms, both on the security and product side. Nothing about their mission requires federation, so I respect that they haven't sacrificed their mission in order to do it.

Re:Keep your phone number private with Signal usernames by fsflover on Tuesday February 20, 2024 @05:51PM (#39448034)
Re:Keep your phone number private with Signal usernames by bjoli on Wednesday February 21, 2024 @10:07AM (#39454696)
I tested matrix in 2021 and found the experience pretty darn awful outside the main client. And by a cursory glance the ecosystem is still pretty much controlled by the matrix.org folks. When I was using it there was a lot of accusations that Synapse did not follow the specification and that server implementera had to reverse engineer what Synapse did to be able to federate.

And talking about that: does federation work properly yet? I used a third party provider and it made my life miserable.

I am all for federation, but in my experience the "federated" part of matrix was a lot worse than the jabber one they want to replace.

Re:Keep your phone number private with Signal usernames by fsflover on Wednesday February 21, 2024 @10:39AM (#39455124)
I'm using a non-matrix.org server. It works fine.
Re:Keep your phone number private with Signal usernames by rstuart4133 on Tuesday February 20, 2024 @05:54PM (#39448059)
Moxie's post looks solid, but there is a counter example: bitcoin nodes. They are a very loose federation of nodes that go through regular upgrades in the protocol. So it is possible.

But yes, it's also very hard. The bitcoin protocol didn't start out that way. It took a lot of knocks and bruises to get to the point they could upgrade all the servers in the federation.

Interestingly, the method bitcoin came up with allows protocol changes to fail, meaning the bulk of the federation never takes them up. Everyone gets a vote, and it only succeeds if the bulk of the federation upgrades. Perhaps from Moxie's point of view that's unacceptable, as it means he is no longer the dictator of the protocol.

Nonetheless, it is possible to design a protocol so it can be upgraded relatively quickly. Even if you don't do add "quick transition" features to a protocol transitions can still haven. IPv6 will replace IPv4. But as Moxie says, it's painfully slow.

Re:Keep your phone number private with Signal usernames by kaanyalova on Tuesday February 20, 2024 @02:49PM (#39446011)
Both the app and the server is open source

https://github.com/signalapp/Signal-Android https://github.com/signalapp/Signal-Server

There are forks like Session which doesn't require a phone number to sign up

https://github.com/oxen-io/session-android

Re:Keep your phone number private with Signal usernames by smt88 on Tuesday February 20, 2024 @05:06PM (#39447625)
I understand this, but Signal doesn't attempt to tolerate third-party apps on their servers as far as I know. They don't support interoperability.
Re:Keep your phone number private with Signal usernames by godelski on Tuesday February 20, 2024 @05:46PM (#39447985)
You can run Signal app forks on the Signal server. Molly is a popular one. You just can't create new servers. I wish you could, but I get the reasoning of not wanting honeypots. But that doesn't stop you from running your own network of Signal servers. So I don't see anything stopping anyone. I mean Mullvad runs their own stuff and I don't see half the complaints about them. I've always been curious why Signal is so unique here. If 1/100th the people that made these concerns developed a open community of signal servers, I'm sure we'd have a viable alternative network. What's stopping everyone?
Re:Keep your phone number private with Signal usernames by AJ007 on Tuesday February 20, 2024 @07:51PM (#39448929)
One of the big lessons from Twitter and Reddit was third party apps are tolerated or even encouraged until they are not. Unlike, for example Discord, I haven't see any indication that third party clients are causing account bans, yet.

The status of open source, privacy respecting messaging apps looks really healthy to me, compared to where we've been over the past 30+ years (thinking starting with ICQ.) Signal was a big leap toward getting average people using much more secure messaging, although it is pretty clear even most 'tech' people don't grasp what is going on or why it is important to be able to use e2ee separate from a combined client+server provider.

Re:Keep your phone number private with Signal usernames by godelski on Tuesday February 20, 2024 @07:54PM (#39448950)
Yes, but my argument is more in the realms of "why are there no projects to create an open network using the existing architecture" not "we shouldn't have an open network and completely rely on Signal forever."
Re:Keep your phone number private with Signal usernames by xorcist on Wednesday February 21, 2024 @06:54AM (#39452714)
The Signal devs have been very clear that they consider forked or third party clients freeloaders and will cut them off, sooner or later.
Re:Keep your phone number private with Signal usernames by godelski on Wednesday February 21, 2024 @12:34PM (#39456812)
Source? Sounds like even a bigger reason to create a parallel network
Re:Keep your phone number private with Signal usernames by LtWorf on Wednesday February 21, 2024 @03:04PM (#39458770)
I recall reading this as well on their website
Re:Keep your phone number private with Signal usernames by godelski on Wednesday February 21, 2024 @11:42PM (#39463340)
I'd still appreciate a source. There's things I'm aware of that I think could be confused with this, but I've seen no indication of them actually wanting to or even caring about forks. Only in the servers.

In fact, in this thread they are discussing how you can, with Molly, use both the official and staging servers with the same number: https://community.signalusers.org/t/signal-fork-with-passphr...

A mod recommends Molly here: https://community.signalusers.org/t/how-to-use-signal-on-3-d...

A list of forks: https://community.signalusers.org/t/list-of-unofficial-forks...

And here's people arguing: https://community.signalusers.org/t/on-forking-signal/31651/...

As far as I can tell, Signal's policy is more "Do what you want, but server costs are high so we don't want to pay for your product. But if you do, here's all the code to give you a start." That's a very different policy from blacklisting.

And as I keep asking others, what's stopping everyone from making a federated Signal? If you can use the same account on both the production/official server and the staging server, why can't you on the production server __and__ a community federated server?

And if they ban you from the production server, so what? Now you're on par with literally every other federated service. Like what is Signal going to do? Stop open sourcing code? That'd be like trying to kill a mosquito by stabbing yourself in the heart. If they're willing to do that, I'd rather it be sooner than later anyways.

So I want a source because I just don't get what you all are complaining about. Is it just that someone else didn't make the thing you want? Sure, I get frustrated, but the comments more come off as Signal being nefarious and I just don't see Signal acting in any way malicious. In fact, hosting links to forks and being a common place for those forks to discuss seems like they are actively supporting them.

Re:Keep your phone number private with Signal usernames by xorcist on Thursday February 22, 2024 @10:30AM (#39468555)
Who is complaining? This is confusing. The whole idea about Signal is to compete with mainstream, as well as with the federated, ecosystems by having a single implementation of both client and server, I believe the argument is that only by moving faster is it possible to compete with the more mainstream commercial messengers for the masses and still have reasonable cryptography.

Moxie wrote several articles about this and expanded on this idea in his conference talks. You are very welcome to take the code and write your own messing system, but do not connect to Signal's servers because that costs them money and they will need to take action, sooner or later.

They were very clear that LibreSignal had no future. They have also been very clear that they discourage any non-official distribution of builds. They have repeatedly told the F-Droid project that they will not publish using their reproducible build system, and any user doing the same will be kindly asked to take down their copy. The F-Droid project has complied.

This seems to be a strange thing to discuss. If the above links are representative it may be a popular subject among a subset of users, which seems misguided. Signal does not wish to be xmpp or matrix and neither should they. It must be their right to decide. There are so many chat software projects. If you don't agree with the goals of one of them, you energy is better spent elsewhere.

Re:Keep your phone number private with Signal usernames by godelski on Thursday February 22, 2024 @01:29PM (#39471097)
Lots of people are complaining. It's why Moxie wrote those many articles. It's why there's so many comments bringing up Matrix and others. People were even doing this before Matrix was E2EE! So yeah I'm tired of hearing it so calling people's complaints out. If you don't like it, fix it. It's HN and people are devs here.
Re:Keep your phone number private with Signal usernames by WhyNotHugo on Wednesday February 21, 2024 @06:55AM (#39452735)
It's not [attempting to be an open ecosystem]. Their ToS used to forbid using third party clients. I don't think this has changed. They haven't banned anyone for using third party clients (to the best of my knowledge), but they're openly against an open ecosystem.

It's private, centralised and the network is closed (e.g.: non-federated), but the source code is public and open source. I think that for the server implementation they do code dumps every once in a while, rather than continuously keep it public.

Re:Keep your phone number private with Signal usernames by faiD9Eet on Wednesday February 21, 2024 @06:51PM (#39461298)
> My understanding is that Signal (the app) is private, not anonymous, centralized, and closed.

You are right about that. There used to be an open source build called LibreSignal

Moxie Marlinspike made clear [1]: You may inspect the code. You are even allowed to compile it. You are not allowed to connect your self compiled client to our message servers. We are not interested in a federated protocol. Make sure your fork creates its own bubble that does not overlap with Open Wisper Systems. Stop using the name Signal.

[1] https://github.com/LibreSignal/LibreSignal/issues/37#issueco...