Live data from Hacker News

Signal is having technical difficulties

status.signal.org

331–340 of 750 posts

Re: Signal is having technical difficulties

#331
post #290
post #221

Earlier quoted context omitted.

IRC all over again. I don't see this taking over until someone comes up with its Gmail.

'its gmail' is matrix.org. It is the default server when you start up Element.

Exactly. There's no reason to run your own server aside from supporting the decentralized nature of it (or wanting to be 100% in control).

Re: Signal is having technical difficulties

#332
For those unaware, the Signal protocol developed by Open Whisper (previous name) is what was adopted by WhatsApp / Facebook Messenger / Skype and possibly others. In a sense, Signal is the original reference implementation of the specification.

https://en.wikipedia.org/wiki/Signal_Protocol

Re: Signal is having technical difficulties

#333
post #311

Earlier quoted context omitted.

Paying for software vs phones is not really an apples to apples comparison. A better comparison would be how people gladly pay ten bucks a month for spotify/netflix but would probably never pay that for messaging and IMHO that's where the industry should be going. People in the past also thought music and movies should be free and pirated the shit out of them, but by making it simple and accessible, for ten bucks a m…

Paying for avatars and stickers.

Paying for coins in a game.

Re: Signal is having technical difficulties

#334
post #25

Earlier quoted context omitted.

I don't see a banner on the top of my app. I only found out when the desktop client kept timing out with 502 errors and after asking on Twitter, found other people were having issues too. It's there on https://status.signal.org/ though.

There is a banner in the Android app, not on the desktop.

For me it's the other way around, haven't had any banners or anything on Android, whereas the desktop client has, and messages have been throwing 50x errors, while the mobile messages just seem to take ages to send.

Re: Signal is having technical difficulties

#336
post #68
post #36

Why not do a some kind of lazy P2P instead of proactive P2P? IIRC, Signal calls are P2P.

Wait, so I can geolocate someone and figure out their ISP by starting a Signal call? Great feature, I love it!

Calls can be relayed through Signal servers:

> Always relay calls:

> Relay all calls through the Signal server to avoid revealing your IP address to your contact. Enabling will reduce call quality.

Re: Signal is having technical difficulties

#337
post #287
post #71

I just donated to Signal after seeing the error banner in the app. I realised I was more than happy to pay WhatsApp's yearly charge back in the pre-Facebook days (think it was 70p or so?). Figured I could give Signal a few quid every now and then, maybe keep a server up for a few seconds :) Donation link should anyone be interested: https://signal.org/donate/

They could easily add an optional badge to avatars showing that you donated $1 that year via an optional in-app purchase. The subtle social pressure in a lot of group chats would be pretty effective, and it would help raise awareness that it is run by a non-profit foundation.

This sounds good on first pass, but consider the implication of allowing donations (and thus, payment method information) to be tied to a Signal users account. I specifically _wouldn't_ want this.

Re: Signal is having technical difficulties

#338
post #71

I just donated to Signal after seeing the error banner in the app. I realised I was more than happy to pay WhatsApp's yearly charge back in the pre-Facebook days (think it was 70p or so?). Figured I could give Signal a few quid every now and then, maybe keep a server up for a few seconds :) Donation link should anyone be interested: https://signal.org/donate/

Thanks for the idea, I also took the opportunity to donate a nice chunk in support of a service I use often and want to continue to exist.

Re: Signal is having technical difficulties

#339

Earlier quoted context omitted.

The signal server project in GitHub isn't updated in 9 months. Have they talked about why they don't do server development in the open?

The Signal servers essentially pass around encrypted blobs from one device to another. Most of the development work is on extending the clients to pass around different types of messages, so there's not much work that needs to be done on the server.

9 months is a long time to go without updates though, especially if you just got a ton of extra users. While I definitely see your point, GP also has a point about development clearly not being open. It's "code available" software, not "open source server" software.

Re: Signal is having technical difficulties

#340
post #218

Time to jump ship! Use element / matrix an open, decentralized, end-to-end encrypted chat protocol with slick clients for Android, iOS, Desktop & Web: https://element.io/ Also easy to self-host a server, if you need full control: $ mkdir -p ~/synapse $ pip3.6 install --user jinja2 matrix-synapse $ cd ~/synapse $ python3.6 -m synapse.app.homeserver \ --server-name my.domain.name \ --config-path homeserver.yaml \ --gen…

The notifications transport for these on iOS is necessarily centralized as push notifications have to be sent from an apple developer client cert to Apple's APNS system. There is no such thing as decentralized messaging on iOS for this reason. The matrix developers run a push service, which all servers have to talk to to push notifications to their iOS app, even if you run your own instance. [ EDIT: The following sta…

> The matrix developers run a push service, which all servers have to talk to to push notifications to their iOS app, even if you run your own instance.

This isn't really true: there are lots of Matrix iOS clients out there, and each run their own separate push server. Only Element iOS's push server is run by the 'matrix developers', and if you are worried about that then (if you are an iOS developer) you can build your own copy of Element iOS pointed at your own push server.

> This means that both the push server operator, as well as Apple, can see the content of all of the push notification messages, thereby bypassing the e2e encryption as well.

This is completely incorrect. By definition, the server can't see the contents of end-to-end encrypted messages, and we don't send push contents (encrypted or otherwise) to the push gateway anyway. Instead, the push notification is a single flag sent to the client to tell it to wake up, which then runs a Push Extension (on iOS) to talk to the Matrix server and do E2EE in order to display the notification body (if desired). It's become particularly painful since iOS 13 thanks to https://appleinsider.com/articles/19/09/05/secure-messaging-....

Post reply on HN