I'm sorry but matrix is a convoluted mess. Speaking from experience, when there's a deep focus on protocols and technical architecture before usability it becomes incredibly hard for the consumer side to get started. It's still very much a DIY thing and the promise of Element hosted offerings kind of just defies the point of the federated design for what most came into it for, self hosting.
Honestly, we just need a drop dead simple chat client/server that can be self hosted and may be eventually extended via wireguard/tailscale networks and MagicDNS.
I'd disagree. In terms of privacy and anonymity, Matrix is an unguaranteeable nightmare. Just all the IRC bridges alone are a worst case scenario on what can happen with your data.
I'd rather recommend Briar [1] which is really end to end encrypted, and works even offline via bluetooth or Wi-Fi LAN.
The Matrix team seems to be focusing on anything but making it as performant and usable as Telegram or Slack. The project leaders have been told this multiple times but there is always a reason.
Matrix/Element iOS builds send all notifications (by Apple's design) through centralized developer-run servers that wake up your client app to talk to your homeserver.
There's no way for you to avoid SPOFs for notifications on Apple devices, because APNS is designed so that the only way you can wake up an app to talk to an API is via notifications sent from the developer of that app.
This means that if the APNS servers go down (unlikely), or that the vector.im notification relay servers go down, nobody using Element on iOS gets any notifications.
It also means that vector.im sees all of the notification events (who got notified when), though I don't believe they see the notification content. The notifications (I speculate) are simply app wakeup events that make the app then contact the homeserver to see what it has new.
I mean, that's great and all, but it would still be pretty annoying if large parts of your network go down, and especially if matrix.org would go down.
I'm actually convinced that all the open source messaging apps are harder to install than postfix or opensmtpd thus a true pain in the butt. I get that most are trying to sell services but having an easy to install and setup program would make a real difference.
It does exist a twitter[0] account not updated since 2014 that has, ironically, in its bio: "We are working very hard to make this twitter account irrelevant."
Even though I do have WhatsApp I wouldn't have noticed without this HN headline.
Everyone I message with is via iMessage or Signal nowadays and I only have WhatsApp because I am part of a few sports clubs which have a WhatsApp group but we don't chat enough for me to notice a downtime like today.
Makes me happy to see how I've actually managed to rid myself of WhatsApp for the most part.
Open source, doesn't require a phone number, and a big strength is that it's decentralized, which makes it much less vulnerable to outages like this.
"Session utilises the decentralised Oxen Service Node Network to store
and route messages. This means that unlike P2P messaging applications
you can message Session users when they are offline.
This network consists of community operated nodes which are stationed
all over the world. Service nodes are organised into collections of small
co-operative groups called swarms.
Swarms offer additional redundancy and message delivery guarantees even if some service nodes become unreachable. By using this network, Session doesn’t have a central point
of failure, and Session’s creators have no capacity to collect or store
personal information about people using the app"
I have investigated session previously and gotten the feeling that it's backed by some kind of crypto pyramid scheme. I can't shake that feeling and the front page talk of joining "the movement" isn't helping.
Nothing on iOS is decentralized, all push notifications must be proxied via Apple's APNS servers from the app developer. There's no support in iOS for p2p messaging apps, even Matrix/Element proxy the notifications via centralized developer-run servers (which are then routed via centralized (but non-SPOF) Apple APNS servers).
I supposed it's a Matrix client, but couldn't find anything by glancing the home page.
Btw, the whole idea of "no phone numbers" makes it really hard to spread. It basically means you can't send a message to anyone in your address book that already has Session installed, unless you get his Session username by other means.
Coincidental timing for me- anecdotally I noticed a few WhatsApp commercials during the Monday Night Football game last evening. Meta was hyping up how its end to end encrypted. That’s the first time I have seen national tv adverting for WhatsApp. There also were commercials for Meta’s new headsets so maybe it was part of a larger spend.
Take my advice - switch off notifications. You'll still see the badge on the app itself e.g. with a red dot, at least that's how it is on iOS. So when you see that you'll know to open it. Before that, there's no reason to be bothered while you're doing something else.
[+] [-] chagaif|3 years ago|reply
[+] [-] asim|3 years ago|reply
Honestly, we just need a drop dead simple chat client/server that can be self hosted and may be eventually extended via wireguard/tailscale networks and MagicDNS.
[+] [-] sofixa|3 years ago|reply
[+] [-] cookiengineer|3 years ago|reply
I'd rather recommend Briar [1] which is really end to end encrypted, and works even offline via bluetooth or Wi-Fi LAN.
[1] https://briarproject.org/
[+] [-] tjixxu|3 years ago|reply
[+] [-] sneak|3 years ago|reply
There's no way for you to avoid SPOFs for notifications on Apple devices, because APNS is designed so that the only way you can wake up an app to talk to an API is via notifications sent from the developer of that app.
This means that if the APNS servers go down (unlikely), or that the vector.im notification relay servers go down, nobody using Element on iOS gets any notifications.
It also means that vector.im sees all of the notification events (who got notified when), though I don't believe they see the notification content. The notifications (I speculate) are simply app wakeup events that make the app then contact the homeserver to see what it has new.
[+] [-] Vinnl|3 years ago|reply
[+] [-] protomyth|3 years ago|reply
[+] [-] zeitlupe|3 years ago|reply
[+] [-] prmoustache|3 years ago|reply
[+] [-] stiltzkin|3 years ago|reply
[+] [-] smingo|3 years ago|reply
[+] [-] zaik|3 years ago|reply
[+] [-] barbariangrunge|3 years ago|reply
[+] [-] dt3ft|3 years ago|reply
[+] [-] fyvhbhn|3 years ago|reply
[+] [-] detaro|3 years ago|reply
[+] [-] jansan|3 years ago|reply
[+] [-] taspeotis|3 years ago|reply
[+] [-] jakopo87|3 years ago|reply
[0] https://nitter.net/wa_status
[+] [-] perryizgr8|3 years ago|reply
[+] [-] dustedcodes|3 years ago|reply
Everyone I message with is via iMessage or Signal nowadays and I only have WhatsApp because I am part of a few sports clubs which have a WhatsApp group but we don't chat enough for me to notice a downtime like today.
Makes me happy to see how I've actually managed to rid myself of WhatsApp for the most part.
[+] [-] seydor|3 years ago|reply
[+] [-] sMarsIntruder|3 years ago|reply
[+] [-] sgt|3 years ago|reply
[+] [-] KoftaBob|3 years ago|reply
Open source, doesn't require a phone number, and a big strength is that it's decentralized, which makes it much less vulnerable to outages like this.
"Session utilises the decentralised Oxen Service Node Network to store and route messages. This means that unlike P2P messaging applications you can message Session users when they are offline. This network consists of community operated nodes which are stationed all over the world. Service nodes are organised into collections of small co-operative groups called swarms.
Swarms offer additional redundancy and message delivery guarantees even if some service nodes become unreachable. By using this network, Session doesn’t have a central point of failure, and Session’s creators have no capacity to collect or store personal information about people using the app"
[+] [-] mnsc|3 years ago|reply
[+] [-] sneak|3 years ago|reply
[+] [-] yaddaor|3 years ago|reply
> Oxen blockchain and the $OXEN privacy token
[+] [-] miroljub|3 years ago|reply
Btw, the whole idea of "no phone numbers" makes it really hard to spread. It basically means you can't send a message to anyone in your address book that already has Session installed, unless you get his Session username by other means.
[+] [-] smithcoin|3 years ago|reply
[+] [-] jve|3 years ago|reply
[+] [-] Nextgrid|3 years ago|reply
[+] [-] irjustin|3 years ago|reply
[+] [-] skc|3 years ago|reply
Though for my closest friends and family we still have Signal as backup.
[+] [-] sgt|3 years ago|reply
[+] [-] Aachen|3 years ago|reply
Sounds like a nice way to test new notification settings before putting them into production. Now go and apply them ;)
[+] [-] dncornholio|3 years ago|reply
[+] [-] Synaesthesia|3 years ago|reply
[+] [-] dividebyhero|3 years ago|reply
[+] [-] vardump|3 years ago|reply
[+] [-] jiggywiggy|3 years ago|reply
[+] [-] unknown|3 years ago|reply
[deleted]
[+] [-] unknown|3 years ago|reply
[deleted]
[+] [-] quados|3 years ago|reply
[+] [-] thinkpapi_W541|3 years ago|reply
[deleted]
[+] [-] klpu|3 years ago|reply
[deleted]
[+] [-] light_hearted|3 years ago|reply
[deleted]
[+] [-] saivamsisuru99|3 years ago|reply
[+] [-] sgt|3 years ago|reply