Most active commenters
  • hiq(3)

←back to thread

544 points josh2600 | 16 comments | | HN request time: 0.828s | source | bottom
1. qrbLPHiKpiux ◴[] No.26714509[source]
Is your backend open source, or not?

Haven’t seen the git updated in a while.

replies(2): >>26714686 #>>26717022 #
2. brodo ◴[] No.26714686[source]
Effectively not anymore. Here is a very recent german article about it: https://www.golem.de/news/crypto-messenger-signal-server-nic...

No updates in the repo for over a year and no answers from the team. The whole crypto currency thing is also a red flag for me. Matrix seems to be the better option by now...

replies(3): >>26715019 #>>26715193 #>>26717772 #
3. rogers18445 ◴[] No.26715019[source]
Just what are they trying to do? They are a non-profit which would make a money grab somewhat impractical. Are they worried they are going to get successfully forked or something?

Their unquestioned faith in Intel SGX is somewhat pathetic to be fair.

4. dunefox ◴[] No.26715193[source]
If anything, Threema is the best alternative.
replies(1): >>26717890 #
5. hiq ◴[] No.26717022[source]
Last commit 5 days ago: https://github.com/signalapp/Signal-Server
replies(1): >>26717113 #
6. olah_1 ◴[] No.26717113[source]
This is either the mandela effect (I know for a fact that the server was stuck on "April 2020" for at least 6 months), or Signal intentionally hid development and then revealed it all when they realized it was bad PR.
replies(3): >>26717385 #>>26717647 #>>26717865 #
7. hiq ◴[] No.26717385{3}[source]
No, they just pushed today. They presumably didn't want to talk about MobileCoin before it was ready.
8. Forbo ◴[] No.26717647{3}[source]
I saw that not too long ago myself. Purely speculation here, but perhaps they opted not to publish any commits until they had a chance to have their MobileCoin implementation audited? Just wish they had been more forthcoming about why they were not pushing commits.
replies(1): >>26719545 #
9. hiq ◴[] No.26717772[source]
Old news: https://github.com/signalapp/Signal-Server
10. codethief ◴[] No.26717865{3}[source]
No, you're absolutely right. The repo had indeed been stuck on "April 2020". I last checked it two days ago.

Wayback Machine for March 11: http://web.archive.org/web/20210311053716/https://github.com...

11. pmlnr ◴[] No.26717890{3}[source]
No, it really is not. Matrix or XMPP.
replies(2): >>26722801 #>>26723439 #
12. olah_1 ◴[] No.26719545{4}[source]
How could they pump the coin overnight if they were forthcoming about their roadmap?
13. approxim8ion ◴[] No.26722801{4}[source]
XMPP has issues on Android and iOS: the app needs to be running and connected to the server at all times to fetch new messages. iOS explicitly disallows this from what I understand, and on Android you are at the mercy of your OEM's battery optimizations unless you specifically keep the app running by pinning it or if the app has persistent notifications. Either way, not something that is easy to explain to normal users, meaning pain points arise very soon.

Matrix is a little more promising, but Element (at least on matrix.org servers) is slow, especially at scale.

replies(1): >>26723193 #
14. Zash ◴[] No.26723193{5}[source]
Any chat app would have issues with battery optimizations. Solution is usually to use the mobile OS vendors push notification infrastructure. Work on that in XMPP started around 2015 and most popular clients and servers should have some support by now. It's tricky to make something nice while the platform is working against you tho, especially while those push notification systems use/d XMPP themselves.
15. dunefox ◴[] No.26723439{4}[source]
Any reasons why not? It ticks all the boxes for me: https://threema.ch/en/
replies(1): >>26725455 #
16. pmlnr ◴[] No.26725455{5}[source]
No self hosting, so not federated/decentralized.